Skip to content
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

Switch documentation host #601

Closed
waylan opened this issue Nov 30, 2017 · 7 comments
Closed

Switch documentation host #601

waylan opened this issue Nov 30, 2017 · 7 comments
Labels
docs Related to the project documentation.

Comments

@waylan
Copy link
Member

waylan commented Nov 30, 2017

As pointed out in #554 I didn't update the publicly hosted docs with the 2.6.9 release. I now remember that I tried but ran into problems uploading the docs. Then I ran out of time and forgot to come back to it later.

In any event as I explain here:

The homepage at http://pythonhosted.org states:

To upload documentation, go to your package edit page (http://pypi.python.org/pypi?%3Aaction=pkg_edit&name=yourpackage), and fill out the form at the bottom of the page.

However, there is no longer a form at the bottom of the edit page for uploading documentation. Instead I only see:

If you would like to DESTROY any existing documentation hosted at http://pythonhosted.org/ProjectName Use this button, There is no undo.

[Destroy Documentation]

I also went to pypi.org and logged in there. But I don't see any options for editing my projects or uploading documentation on that site.

So, how do I upload an update to my documentation?

In addition to the above, pythonhosted seems to have been rather flakey lately. I'm considering switching to GitHub Pages (probably using Organization Pages so the URL would be https://Python-Markdown.github.io). I'm not interested in readthedocs as they require you to have them build your docs and then we cannot use our own tooling to build our own docs (they do support MkDocs, but an older version with less than complete support for Markdown extensions, which is a nonstarter IMO). Any thoughts?

@mitya57
Copy link
Collaborator

mitya57 commented Dec 1, 2017

In case you want to update the pythonhosted.org page: last time I tried, setuptools’ upload_docs command worked. This means you can either use POST requests directly (see the implementation) or adapt that command to use your custom tarball instead of a Sphinx-generated one.

@waylan
Copy link
Member Author

waylan commented Dec 1, 2017

As a reminder, we are not yet using setuptools, so we don't have the upload_docs command available. We could certainly switch over (the md3 branch already has been), but that doesn't help for a previous release.

However, I do see some value in using the mechanism in that script to upload something redirecting people to the new docs.

@waylan
Copy link
Member Author

waylan commented Dec 1, 2017

According to pypa/setuptools@7f81445 the upload_docs command is deprecated (with a warning suggesting using RTD) and a separate comment indicates that the new "Wharehouse" (pypi.org) will not ever support hosting documentation. Unfortunately, nothing in the commit references a source (like perhaps, an official announcement?), but this isn't the first I've see that suggests pythonhosted.org may be going away completely when the switch from pypi.python.org to pypi.org is complete. My point is that we should switch now before we can't change anything on pythonhosted.org.

@waylan
Copy link
Member Author

waylan commented Dec 1, 2017

After some more searching, AFAICT, the current state of affairs is explained in the discussion in pypi/warehouse#582 (see also pypi/legacy#672 which links to some mailing list discussions). What is clear is that pythonhosted.org will be going away. What's not clear is if we can still update anything there (some comments seem to indicate not).

Given the state of things, I'm proposing the following plan:

  1. First, prepare and upload docs to an alternate host (GitHub Pages via MkDocs?)
  2. After the alternate host is live (and links are updated where we can), explore updating the existing docs on pyhtonhosted.org to redirect people to the new docs.
  3. Finally, at some point in the future, delete the docs from pythonhosted.org.

@waylan
Copy link
Member Author

waylan commented Dec 2, 2017

So I successfully got the upload_docs script to run. However, the upload did not succeed. This was the output:

running upload_docs
Upload_docs command is deprecated. Use RTD instead.
Submitting documentation to https://pypi.python.org/pypi/
Upload failed (410): Gone (This API has been deprecated and removed from legacy PyPI in favor of using the APIs available in the new PyPI.org implementation of PyPI (located at https://pypi.org/). For more information about migrating your use of this API to PyPI.org, please see https://packaging.python.org/guides/migrating-to-pypi-org/#uploading. For more information about the sunsetting of this API, please see https://mail.python.org/pipermail/distutils-sig/2017-June/030766.html)

AFAICT, we can only "delete" the existing documentation. There are no options to update in any way.
Unfortunately, it seems that they skipped from step 1 to step 5 of the roadmap without bothering with steps 2, 3, & 4.

@facelessuser
Copy link
Collaborator

Ha, man, I love Python, but some of the PyPI decisions are weird.

waylan added a commit to waylan/markdown that referenced this issue Dec 2, 2017
This is a work in progress.

I merged in 6f87b32 from the md3 branch. That branch has all of the
extension docs removed, so they haven't been converted yet. And I
only resolved conflicts and updated mkdocs.yml to the current MkDocs
format.

Addresses Python-Markdown#601.
@waylan waylan mentioned this issue Dec 2, 2017
waylan added a commit to waylan/markdown that referenced this issue Dec 2, 2017
This is a work in progress.

I merged in 6f87b32 from the md3 branch. That branch has all of the
extension docs removed, so they haven't been converted yet. And I
only resolved conflicts and updated mkdocs.yml to the current MkDocs
format.

Addresses Python-Markdown#601.
@waylan waylan added the docs Related to the project documentation. label Dec 5, 2017
@waylan waylan closed this as completed in b62dded Dec 7, 2017
@waylan
Copy link
Member Author

waylan commented Dec 7, 2017

For the record, the documentation is now available at https://python-markdown.github.io/.

I used to be able to edit a package's meta-data right in PyPI. Apparently, now the only way to do so is to upload a new release. Therefore, even after all that work, PyPI still points to pythonhosted.org. Guess we need to roll a new release to finalize this.

I'll delete the old docs after PyPI no longer points to them.

@waylan waylan reopened this Dec 7, 2017
waylan added a commit to waylan/mkdocs that referenced this issue Dec 7, 2017
Python-Markdown has moved its documentation to
https://python-markdown.github.io/. See Python-Markdown/markdown#601
for details. The docs now point to the new location.

The Python-Markdown GitHub repo was also moved to
https://github.com/Python-Markdown/markdown so any links to the repo
have been updated as well.
waylan added a commit to mkdocs/mkdocs that referenced this issue Dec 7, 2017
Python-Markdown has moved its documentation to
https://python-markdown.github.io/. See Python-Markdown/markdown#601
for details. The docs now point to the new location.

The Python-Markdown GitHub repo was also moved to
https://github.com/Python-Markdown/markdown so any links to the repo
have been updated as well.
waylan added a commit to waylan/markdown that referenced this issue Dec 7, 2017
This version was released to force PyPI to point to the new docs location.
Closes Python-Markdown#601. The old PyPI hosted docs can be deleted after this.
waylan added a commit that referenced this issue Dec 7, 2017
This version was released to force PyPI to point to the new docs location.
Closes #601. The old PyPI hosted docs can be deleted after this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Related to the project documentation.
Projects
None yet
Development

No branches or pull requests

3 participants