On Wed, Aug 09, 2006 at 12:12:22AM +0000, John J Lee wrote: -> On Tue, 8 Aug 2006, Titus Brown wrote: -> [...] -> > -> this reason -- the setuptools multi-version support doesn't address the -> > -> problem of multiple versions being used *in the same process*. This isn't -> > -> a problem with applications that depend on specific versions of libraries, -> > -> but it is a problem with libraries that depend on other libraries. I -> > -> wonder if PJE might be sympathetic to this problem... -> > -> > I'm pretty sure that the import semantics in Python simply don't allow -> > for this. -> -> Nonsense :-) -> -> Where there's a will, there's a way, and there are plenty of ways in -> Python, I'm sure. (Some of them quite ugly, no doubt, but I hear that -> anything related to Python imports is currently a bit ugly if you look -> closely enough.) How about name mangling + an import function implemented -> using module imp?
There's an underlying caching layer that cannot currently be manipulated in CPython. That would be the area to worry about, I think. It's certainly caused me problems in the past... --titus _______________________________________________ twill mailing list [email protected] http://lists.idyll.org/listinfo/twill
