On Jun 06, 2016, at 01:02 PM, Łukasz Langa wrote: >There’s a problem with this approach. It will force people to write >deprecated code because you never know if your library is going to run on >3.5.0 or 3.5.1. Barry, Ubuntu wily, xenial and yakkety currently package >3.5.0 or 3.5.1. When 3.5.2 is going to get released, are they going to get >it? I’m pretty sure wily isn’t and yakkety is but just wanted to confirm; >especially with xenial being an LTS release.
Matthias and I talked briefly about this at Pycon. We want to get 3.5.2 into Ubuntu 16.04.1 if it's released in time. 16.04.1 is currently scheduled for July 21st [1] so if Larry keeps with his announced schedule that should work out[2]. Obviously it would make it into Yakkety too. It's not worth it for Wily (15.10) since that EOLs next month. Cheers, -Barry [1] https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule [2] https://mail.python.org/pipermail/python-dev/2016-April/144383.html
pgpI_nU_ukCmy.pgp
Description: OpenPGP digital signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
