-
Notifications
You must be signed in to change notification settings - Fork 864
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
Comments
In case you want to update the |
As a reminder, we are not yet using setuptools, so we don't have the However, I do see some value in using the mechanism in that script to upload something redirecting people to the new docs. |
According to pypa/setuptools@7f81445 the |
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:
|
So I successfully got the
AFAICT, we can only "delete" the existing documentation. There are no options to update in any way. |
Ha, man, I love Python, but some of the PyPI decisions are weird. |
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.
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.
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. |
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.
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.
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.
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.
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:
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?The text was updated successfully, but these errors were encountered: