[3.7] bpo-35472: Allow sphinx 3.6.6 to build Python 3.7 documentation.#11192
[3.7] bpo-35472: Allow sphinx 3.6.6 to build Python 3.7 documentation.#11192JulienPalard merged 1 commit intopython:3.7from
Conversation
JulienPalard
requested review from
a team,
1st1,
asvetlov,
ericvsmith,
gpshead,
gvanrossum,
ilevkivskyi,
rhettinger,
skrah and
terryjreedy
as code owners
|
Why so many commits are affected? |
|
Apparently, Julien (correctly) branched off of 3.7 in his clone but left the base branch on github's PR form. That makes all differences between 3.7 and 3.8 part of the PR. When he changed the base branch to 3.7, those all went away. Julien, how did you do that without closing and opening another PR? For me, the merge target on the files page is read-only. |
|
@terryjreedy Yes I had an issue (I was on very low bandwidth at the time, in a train), while opening the PR, the select box to change the base was unresponsive, so I opened the issue, and then was able to change it. You can change the base by clicking the "Edit" button next to the title. |
|
Should I tag the branch |
JulienPalard
changed the title
|
I believe that if you deleted |
|
@terryjreedy I did the other way around: I added the [3.7] because bedevere was complaining. |
5 participants
This is not a backport, nor a change I'm willing to do on master, this is intentionally only for the 3.7 branch, so requirements will look like this:
https://bugs.python.org/issue35472