> In short, a C extension module may cache data from one sub interpreter
> and then use it in the context of a different sub interpreter causing
> incorrect or errornous behaviour. The problem with Decimal support in
> pyscopg falls into this category. It is entirely possible that the OP
> may
On 7/20/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> For the record, the description which was given to you whereby "if the
> first request served by a thread used the old version of Django, that
> was the version that was used for all subsequent requests on that
> thread" is nonsense.
On Jul 19, 2:07 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 7/19/07, oggie rob <[EMAIL PROTECTED]> wrote:
>
> > Please, if you've seen the same issue or have any helpful ideas to try
> > to stop the error, let me know.
>
> I think I've seen the same problem (or, at least, an
Thanks for the tip, Niels. I tried that and it didn't work either.
I got to thinking about how likely it would be that mod_python &
interpreters were causing problems. I've used multiple interpreters
for some time and haven't noticed any other strange behaviour. A
little test by printing out the
In case the problem lies in manipulating the python path inside a
section, perhaps you could play another trick to load the
different versions of django. I am doing as follows, though, not with
Location tags but in VirtualHost sections, and it works for me:
Somewhere on the python path, there
Thanks for your help, Russ. I updated mod_python (which was probably
overdue anyway), but that didn't fix the problem. I've been looking
for other signs but nothing has surfaced yet.
If anybody else can recall a similar experience, please let me know!
-rob
On Jul 18, 9:07 pm, "Russell
On 7/19/07, oggie rob <[EMAIL PROTECTED]> wrote:
>
> Please, if you've seen the same issue or have any helpful ideas to try
> to stop the error, let me know.
I think I've seen the same problem (or, at least, an analogous one).
Unfortunately, I can't provide much by way of helpful debug or
I've run into a problem that appears to be caused by multiple django
versions running on the same server. I have a preforked mod_python
installation and the problem I'm seeing is this: after using the trunk-
based application, I try to use the 0.91-based application and get a
500 error. The root
8 matches
Mail list logo
