Add information for lib3to6 to practicalities #287
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also update some prose for 2020; and for people like me who only skim headings, re-wrote the not-recommended mitigations in negative voice.
Carreau
reviewed
Aug 26, 2020
_practicalities/intro.md
Outdated
|
|
||
| It is possible to release a meta-package that has _virtually_ no code and relies | ||
| on a conditional dependency to install its actual core code on the user system. | ||
| For example, Frob-6.0 could be a meta-package which depends on | ||
| Frob-real-py2 on Python < 3.0, and Frob-real-py3 on Python ≥ 3.4. While | ||
| this approach is _doable_ this can make imports confusing. | ||
|
|
||
| ## Depend on setuptools | ||
| ## Don't depend on setuptools |
There was a problem hiding this comment.
I think this one is
Suggested change
| ## Don't depend on setuptools | |
| ## Don't depend on setuptools unless version >=24.3 |
Maybe ?
There was a problem hiding this comment.
How about Don't depend on setuptools unless version >=24.3
So that it's all a list of not to dos?
There was a problem hiding this comment.
sounds good updated suggestion.
There was a problem hiding this comment.
buildscript {
repositories {
// Gradle 4.1 and higher include support for Google's Maven repo using
// the google() method. And you need to include this repo to download
//
Carreau
approved these changes
Aug 26, 2020
hugovk
reviewed
Aug 26, 2020
_practicalities/intro.md
Outdated
| ## If your users absolutely need Py2.7 but you want to move on | ||
|
|
||
| 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. T |
There was a problem hiding this comment.
Suggested change
| it may nonetheless be possible to start using Python 3 in your codebase. T | |
| it may nonetheless be possible to start using Python 3 in your codebase. |
_practicalities/intro.md
Outdated
|
|
||
| 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. T | ||
| hrough automatic conversion using [lib3to6](https://pypi.org/project/lib3to6/) |
There was a problem hiding this comment.
Suggested change
| hrough automatic conversion using [lib3to6](https://pypi.org/project/lib3to6/) | |
| Through automatic conversion using [lib3to6](https://pypi.org/project/lib3to6/) |
_practicalities/intro.md
Outdated
| 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. T | ||
| hrough automatic conversion using [lib3to6](https://pypi.org/project/lib3to6/) | ||
| (similar to BabelJS for JavaScript) |
There was a problem hiding this comment.
Looks like it's named simply Babel: https://babeljs.io/
Suggested change
| (similar to BabelJS for JavaScript) | |
| (similar to Babel for JavaScript) |
_practicalities/intro.md
Outdated
| it may nonetheless be possible to start using Python 3 in your codebase. T | ||
| hrough automatic conversion using [lib3to6](https://pypi.org/project/lib3to6/) | ||
| (similar to BabelJS for JavaScript) | ||
| you can generate distribution files that will work on both Python2 and Python3. |
There was a problem hiding this comment.
Suggested change
| you can generate distribution files that will work on both Python2 and Python3. | |
| you can generate distribution files that will work on both Python 2 and Python 3. |
_practicalities/intro.md
Outdated
| hrough automatic conversion using [lib3to6](https://pypi.org/project/lib3to6/) | ||
| (similar to BabelJS for JavaScript) | ||
| you can generate distribution files that will work on both Python2 and Python3. | ||
| Lib3to6 is also useful if your project needs to support older versions of Python3 |
There was a problem hiding this comment.
Suggested change
| Lib3to6 is also useful if your project needs to support older versions of Python3 | |
| Lib3to6 is also useful if your project needs to support older versions of Python 3 |
Closed
myself001695
reviewed
Feb 8, 2023
| @@ -11,7 +11,6 @@ is mostly written with the assumption that software are going to stop Python 2 | |||
| support, it does perfectly apply to a package that wishes to not support Python 3, | |||
| or is stopping support for any minor version. | |||
|
|
|||
|
|
|||
| This page gathers information and links to resources allowing a library | |||
| to stop supporting an older version of Python without causing too | |||
| much disruption for users who haven't upgraded to this new version. | |||
|
(I've reported @myself001695 to GitHub for disruptive behaviour.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also update some prose for 2020; and for people like me who only skim headings, re-wrote the not-recommended mitigations in negative voice.