On Jul 24, 12:15 pm, oggie rob <[EMAIL PROTECTED]> wrote: > > One problem that could arise is if, even in different sub interpreters, > > two Django instances separately tried to use version 1 and 2 of pyscopg. > > This is because the Python wrappers for one wouldn't match the loaded > > C extension module since it is named the same for both versions and > > would only be loaded once for the whole process. > > Are you sure this would happen? If that were the case I would have > expected my box to blow up by now. I wonder if the extensions are > named differently, or if the namespace avoids the problem (i.e. > "import psycopg" vs "import psycopg2")? I haven't seen any problems so > far (cross fingers).
If the C extension module resides within the package, ie., thus is within parent package namespace, then probably wouldn't occur, ie., both would be loaded. I would though still be concerned if the two different versions of the C extension use the same C symbol names for certain global non static data. If this occurs the dynamic linker may in the second loaded module, actually use global data variables from the first to be loaded module rather than its own. If the way such global data was initialised was different to how expected, it may feasibly cause subtle strange problems with one more of the other. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
