There will come a point very soon when working on Python 2 code is about as attractive as working on Perl (sorry, Perl afficionados!).
So this effort will get us to the point where heavily-developed things run in Python 3, less-heavily-develped stuff is at least "ready to port" (ensured via various source-code analysis tools), and there's a long tail of stuff still running in Python 2 that is unlikely to be touched anyway. Dustin 2017-11-13 13:21 GMT-05:00 Gregory Szorc <g...@mozilla.com>: > On Mon, Nov 13, 2017 at 5:22 AM, Ted Mielczarek <t...@mielczarek.org> wrote: >> >> On Sun, Nov 12, 2017, at 12:12 PM, David Burns wrote: >> >> I am not saying it should but if we have a requirement for python 3, we >> are also going to have a requirement for py2 to both be available for local >> development. >> >> >> Correct, and as far as I know that's the plan of record. As Greg said, >> we're not going to convert all the code in the tree to run under Python 3 >> immediately, and we will likely have some laggards that stay on Python 2 for >> a while. We do have folks working on making the in-tree Python code Python 3 >> compatible (thanks ahal for leading that effort!), so hopefully we could get >> to a point where Python 3 is used for most things but it's a fair amount of >> work. >> >> We'd simply like to have Python 3 available for some code that would >> benefit from its faster execution speed and things like asyncio. Greg >> floated the idea of doing moz.build evaluation in Python 3 last week, which >> seems like a great candidate. > > > Yes, the plan is to require Python 2.7 *and* Python 3 for an indeterminate > amount of time. There's absolutely no way we can do a flag day conversion of > all the Python in the repo. Unless we make porting an organizational > priority (which I don't foresee happening because there is little to gain > from touching code not under active development), porting will take years > and will likely extend beyond 2020. > > What we can do is enable people to write new code targeting Python 3 and > port existing code that would benefit from Python 3. That's my main goal for > establishing this requirement. > > _______________________________________________ > dev-builds mailing list > dev-builds@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-builds > _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
