On 04/15/2014 01:08 PM, Joe Orton wrote:
On Mon, Apr 14, 2014 at 04:54:33PM -0400, Bohuslav Kabrda wrote:
AFAIK you can't have 2 mod_wsgi's, each one compiled against a
different Python major.minor, loaded by Apache at the same time for
various reasons. So the best solution would IMO be to creat
On Tue, Apr 15, 2014 at 09:21:50AM -0700, Toshio Kuratomi wrote:
> We should probably have a similar guard in the mod_wsgi config file as well.
> Then be sure that we consciously name the conf files so that we are
> promoting one of these as the default (because sort order will load one of
> them b
On Mon, Apr 14, 2014 at 04:54:33PM -0400, Bohuslav Kabrda wrote:
> ━━━
>
> I naively ported my Django app to Python 3 and didn't realize WSGI was
> going to be an issue. I saw python3-django was available for Fedo
> From: jor...@redhat.com
> Date: 04/15/2014 07:08
> Subject: Re: Python 3 and mod_wsgi
>
> On Mon, Apr 14, 2014 at 04:54:33PM -0400, Bohuslav Kabrda wrote:
> > AFAIK you can't have 2 mod_wsgi's, each one compiled against a
> > different Python major.minor,
On Mon, Apr 14, 2014 at 04:54:33PM -0400, Bohuslav Kabrda wrote:
> AFAIK you can't have 2 mod_wsgi's, each one compiled against a
> different Python major.minor, loaded by Apache at the same time for
> various reasons. So the best solution would IMO be to create
> python3-mod_wsgi (subpackage of
- Original Message -
> I naively ported my Django app to Python 3 and didn't realize WSGI was going
> to be an issue. I saw python3-django was available for Fedora 20 and thought
> I was all set until I saw in my httpd logs that python2.7 seems to be the
> assumed default for mod_wsgi. Aft
I naively ported my Django app to Python 3 and didn't realize WSGI was
going to be an issue. I saw python3-django was available for Fedora 20
and thought I was all set until I saw in my httpd logs that python2.7
seems to be the assumed default for mod_wsgi. After reading the README
and more,
