On Thu, Aug 18, 2011 at 5:17 AM, Fred Drake <fdrake at acm.org> wrote: > On Wed, Aug 17, 2011 at 11:00 PM, Nick Coghlan <ncoghlan at gmail.com> wrote: >> It's actually for the same reason that unittest changes are backported >> under the unittest2 name - the distutils2 name can be used in the >> future to get Python 3.4 packaging features in Python 3.3, but that >> would be difficult if the backport shadowed the standard library name. > > Ah, yes... the old "too bad we stuck it in the standard library" problem. > > For some things, an easy lament, but for foundational packaging-related > things, it's hard to get around. Yeah exactly. And the good thing about packaging and distutils2 is that for the regular usage (package your project) you don't type any code, just define options in setup.cfg. IOW there's no "import packaging" or "import distutils2". Cheers Tarek > > > -Fred > > -- > Fred L. Drake, Jr. <fdrake at acm.org> > "A person who won't read has no advantage over one who can't read." > --Samuel Langhorne Clemens > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com > -- Tarek Ziadé | http://ziade.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4