This repository arose from the discussion of some proposed amendments to our guidance for redistributors around handling the /usr/bin/python symlink on Unix-like systems: python/peps#315
@warsaw pointed out that the "Migrations Notes" section in that PEP had kind of become a miscellaneous grab bag of potential problems to consider, rather than providing a clear and crisp definition of what we considered reasonable for redistributors to do.
We figure that by creating a separate "Redistributor's Guide", we'll have a place to document the things that both community and commercial redistributors will need to pay attention to in order to provide a good Python developer experience for their users:
- expected command availability (
python vs pythonX vs pythonX.Y)
- binary ABI compatibility (especially in Python 2.7, with the narrow/wide distinction)
- virtual environment and package management support
- ensuring OpenSSL is kept up to date (and responsiveness to security issues in general)
As far as the overall guide structure goes, I'd like to adopt the basic layout now used in https://packaging.python.org/, where all content is classified as either a Tutorial, a Guide, or a Discussion.
While the "Tutorials" and "Guides" sections would likely start out empty, and we'd just have a single "Discussion" of issues to consider when managing a platform's migration from Python 2 to Python 3, I still think that's a good way of framing the different kinds of article that may be appropriate.
This repository arose from the discussion of some proposed amendments to our guidance for redistributors around handling the
/usr/bin/pythonsymlink on Unix-like systems: python/peps#315@warsaw pointed out that the "Migrations Notes" section in that PEP had kind of become a miscellaneous grab bag of potential problems to consider, rather than providing a clear and crisp definition of what we considered reasonable for redistributors to do.
We figure that by creating a separate "Redistributor's Guide", we'll have a place to document the things that both community and commercial redistributors will need to pay attention to in order to provide a good Python developer experience for their users:
pythonvspythonXvspythonX.Y)As far as the overall guide structure goes, I'd like to adopt the basic layout now used in https://packaging.python.org/, where all content is classified as either a Tutorial, a Guide, or a Discussion.
While the "Tutorials" and "Guides" sections would likely start out empty, and we'd just have a single "Discussion" of issues to consider when managing a platform's migration from Python 2 to Python 3, I still think that's a good way of framing the different kinds of article that may be appropriate.