[issue12298] Sphinx glitch in library/functions

Éric Araujo added the comment: No problem, what counts is that our documentation and code get better for our users, not my ego :) -- ___ Python tracker ___

[issue12298] Sphinx glitch in library/functions

Sandro Tosi added the comment: Oh sorry Éric, I completely oversaw there was an issue associated with the cset - i'll pay more attention next time! -- ___ Python tracker ___ __

[issue12298] Sphinx glitch in library/functions

Éric Araujo added the comment: Sandro ported to 2.7 in 07b3fc67bf45. Thanks! If I may make two remarks: - Please duplicate commit messages from 3.2 and 2.7: it makes it easier to understand what a changeset is about without having to hunt. (This does not apply to 3.3 as the changeset with

[issue12298] Sphinx glitch in library/functions

Éric Araujo added the comment: > I agree that all table entries should link to the entry in the same file. This is fixed in 3.2 and 3.3, with a bit of reST kludgery. I’ll backport to 2.7 if there is no negative feedback. > range() definitely needs a forward reference to 4.6 sequence types >

[issue12298] Sphinx glitch in library/functions

Roundup Robot added the comment: New changeset 7a05cb3beddf by Éric Araujo in branch '3.2': Fix a few links in the table of built-in functions (#12298) http://hg.python.org/cpython/rev/7a05cb3beddf New changeset 58dd7addef3a by Éric Araujo in branch '3.2': Add links from library/functions to ot

[issue12298] Sphinx glitch in library/functions

Changes by Ezio Melotti : -- keywords: +easy stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue12298] Sphinx glitch in library/functions

Terry J. Reedy added the comment: I agree that all table entries should link to the entry in the same file. dict() and set() also jump to CH. 4, in addition to memoryview and frozenset. Others all work properly. The entries for classes should generally have a link to their section in '4. Bui

[issue12298] Sphinx glitch in library/functions

Éric Araujo added the comment: Sounds like the easiest solution that could work, thanks. I’m on it. -- assignee: docs@python -> eric.araujo status: closed -> open ___ Python tracker __

[issue12298] Sphinx glitch in library/functions

Georg Brandl added the comment: You can put an anchor and use :ref:. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue12298] Sphinx glitch in library/functions

Éric Araujo added the comment: Certainly. I tried using `.memoryview` without success. How would you do it? -- ___ Python tracker ___ _

[issue12298] Sphinx glitch in library/functions

Georg Brandl added the comment: Well, then a different way of linking to them must be used. -- ___ Python tracker ___ ___ Python-bugs

[issue12298] Sphinx glitch in library/functions

Éric Araujo added the comment: memoryview and frozenset do have a small entry in library/functions, and the links at the top of the file are meant to jump to entries in the same file. -- ___ Python tracker __

[issue12298] Sphinx glitch in library/functions

Changes by Georg Brandl : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue12298] Sphinx glitch in library/functions

Georg Brandl added the comment: This is not a Sphinx glitch: that's where these classes are defined. (Plus, dependencies work the other way round.) -- dependencies: -Fix referencing of built-in types (list, int, ...) nosy: +georg.brandl ___ Python

[issue12298] Sphinx glitch in library/functions

Changes by Ezio Melotti : -- dependencies: +Fix referencing of built-in types (list, int, ...) ___ Python tracker ___ ___ Python-bugs-

[issue12298] Sphinx glitch in library/functions

New submission from Éric Araujo : In the summary table at the top of library/functions, the links for frozenset and memoryview do not jump to the definition down in the same file, but link to stdtypes. -- assignee: docs@python components: Documentation messages: 137997 nosy: docs@pytho