
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 version of one package A, and B another one?
If they really do need different versions, this is insoluble. If they can actually use the same version because it's compatible enough, it may be necessary to make Python smart enough to notice that they're symlinks to the same file and only import it once. Or maybe something does need to be added to the language that understands version numbering, compatibility rules, etc. as I suggested in another post. -- Greg