On Wed, Apr 8, 2009 at 12:11 PM, Lennart Regebro <rege...@gmail.com> wrote: > On Wed, Apr 8, 2009 at 12:03, Tarek Ziadé <ziade.ta...@gmail.com> wrote: >> But I will not work in flame-threads anymore on my side. > > Probably a good idea. > > The only thing I'm worried about is the fact that you are proposing > both to remove and add things to distutils. Although backports will be > available, how will this work? If I use a new version of distutils, > and somebody uses 2.5 to install my package, how will he know how to > fix the errors that appear? >And how will my 2.6 package work under 2.7 > if you remove backwards compatibility?
I don't think we want to break any current feature in 2.7, we will probably just display deprecation warnings and keep them, then wait until the next python version. And if someone want to use your package, that uses a new feature that is not present in 2.5/2.6, he will need to install the backport. Some good practice will be needed for package developers for this (maybe a kind error message) Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
