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

[3.6] bpo-30052: Always regenerate cross-references (GH-1339) #1921

Merged
merged 1 commit into from
Jun 6, 2017

Conversation

ncoghlan
Copy link
Contributor

@ncoghlan ncoghlan commented Jun 2, 2017

  • bpo-30052: Always regenerate cross-references

The patch for bpo-30052 changed the preferred link target
for :func:bytes and :funcbytearray references to be the
respective type definitions rather than the corresponding
builtin function entries.

This patch changes the daily documentation builds to disable
the output caching in Sphinx, in order to ensure that
cross-reference changes like this one are reliably picked
up and applied automatically after merging.
(cherry picked from commit 7a82f9c)

* bpo-30052: Always regenerate cross-references

The patch for bpo-30052 changed the preferred link target
for :func:`bytes` and :func`bytearray` references to be the
respective type definitions rather than the corresponding
builtin function entries.

This patch changes the daily documentation builds to disable
the output caching in Sphinx, in order to ensure that
cross-reference changes like this one are reliably picked
up and applied automatically after merging.
(cherry picked from commit 7a82f9c)
@ncoghlan ncoghlan changed the title bpo-30052: Always regenerate cross-references (#1339) [3.6] bpo-30052: Always regenerate cross-references (GH1339) Jun 2, 2017
@ncoghlan ncoghlan changed the title [3.6] bpo-30052: Always regenerate cross-references (GH1339) [3.6] bpo-30052: Always regenerate cross-references (GH-1339) Jun 2, 2017
@Mariatta Mariatta merged commit 798cfb2 into python:3.6 Jun 6, 2017
@ncoghlan ncoghlan deleted the backport-7a82f9c-3.6 branch March 30, 2018 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants