On 15 February 2011 16:56, Daniele Varrazzo <[email protected]> wrote: > On Feb 15, 1:54 am, Graham Dumpleton <[email protected]> > wrote: > >> To clarify for those not following this issue, this is a Windows >> specific issue and so if you are using a UNIX type system you can >> ignore it. > > Yes, sorry: I missed the "windows" part in the description. > > For more information about the issue, there is plenty of details in > the psycopg ticket #20 <http://psycopg.lighthouseapp.com/projects/ > 62710/tickets/20>.
I take it from reading that description that it will not help for mod_wsgi.so to embed manifest with reference to the DLL as needs to be either in the executable or the originating DLL. So, seems that nothing that I can do in mod_wsgi itself to avoid distinct extension modules from needing to reference the DLL themselves. Does this also mean that another extension module, eg., PILs _imaging.so, if it requires it would still in parallel need to reference it in its manifest even though pyscopg2 may have already done that and is loaded? Graham -- 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.
