On Nov 15, 2008, at 4:53 PM, Randy Syring wrote:
> > When I run the exact same code using PyISAPIe, I get the following log > file, which shows many exceptions all propagating up to my application > and hosing it: Reading Graham's comments on threading: http://groups.google.com/group/modwsgi/tree/browse_frm/thread/75463f392f3ff5d9/5275a98acfecb1fe?rnum=1&q=threading.local&_done=%2Fgroup%2Fmodwsgi%2Fbrowse_frm%2Fthread%2F75463f392f3ff5d9%2F4e10cfbb87794f2c%3Flnk%3Dgst%26q%3Dthreading.local%26#doc_6f269158c4c1ae3f There are obviously fine grained details when interfacing native C code with Python threads. Note that the issue he's discussing there involves the state of a threading.local() being *lost*, which would not cause the problem we're seeing. We're seeing a mismatch between the ID of the thread and the threading object itself which is a much more severe situation. I've looked into PyISAPIe. Suffice to say this seems to be an extremely new project. Their homepage is blank: http://pyisapie.sourceforge.net/ Bug tracker is empty: http://sourceforge.net/tracker/?group_id=142454 but they do have a google group, with 20 members and about 40 posts: http://groups.google.com/group/pyisapie/topics It would be worthwhile to ask about threading.local() there, but it seems very possible that some interaction on their end is incompatible with threading.local(). I certainly wouldn't trust native python- embedded code with that low of a user base on a production site. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
