This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Bernát Gábor, docs@python, gvanrossum, levkivskyi
Date 2017-08-22.22:27:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 you generate the docs for your project (that references the Python docs)? Finally, are there other objects in the typing for which this is a problem? (I guess I could answer this myself once I understand how intersphinx decides whether something is a class or data.)

I also think this is somewhat unfortunate, because it seems that whenever something is changed from "class" to "data" or vice versa, intersphinx will be confused, even though it's easy to give examples where such a change could be backwards compatible.
Date User Action Args
2017-08-22 22:27:47gvanrossumsetrecipients: + gvanrossum, docs@python, levkivskyi, Bernát Gábor
2017-08-22 22:27:47gvanrossumsetmessageid: <>
2017-08-22 22:27:47gvanrossumlinkissue31024 messages
2017-08-22 22:27:47gvanrossumcreate