-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
PEP 453: update the "Installing Python Modules" documentation #63606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Updating the "Installing Python Modules" docs in 2.7, 3.3 and default to recommend pip as the default cross-platform installer. |
Once bpo-19406 is implemented, this will need an additional update to indicate pip should be available by default in 3.4. |
Marcus Smith (aka @qwcode) has made good strides this week in getting the Python Packaging User Guide to a presentable state using the current Python docs theme. Bootstrapping: https://python-packaging-user-guide.readthedocs.org/en/latest/setup.html Accordingly, I think it makes sense to:
Thoughts? |
Alternative (more sensible) option - leave the packaging user guide hosted on ReadTheDocs, and if we decide to add a python.org subdomain for it later, that won't break any existing links. |
Larry, just a heads up that as a docs patch that isn't directly affected by the feature freeze, I likely won't get to this one until after beta 1. We'll make sure bpo-19406 and the other functional changes are resolved, though. |
After reviewing the Extending & Embedding docs recently, I think a disclaimer/redirect to the tool recommendations in the Python Packaging User Guide is appropriate there as well. Marcus also added an issue to update the distutils docs themselves: https://bitbucket.org/pypa/python-packaging-user-guide/issue/29/modernize-distutils-docs (The user guide tracker is currently serving as a metatracker for docs issues for all the core tools) |
New changeset a9f91a38a265 by Nick Coghlan in branch '2.7': |
New changeset 16b7536e418b by Nick Coghlan in branch '3.3': New changeset bc21da9727ad by Nick Coghlan in branch 'default': |
I suggest that a documentation issue cannot be a release blocker. Most people read the documentation online, and will read an update once it is available. |
Agreed, this was set to ensure Larry followed up with a "Please explain" if I'll still try to get it done for the beta, but I still have |
After attempting to fix these docs in place, I now think that's a doomed effort. However, we can't just delete them, because they still contain details that haven't been moved to the distutils module docs or the Python Packaging User Guide yet. So, what I'm planning to do instead is leave the existing Doc/install and Doc/distutils directories alone (including all their labels), changing the top level index page to point to new Doc/installing and Doc/distributing directories, and add a link to the old guides from the distutils docs page. That will keep the legacy docs available, while removing all the confusing legacy cruft from the new end user facing docs (which can now just be very brief before redirecting to packaging.python.org). |
I like the way the attached patch has worked out - I think it's complete from a structural point of view. The two missing pieces are to fill in the contents for the new Installing and Distributing guides, and those will be kept deliberately short, since we want to minimise the duplicating of content from the Python Packaging User Guide. |
"Legacy version". nice. btw, "http://packaging.python.org/en/latest/tutorial.html#creating-and-using-virtual-environments" will certainly end up including "pyvenv" command examples as well. currently just mentioned in a footnote. like I mentioned on distutils-sig, I still hope to submit a patch to move critical content from the legacy pages to library/distutils.rst at some point. also, btw, maybe you can fix this page real quick? http://www.python.org/documentation/. not sure what repo/team is managing this, but it's referencing the old HHGTP. |
Thanks for the feedback! Could you lob that last one at the pythondotorg issue tracker on GitHub ( |
And regarding moving the still-relevant content to the main distutils docs, I figure the approach in my patch is a neat hack to move that task off the |
about the hhgtp link, logged here: python/pythondotorg#268 (and already fixed) also, pyvenv is more prominent now in PUG as of latest changes (see pypa/packaging.python.org#35) |
Left some comments for Nick on Rietveld (the ever-useful CC name selection did not let me find you, so you may have not gotten a mail). |
New changeset d22ef969cb82 by Nick Coghlan in branch 'default': |
Not sure how much I'll be online tomorrow or Saturday, so I went ahead and committed what I had. The new guides definitely aren't perfect, but I think they're in acceptable shape for 3.4.0, and we can improve them in parallel with Python Packaging User Guide updates (e.g. there were some "How do I...?" questions I left unanswered because the relevant PPUG sections don't have answers yet. In particular, I completely punted on the non-PyPI distribution question for now) |
New changeset f5be4ea5b43e by Nick Coghlan in branch 'default': |
New changeset 25dc02a2acae by Ned Deily in branch 'default': |
The link to the "quick recommendations section" in the Python 2.7 and 3.3 docs is broken. It appears that the PPUG has changed the path from
to
Also, should the "Installing Python Modules" in Python 2.7.9 and 2.7.10 be the same as the one in Python 3.4? After all, pip is included in Python 2.7.9+, isn't it? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: