On Wed, Oct 14, 2009 at 4:19 PM, kiorky <kiorky@cryptelium.net> wrote:
kiorky a écrit :
[]
This may be quite current even if it's not a good habit to have circular dependencies between distributions. Imagine that.
B(0.7) -> A(0.6). A(0.6) -> B(0.7).
Can i have the same namespace "ns" shared between the twice distributions with both the setuptools namespaces implementation (A) and the pkg_util's one (B)? "Have" mean that i can import ns in both distributions.
Not sur to follow this. Is that two different working sets ?
So, if: * I have old distributions with C code even not declaring they are relying on setuptools, installing with the 0.6 code automatically. * I have entry points and namespaces from 0.7 available to import in 0.6 and vice-versa.
I will see no more objections.
Another related thing, as i read the pep376 implementation, it may be good and easy to provide some wrappers to some setuptools very used objects like WorkingSet or Environment as similary code is already implemented to smoothly migrate existing code.
In Distribute 0.7.x we will provide new tools, and we won't try to provide backward compat. Projects that whish to use Distribute 0.7 features will have to switch to it I guess, so, depending on the project, it can use various strategy to migrate its code. Tarek