Although we are reaching a tipping point where a lot of projects are announcing the end of Python 2 support as of a certain date.
Whatever is in the latest version of Python 3 when it will be considered a sane decision to have a Python 3-only library will be considered standard. On Sun, Aug 21, 2016 at 5:28 PM, Donald Stufft <don...@stufft.io> wrote: > > On Aug 21, 2016, at 5:18 AM, Sylvain Corlay <sylvain.cor...@gmail.com> > wrote: > > With this reasoning, nothing should ever be added to the standard library. > > > > Packaging is a bit different than other things because the network effect > is much more prominent. There’s no real way to say, install a backport if > you need one, you just have to kind of wait until every has upgraded which > is unlikely other bits of the standard library. In addition, people writing > projects in Python that are designed to be distributed, they tend to need > to work across many versions of Python, while someone writing a project for > themselves only need to worry about whatever version of Python they are > deploying to. So while the new statistics module is, even without a > backport, immediately useful to people developing their own projects for a > recent version of Python, something in distutils is not useful for package > authors until it is the *minimum* version of Python they support. > > This generally makes the reward for changing distutils very small, > particularly with the 3.x split because very few authors are willing to > drop 2.7 much less go straight to 3.6 (or whatever) and for people making > their own, internal projects, distutils isn’t generally used a whole lot > there either. > > — > Donald Stufft > > > >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
