On 10/1/07, Sandro Dentella <[EMAIL PROTECTED]> wrote:
> I'm no expert of these specifications and would like to better
> understand. Firstly I'd appreciate a link to relevant part, secondly,
> reading the follow-up in the backward incompatible changes is:
It's section 9.1 of RFC 2616, where "saf
On Sat, Sep 29, 2007 at 08:01:12PM -0700, [EMAIL PROTECTED] wrote:
>
> Doh, it was not mod_wsgi, or localemiddleware, it was the
> set_language_view() that after rev 6177 requires a post request
I see in the Backwards-incompatible changes says:
The old behaviour meant that state (the locale
Doh, it was not mod_wsgi, or localemiddleware, it was the
set_language_view() that after rev 6177 requires a post request
On Sep 30, 4:29 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Found it, LocaleMiddleware is having some issues on mod_wsgi, i'll try
> figuring out why.
>
> On Sep 30,
Found it, LocaleMiddleware is having some issues on mod_wsgi, i'll try
figuring out why.
On Sep 30, 1:55 am, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> What does your mod_python Apache configuration look like?
>
> Only difference at this point is that mod_wsgi hosted app would run as
> distinc
What does your mod_python Apache configuration look like?
Only difference at this point is that mod_wsgi hosted app would run as
distinct user whereas mod_python would run it as Apache user.
Need to see how you set PythonPath in mod_python configuration.
Also, I am ignorant of a lot of what Dja
Still the same using Apache/2.2.2 and mod_wsgi 1.0
On Sep 28, 2:37 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> I will try apache 2.2 I am currentry running 2.0.58 on freebsd 6.1
>
> On Sep 28, 2:20 pm, "Ramiro Morales" <[EMAIL PROTECTED]> wrote:
>
> > On 9/28/07, [EMAIL PROTECTED] <[EMAI
I will try apache 2.2 I am currentry running 2.0.58 on freebsd 6.1
On Sep 28, 2:20 pm, "Ramiro Morales" <[EMAIL PROTECTED]> wrote:
> On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> > Updated mod_wsgi to revision 561
>
> > No change
>
> > On Sep 28, 10:25 am, "[EMAIL PROTECTED]"
>
On 9/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Updated mod_wsgi to revision 561
>
> No change
>
> On Sep 28, 10:25 am, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> wrote:
> > Django revision: 6426
> > Mod_wsgi revision: Revision: 489
> > Mod_python 3.2.7
> >
> > To test just set up the
Updated mod_wsgi to revision 561
No change
On Sep 28, 10:25 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Django revision: 6426
> Mod_wsgi revision: Revision: 489
> Mod_python 3.2.7
>
> To test just set up the admin interface and see if it is translated or
> not.
>
> --
>
> start
Django revision: 6426
Mod_wsgi revision: Revision: 489
Mod_python 3.2.7
To test just set up the admin interface and see if it is translated or
not.
--
startup script
#!/usr/local/bin/python
import sys, os
paths = [
'/home/hvalsluken/code']
if paths not in sys.path:
for path in
You are going to have to provide more information.
Stating versions of mod_python/mod_wsgi and the configurations/script
files used would be a start. Some example code of what triggers the
problem and any relevant Django configuration, plus, exactly which
version of Django or revision number from
I have a project running on django trunk using mod_wsgi in dev and
mod_python in production.
In production translation gives the expected results, in my own code
and in the admin.
Dev is set up exactly the same way, the only difference is that it is
running mod_wsgi, but no strings are translate
12 matches
Mail list logo
