On Wed, Apr 15, 2015 at 04:27:51PM -0400, Paul Tagliamonte wrote:
> I'd like this to have the endorsement of the team, so, does anyone object to
> me asking people to not write new tools in Python 2 only (prefer alternative
> deps or porting), and only use Python 2 in very special curcumstances or
> for legacy codebases (perhaps a pitch to move to Python 3), along with a
> note that we plan to deprecate Python 2 when upstream support is gone
> (2020), which puts us on track for two cycles (Buster)
Maybe /usr/bin/python can become a wrapper executing Python 2
(like now) but also showing
Python 2 will be deprecated in 2020 the latest.
Do not use it to write new code.
Consider helping in porting existing code.
Thanks.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150416080725.ga3...@hermes.hilbert.loc
