On Wed, Apr 7, 2010 at 2:02 PM, Michael Dirolf <[email protected]> wrote: > As a follow-up, there is a fix that went into PyMongo since 1.5.2 for > behavior similar to this. I think the OP is looking into this now, but > unless the master of PyMongo fails (against any version of modwsgi), I > think that was probably the issue...
Sorry for the noise. It appears that it was simply a bug in PyMongo 1.5.2 and a Python path error led me to believe modwsgi was related. FWIW, PyMongo master (aka 1.5.2+) works as expected everywhere. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
