[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Ivan Levkivskyi added the comment: TBH, I think this is a Sphinx problem, not a Python problem. And concerning ``Tuple`` being an actual class I think this is an implementation detail, so that I am closing this as "won't fix". -- resolution: -> wont fix stage: -> resolved status:

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Guido van Rossum added the comment: OK, I think Sphinx is way too complicated for its own good, and it's arguably not the fault of Python's documentation that this doesn't work for you. I would like to close this issue as "won't fix", except... in a sense Tuple actually *is* a class, since

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Bernát Gábor added the comment: I suppose when the python.org documentation is generated the objects.inv file gets generated with it (I did not found exactly this piece of code here though). When Sphinx runs, it's intersphinx plugin goes out to python.org, downloads the objects.inv, decodes

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Guido van Rossum added the comment: Thanks, I am a little closer to understanding now. > once intersphinx looks at the Tuple during documentation generation it > deduces it actually is of type class How does intersphinx deduce this? Also, does it run when we generate the Python docs, or when

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Ivan Levkivskyi added the comment: > For the end user the fact that this is a class is still hidden I am not sure what you mean by this, but with your PR the rendered docs will literally say ``class typing.Tuple``. > We should probably add a unit test that makes sure all runtime "type"

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Bernát Gábor added the comment: so here's the problem in detail: Intersphinx (http://www.sphinx-doc.org/en/stable/ext/intersphinx.html) is a built in Sphinx plugin that allows to link to documentation of other projects in your own documentation. For example when specifying the argument of a

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Guido van Rossum added the comment: Before I spend more time reviewing your patch, can you please explain what you mean by "sphinx fails to find these"? Is there a particular dead link on docs.python.org or a specific query you typed in the search box that failed to find the definition of

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Changes by Roundup Robot : -- pull_requests: +3219 ___ Python tracker ___

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Ivan Levkivskyi added the comment: Bernát, I would recommend asking this on Sphinx tracker (I also assigned this to docs@python since this seems to be a purely documentation issue). https://github.com/sphinx-doc/sphinx -- assignee: -> docs@python components: +Documentation nosy:

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Bernát Gábor added the comment: how can we find it out? -- ___ Python tracker ___ ___ Python-bugs-list

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Ivan Levkivskyi added the comment: > Do you have any idea? Unfortunately no. -- ___ Python tracker ___ ___

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Bernát Gábor added the comment: I would need to know who and how maintains the https://docs.python.org/3.6/objects.inv file. Do you have any idea? -- ___ Python tracker

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Ivan Levkivskyi added the comment: > This ticket is about fix objects.inv to have the Tuple in the correct bucket. If you know how to do this without breaking the python docs system (so that Tuple and Callable will not have a "class" prefix on https://docs.python.org/3/library/typing.html)

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Bernát Gábor added the comment: I agree we should not advertise the type. However, whatever its type is should be in sync in what we put inside objects.inv. That's sort of a encoded binary black box for the user; the Sphinx tool included. It maps standard library elements to URLs. This ticket

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

Ivan Levkivskyi added the comment: The fact that it is a class is an implementation detail and may change before Python 3.7 beta (situation is the same for Callable). Guido explicitly doesn't like to "advertise" it as a class yet. Unless he changed his mind, I would propose to close the

[issue31024] typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv

New submission from Bernát Gábor: Hello, typing.Tuple is class but is defined as data inside https://docs.python.org/3.6/objects.inv which means that Sphinx fails to find these. Thanks, -- components: Library (Lib) messages: 299048 nosy: Bernát Gábor priority: normal severity: