Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add lib3to6 #285
Add lib3to6 #285
Comments
|
My feeling: if |
|
Would you feel comfortable if I add a section to the Reccomended Mitigations Something to the effect of this: If you have users that still depend on Python 2.7 and you cannot drop support yet, it may nonetheless be possible to start using Python 3 in your codebase. Through automatic conversion using lib3to6 (similar to BabelJS) you can generate distribution files that will work on both Python2 and Python3. |
|
In PR #286 -- look it over and see if it sounds good? |
|
@mscuthbert isn't that already merged? |
|
@mbarkhau -- the placement on the front page is done, but the Recommended Mitigations addition is in the new PR. |
|
Ahh, I looked throught the open ones. I guess you meant #287. LGTM |
I have written a library called lib3to6.
I am unsure of the most appropriate way to add lib3to6 to python3statement.org, since a large part of the purpose (though not the whole purpose) of lib3to6 is to help with backwards compatibility for Python 2.7. In that sense, the project would not be appropriate to add to the list of participating projects.
I do feel however (biased as I am) that for some libraries, lib3to6 makes it very cheap to support Python 2.7. The most recent example where I did this was with the pretty-traceback package.
I assume there are at least some packages that currently support both Python2 and Python3, which could benefit from this kind of automated compilation/transpilation, but who are not aware of lib3to6 as an option. They could start to use many of the Python3 language features and associated tooling such as mypy, remove much of the boilerplate such as
from __future__ import print_functionfrom their source repository and nonetheless retain support for Python2.7 if that is important to their users. In this way, lib3to6 can reduce the burden on maintainers to continue supporting Python2.7 if they still need to.If/how to add lib3to6 to python3statement.org, I'm not sure. Perhaps a mention on the practicalities page would be appropriate.