Paul Moore wrote:
Is nobody but me seeing shades of Windows DLL hell in all of this?
Dll hell was caused because there was no versioning, and new dll
overwrote older ones, while not being compatible. If we add a versioning
checking, we won't have dll hell problem, but dependency hell,
Paul Moore wrote:
Is there anything I can do to get it applied, or should I just leave
it now for someone to decide if they care enough? (As it's a library
change, I don't know to what extent the no API changes after the next
alpha rule will apply).
I'm looking into it now - assuming it
On 19/03/2008, Guido van Rossum [EMAIL PROTECTED] wrote:
I'm currently working on an addition to pkgutil to provide this type
of function. I'm considering going a little further (adding functions
to get a file-like object, test for existence, and list available
resources, modelled on
David Cournapeau wrote:
Library versioning without API
stability just does not make sense to me.
Yes, obviously if you have library versioning you need to
use it properly in order for it to be any use.
How do you do if you have a package D
which depends on both C and B, and C needs one
