Great. I would raise it as a red flag with pymssql developers if still conversing with them as it would perhaps be a regression if the module now only works in Python main interpreter and not sub interpreters. Give them a link to that section in documentation for a partial explanation of issue.
Graham On 14/11/2013, at 9:09 AM, Frederick Yankowski <[email protected]> wrote: > Sorry, I conflated WSGIApplicationGroup with WSGIProcessGroup. > > Anyway, after I set WSGIProcessGroup to %{GLOBAL} the problem is gone. > _mssql.connect() no longer hangs. I installed the latest pymssql package > with pip and that too works fine. > > So, thank you very much. > > -Fred > > On Wednesday, November 13, 2013 3:38:25 PM UTC-6, Graham Dumpleton wrote: > I also didn't say WSGIProcessGroup. I said WSGIApplicationGroup. Anyway, set > it as explained and see what happens. > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/groups/opt_out.
