[issue15693] expose glossary link on hover

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.1, Python 3.3, Python 3.4 ___ Python tracker ___ _

[issue15693] expose glossary link on hover

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue15693] expose glossary link on hover

Chris Jerdonek added the comment: It looks like the issue I previously filed on the Sphinx tracker was migrated here: https://github.com/sphinx-doc/sphinx/issues/996 . But the patch I submitted seems to have been dropped. -- ___ Python tracker

[issue15693] expose glossary link on hover

Changes by Georg Brandl : -- assignee: georg.brandl -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue15693] expose glossary link on hover

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue15693] expose glossary link on hover

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue15693] expose glossary link on hover

Changes by Antoine Pitrou : -- stage: patch review -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue15693] expose glossary link on hover

Changes by Antoine Pitrou : -- assignee: docs@python -> georg.brandl nosy: +georg.brandl stage: -> patch review type: enhancement -> behavior versions: +Python 3.1, Python 3.4 ___ Python tracker __

[issue15693] expose glossary link on hover

Chris Jerdonek added the comment: I submitted a patch for this issue on the Sphinx tracker. -- ___ Python tracker ___ ___ Python-bugs-

[issue15693] expose glossary link on hover

Chris Jerdonek added the comment: I created a Sphinx issue for this here: https://bitbucket.org/birkenfeld/sphinx/issue/996/expose-glossary-entry-link-on-hover -- ___ Python tracker ___

[issue15693] expose glossary link on hover

R. David Murray added the comment: Well, I think it depends on what we consider the priority of the issue. So, I personally would count this one as low, and would be happy that it gets fixed whenever we happen to upgrade to a version of Sphinx that fixes it. If it is an issue we consider hig

[issue15693] expose glossary link on hover

Chris Jerdonek added the comment: > I think we generally upgrade it exactly when there is a new Sphinx feature we > want for our docs :) :) Would the appropriate way to handle it be then to create an issue to "upgrade Sphinx when XXX issue is resolved" and link to the corresponding Sphinx is

[issue15693] expose glossary link on hover

R. David Murray added the comment: We do pin it, but we generally have no problem with upgrading. I think we generally upgrade it exactly when there is a new Sphinx feature we want for our docs :) We don't maintain local patches to Sphinx (though we do have code that is specific to our docs,

[issue15693] expose glossary link on hover

Chris Jerdonek added the comment: Do we pin the version of Sphinx that we use to generate the documentation? If Sphinx fixes the issue, would we need to make a corresponding change here to reflect the fix? -- ___ Python tracker

[issue15693] expose glossary link on hover

New submission from Chris Jerdonek: It would be nice if hovering over the right side of the header to a glossary entry would expose a link in the same way that it does for function definitions, etc. http://docs.python.org/dev/glossary.html#glossary Otherwise, there doesn't seem to be a conven

[issue15693] expose glossary link on hover

R. David Murray added the comment: I think it probably should be filed with sphinx instead, rather than also. -- nosy: +r.david.murray ___ Python tracker ___