On 20 October 2010 00:04, crumble wrote:
> Ok for another project that uses lxml I add to add the following
> Directive in my apache conf file:
>
> WSGIApplicationGroup %{GLOBAL}
>
> I tried it in my stackless configuration an now I can do `import
> stackless`
Which may imply that stackless Pytho
I have updated:
http://code.google.com/p/modwsgi/wiki/InstallationIssues#Multiple_Python_Versions
with additional information about why/when WSGIPythonHome should be
set for this sort of situation.
This is actually the primary reason for using WSGIPythonHome.
Use of this directive for Python
Ok for another project that uses lxml I add to add the following
Directive in my apache conf file:
WSGIApplicationGroup %{GLOBAL}
I tried it in my stackless configuration an now I can do `import
stackless`
I'll keep you posted If I manage to get Nagare working with mod_wsgi.
On 11 oct, 10:57, c
Yes I did a ./configure --with-python=/opt/stackless-2.7-maint/bin/
python and during compilation include dirs and library dirs were in /
opt/stackless-2.7-maint. Moreover, I only have that 2.7 python version
installed on my system.
On 9 oct, 16:25, Carl Nobile wrote:
> I just had a thought, did
I just had a thought, did you compile mod_wsgi with stackless? You
cannot just change the python version that mod_wsgi uses after it has
been compiled. You must use the exact version of python that mod_wsgi
was built with when you run your apps.
~Carl
On Fri, Oct 8, 2010 at 6:27 AM, crumble wrot
As a matter of fact I need channels, tasks and pickling of tasks.
My goal is to run nagare (http://www.nagare.org) applications, right
now I run them with apache using mod_fastcgi and flup.
I managed to change www-data path (I modified /etc/apache/envvars) now
my wsgi script displays:
/opt/stackl
Will your code need to be spawning a lot of threads on its own? Would
a process model do just as well. Guido has not, at least to my
knowledge, approved any way of getting around the GIL issues which
would make me very hesitant to use a fork of Python. I didn't
understand what stackless python was
I have no need for 2.7, what i need is stackless python actually.
But I assumed having a version number different from system one would
shed the light on linking errors I would miss otherwise.
Right now I'm trying to change www-data user's PATH so that apache
will find the right python executable.
It's always easier to work with the version that come with your
platform, and in production environments that's what we do. There will
not be enough different between 2.6 and 2.7 to make much difference.
Is there a reason you need to have a virtual env?
To get the python executable on the command
As I understand it, /opt/stackless-2.7-maint is my BASELINE
environment not just a package, the python I run is, /opt/
stackless-2.7-maint/bin/python. It is no symlink or venv python.
I thought in that case WSGIPythonHome would be /opt/stackless-2.7-
maint, any idea what the Python BASELINE enviro
10 matches
Mail list logo
