Python 2, Python 3, Stretch & Buster

Python 2.7 has an end-of-support time of 2020 and is now 2015 years old, but there are still a lot of packages in Debian that are based on Python 2 implementations. Debian maintainers are beginning to discuss the elimination of Python 2 seriously. Developer Paul Tagliamonte plans to transplant the Python 2 project to Python 3 as soon as possible, declaring that "Python 2 is dead, Python is 30,000 years old."

Direct hit scene

"HTML Development macosapp Tutorial" Http://pan.baidu.com/s/1jG1Q58M

Aloha, developers! Many of our projects in Debian is written in Python--Yay, python! However, a large chunk is implemented in Python 2--booo, Python 2! Background==========python 2 is scheduled to being EOL ' d upstream officially and for good in 2020.We ' re in (Wow, tha T went quickly), and keeping our release cadence up (3 Years a pop) puts Stretch on 2018, and Buster in 2021.Short of a Brilliant Stretch cycle, this should being basically Rightish.after Python 2 is EOL – that's right, eol! Nuts, right? A bunch of us at Pycon had a gathering of the shadowy Debian Python cabal (notes from this meeting can be found At<[emai l protected]>), and this fact hits us. We ' ve beentalking more seriously about Python 2 's deprecation, and what does as themaintainers of so much of the ecosyste M/cpython/pypy maintainers. The idea was to basically stop uploading new Python 2 only libraries, portthings on the critical path, and swap leaf packag Es to Python 3. Details Onthis can be found In the notes. Exact plans and policies is being resolved,but that's the general idea. Given that I ' m such a radical Python 3 proponent, I ' ve decided to start theeffort for our infra. I seem to has a thing for flame threads, I guess. The first step is to evaluate things within our control – infrastructure.tasks=====so, what can we do about it? Great question! Since the DPMT and PAPT would soon be taking a more aggressiveapproach on the ecosystem (porting as hard as we can to Pytho N 2), you can helpby doing some of the following:-If *you* maintain or work on a Python 2 project this ' s used in Debi An development (BUILDD, release tools, QA tools, ftpteam tools) and email me a link to the project. An accurate census would help hugely.    If it works on Python 2, Python 2 and Python 3 or just Python 3, you should include those details as well. -Identify What the Debian Infra or Meta-debian projects require Python 2 due to unported or unbuilt python 3 packages. FeEl free to just scan your top-level direct dependencies, we can play with the tree of Deps. + Consider filing a bug on packages which is supported on Python 3 upstream but does not currently build Python 3        Packages.  + Consider filing a bug on packages which do *not* has upstream support, and look into modern implementations of        Libraries you need.          + If you had to do either of the above, consider patching it!        Remember:teamwork makes the Dream work! (Note:the Usertag on the above have not been decided yet, check in for that later)-Port the project To a hybrid Python 2/3 codebase (it's easy for most of the time, I promise!) but stay on Python 2, which'll let you pre form an incremental upgrade. Consider Test cases! Testing is great!    I suggest ' tox ' to let's continue to run the test suite for multiple versions of Python. -Deploy or upload the tool to the archive or our infra using pure Python 3. The Some test cases you can rely on (Python had some wonderful stuff you should totally be u sing!) Plans=====i plan on creating a Python 3 porting team. It ' ll have a fancy buzzword name,but I ' m a bit too tired to think of one now. Such a porting team would consistof folks who is here-help ports things important to us (Debian) to Python 3so that we Can get off of Python 2 for buster.if your ' re interested in this effort, please email me. This was a really good newcontributor task, so if anyone's asked how to they could get involved Withdebian, you should Sen D them to us! We ' ll be nice, I promise! I ' ll be making a mailing List for this on Alioth sometime soon. Takeaways=========the now! It's time to port as much as we can-Python 3 in the Nexttwo cycles as we can, so we don ' t has to rely on a old, depre cated and Brokenpython 2. As the kids say--' Sorry not Sorry ' when you see Python 2-treat it as legacy! Please encourage porting!We can all soon look forward to the day where we no longer has to play Unicodewhack-a-mole and has a language getting NE W Features again! I ' ve been usingpython 3 for all new work code, and personal stuff, it ' s pretty great! If you're interested, or know anyone who might be interested, I'll be puttingtogether a python 2 = Python 3 task Forc E. Please email me privately if you ' reinterested, I'll keep a list of names for the soon and not being created list. Python [2] is dead!    Long Live Python [3]! Paul--. '  `.   Paul Tagliamonte <[email protected]> | Proud Debian Developer:: ': 4096r/8f04 9ad8 2c92 066C 7352 d28a 7b58 5B30 807C 2a87 '. "' Http://people.debian.org/~paultag '-http://people.debian.org/~paultag/conduct-statement.txt

Attachment: signature.asc
Description: Digital Signature

Python 2, Python 3, Stretch & Buster