-
Notifications
You must be signed in to change notification settings - Fork 886
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
Docs - replace python with python3 for intersphinx #2429
Comments
- add python3 for intersphinx. See Pylons#2429 - minor grammar
I would just re-alias python to python3's url and add a python2 if anything needs to ref py2 explicitly. |
When I did this: 'python': (
'https://docs.python.org/3',
None), and :ref:`Python Packages <python:tut-packages>` Links still pointed at Python 2 docs. I even blasted away the build directory. Do you mean something else? |
That seems like something is still sticking around for whatever reason. |
@stevepiercy don't start tagging this pip work on the 1.7 milestone unless you're positive it's getting done in the next few weeks. |
Unless something untoward should happen to me, it will. |
I couldn't figure out why things stuck around. Were you able to replicate the issue? Could it be some obscure default in intersphinx? |
I'm pretty anti changing every reference in the doc to |
Were you able to replicate the issue? I'd like to know if it's just my setup. If you can replicate it, then I'll try a clean virtualenv to eliminate any possible stickiness. |
It was me. There's a stray |
- update intersphinx link to python3 docs - Closes Pylons#2429
Closed by #2431 |
Our intersphinx links and many other links to Python docs point to version 2.x, e.g.,
We should be using this:
...where we edit
docs/conf.py
to generate intersphinx links to the Python 3.x docs concurrently with Python 2:Some links might change between Python 2 and 3, so each rendered link needs to be tested.
Assuming all links to Python 2 can be changed to 3, then
docs/conf.py
can drop the intersphinx entry for 'python' as the final step of this task.I'm already doing this for the branch docs/easy-install-to-pip.2104 and issue #2223, but there are other docs that are outside the scope of that branch/issue that will also need review.
The text was updated successfully, but these errors were encountered: