Re: [Mailman-Developers] mailman
Hi Aditya,
On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote:
I'm sorry for the misdirect. I'm myself a beginner here!
Absolutely no problem, every hint is welcome :-).
I'm also a beginner with mailman 3 and absolutely no python expert :-(. To be honest it is not easy to understand the full procedure of installation of all needed components for mm3, at least if you like to install not the mailman_bundler package. There are so many sites with documentation and it is not easy to find out what is the right one. A step to step guide to install all components, which also beginners or not python programmers do understand, would be great. Maybe there is some kind of such a guide, but I haven't found it. And if it is not, I'd like to help to create such a guide, but I'd need support from people with mor knowledge of python and all the things which are needed.
This issue on gitlab is probably the same as the one you are facing. The fix recommended is the installation of falcon 0.3.0.1 or 0.3 [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503
If I understand it correctly, I already have a newer version of falcon installed:
root@mm3:/opt/mailman-bundler# find . -name *falcon* ./venv-3.4/lib/python3.4/site-packages/falcon ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info ./venv-3.4/bin/falcon-bench root@mm3:/opt/mailman-bundler#
But as said before, I'mno python expert...
Ciao and thanks again for your help,
Schoepp
The problem is that when python 3.4 makes a virtualenv, it somehow pulls in falcon1.0.0rc1... even if you have falcon0.3.0 installed.
I've spent the last couple days fighting with this exact problem and trying to find ways to trick python 3.4 to not pull in falcon 1.0 when making a virtualenv, no solution yet though. I suspect I'm going to have to rebuild python 3.4.4 a few times before getting it.
On 03/31/2016 10:09 AM, Christian Schoepplein wrote:
Hi Aditya,
On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote:
I'm sorry for the misdirect. I'm myself a beginner here! Absolutely no problem, every hint is welcome :-).
I'm also a beginner with mailman 3 and absolutely no python expert :-(. To be honest it is not easy to understand the full procedure of installation of all needed components for mm3, at least if you like to install not the mailman_bundler package. There are so many sites with documentation and it is not easy to find out what is the right one. A step to step guide to install all components, which also beginners or not python programmers do understand, would be great. Maybe there is some kind of such a guide, but I haven't found it. And if it is not, I'd like to help to create such a guide, but I'd need support from people with mor knowledge of python and all the things which are needed.
This issue on gitlab is probably the same as the one you are facing. The fix recommended is the installation of falcon 0.3.0.1 or 0.3 [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503 If I understand it correctly, I already have a newer version of falcon installed:
root@mm3:/opt/mailman-bundler# find . -name *falcon* ./venv-3.4/lib/python3.4/site-packages/falcon ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info ./venv-3.4/bin/falcon-bench root@mm3:/opt/mailman-bundler#
But as said before, I'mno python expert...
Ciao and thanks again for your help,
Schoepp
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex....
Security Policy: http://wiki.list.org/x/QIA9
I should also mention that I've done a full sweep of my system to make sure falcon 1.0.0rc1 isn't hiding anywhere. I can only suspect it's built into some other package and I need to hunt it down.
On 03/31/2016 10:18 AM, treal tv wrote:
The problem is that when python 3.4 makes a virtualenv, it somehow pulls in falcon1.0.0rc1... even if you have falcon0.3.0 installed.
I've spent the last couple days fighting with this exact problem and trying to find ways to trick python 3.4 to not pull in falcon 1.0 when making a virtualenv, no solution yet though. I suspect I'm going to have to rebuild python 3.4.4 a few times before getting it.
On 03/31/2016 10:09 AM, Christian Schoepplein wrote:
Hi Aditya,
On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote:
I'm sorry for the misdirect. I'm myself a beginner here! Absolutely no problem, every hint is welcome :-).
I'm also a beginner with mailman 3 and absolutely no python expert :-(. To be honest it is not easy to understand the full procedure of installation of all needed components for mm3, at least if you like to install not the mailman_bundler package. There are so many sites with documentation and it is not easy to find out what is the right one. A step to step guide to install all components, which also beginners or not python programmers do understand, would be great. Maybe there is some kind of such a guide, but I haven't found it. And if it is not, I'd like to help to create such a guide, but I'd need support from people with mor knowledge of python and all the things which are needed.
This issue on gitlab is probably the same as the one you are facing. The fix recommended is the installation of falcon 0.3.0.1 or 0.3 [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503 If I understand it correctly, I already have a newer version of falcon installed:
root@mm3:/opt/mailman-bundler# find . -name *falcon* ./venv-3.4/lib/python3.4/site-packages/falcon ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info ./venv-3.4/bin/falcon-bench root@mm3:/opt/mailman-bundler#
But as said before, I'mno python expert...
Ciao and thanks again for your help,
Schoepp
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex....
Security Policy: http://wiki.list.org/x/QIA9
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex....
Security Policy: http://wiki.list.org/x/QIA9
treal tv writes:
The problem is that when python 3.4 makes a virtualenv, it somehow pulls in falcon1.0.0rc1... even if you have falcon0.3.0 installed.
Barry has that pinned to < 1.0 in 3.0.3, do a diff against 3.0.2 (or maybe just grep the logs) and you should find out how to stop that.
I've been checking all the logs for hints, but I have a feeling I missed a big hint in there now. I'll try 3.0.2, thanks
On 03/31/2016 10:30 AM, Stephen J. Turnbull wrote:
treal tv writes:
The problem is that when python 3.4 makes a virtualenv, it somehow pulls in falcon1.0.0rc1... even if you have falcon0.3.0 installed.
Barry has that pinned to < 1.0 in 3.0.3, do a diff against 3.0.2 (or maybe just grep the logs) and you should find out how to stop that.
On 3/31/16 7:09 AM, Christian Schoepplein wrote:
I'm also a beginner with mailman 3 and absolutely no python expert :-(. To be honest it is not easy to understand the full procedure of installation of all needed components for mm3, at least if you like to install not the mailman_bundler package. There are so many sites with documentation and it is not easy to find out what is the right one. A step to step guide to install all components, which also beginners or not python programmers do understand, would be great. Maybe there is some kind of such a guide, but I haven't found it. And if it is not, I'd like to help to create such a guide, but I'd need support from people with mor knowledge of python and all the things which are needed.
I feel your pain.
This issue on gitlab is probably the same as the one you are facing. The fix recommended is the installation of falcon 0.3.0.1 or 0.3 [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503
If I understand it correctly, I already have a newer version of falcon installed:
root@mm3:/opt/mailman-bundler# find . -name *falcon* ./venv-3.4/lib/python3.4/site-packages/falcon ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info ./venv-3.4/bin/falcon-bench root@mm3:/opt/mailman-bundler#
We are not yet compatible with falcon 1.0, see <https://gitlab.com/mailman/mailman/issues/20>.
You need to find where in your installation falcon 0.3 is installed and replace the falcon 1.0 things in venv-3.4/lib/python3.4/site-packages with symlinks to the corresponding falcon 0.3 directories.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mar 31, 2016, at 07:36 AM, Mark Sapiro wrote:
We are not yet compatible with falcon 1.0, see <https://gitlab.com/mailman/mailman/issues/20>.
You need to find where in your installation falcon 0.3 is installed and replace the falcon 1.0 things in venv-3.4/lib/python3.4/site-packages with symlinks to the corresponding falcon 0.3 directories.
I think, but haven't tried, that if you blow away the falcon 1.0 directories in your venv, then install mailman-3.0.3 you should get falcon 0.3. Double check Mailman's setup.py, which should now pin Falcon to < 1.0.
Cheers, -Barry
participants (5)
-
Barry Warsaw -
Christian Schoepplein -
Mark Sapiro -
Stephen J. Turnbull -
treal tv