Thanks for the quick reply Russ :-)

> Do you only get the problem under mod_wsgi, or do you get it under the dev 
> server as well?
A new project and one of my finished projects works fine with the dev
server and rev #12873, so might just be a mod_wsgi issue

Updating to revs #12866 or #12873 gives me a 500 error with 'Apache/
2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i mod_autoindex_color
PHP/5.2.9 SVN/1.6.5 mod_wsgi/3.0 Python/2.6.5' underneath it

It only crashes for me with apache, mod_wsgi, new project (no views/
models/etc), finished project, and rev # 12865 and they all work
normally with the dev server, so that pretty much rules out any of my
code causing it. It could of course be some dodgy settings, no idea
what though...


On Mar 28, 4:01 pm, Russell Keith-Magee <freakboy3...@gmail.com>
wrote:
> On Sun, Mar 28, 2010 at 10:12 PM, nih <steven.bisse...@googlemail.com> wrote:
> > One of the files modified in django rev #12866 has broken mod_wsgi for
> > me, the web app loads perfectly ok in rev #12865, the apache mod_wsgi
> > log when using django rev #12866 has:
>
> ...
> > none of the changed files in rev #12866 look like they have anything
> > to do with mod_wsgi, so I've no idea :-(
>
> We've been getting some scattered reports of problems with changeset
> 12866, but so far, nothing specific that has enabled us to track down
> a specific cause. Ticket #13234 is tracking the problem, and based on
> the stack trace you provide, your problem appears to be related (your
> trace deals with trans_null, rather than trans_real, but the two
> functions are closely related). However, Django's test suite passes
> without any problems for me, and I can run my local test server and
> projects without difficulties.
>
> At this point, what we need are lots more details, hopefully leading
> to a test case that can reliably replicate the problem. So:
>
>  * Do you only get the problem under mod_wsgi, or do you get it under
> the dev server as well?
>
>  * Do you get the problem on *every* view, or just some views? If it's
> only on selected views, what are you doing on those views?
>
>  * What i18n code and settings are you using?
>
>  * Are you, at any point in your code, importing trans_real or
> trans_null specifically?
>
>  * Can you reduce your failing project to a minimal single view/model
> that causes the problem? Alternatively, can you create a test project
> from scratch that exhibits the problem?
>
> Thanks in advance for any assistance you can provide narrowing down
> this problem.
>
> Yours,
> Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to