[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-09-10 Thread Bryce Verdier
Bryce Verdier added the comment: No worries, I totally understand. I was working on it a little bit at a time, as life would allow. And being probably more thorough than I needed to be. Here is the patch of everything that I've accomplished. Hope this helps. -- keywords: +patch Added

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-09-09 Thread Éric Araujo
Éric Araujo added the comment: After thinking about this, I think it may be easier for everyone if I just did the change. It’s just a list of boring grep-sed combos to run, and it’s easier if a core dev just does it instead of reviewing a long patch. Sorry if you invested time, Bryce.

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-08 Thread Terry J. Reedy
Terry J. Reedy added the comment: Changing ``x`` to :data:`x` adds 4 chars. Changing ``x()`` to :func:`x` justs adds 2. If I were to review, I would prefer that the additions not trigger cascading line rewraps. -- ___ Python tracker

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-08 Thread Ezio Melotti
Ezio Melotti added the comment: ``...`` should also be used for common names like True, False, None (no one needs links to their doc to see what they are), or, as Éric said, to avoid creating links for each occurrence of a name (one such example is the name of a module in the page that docume

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-08 Thread Éric Araujo
Éric Araujo added the comment: instead of* An addition: in some cases, it may be on purpose that someone used ``somename`` instead of :func:`somename`, for example to avoid a ton of link in the doc of the somename function. For the most part however, I believe it was just unawareness (or ma

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-08 Thread Éric Araujo
Éric Araujo added the comment: > I would like to help out with this, as there seems to be a lot of > work that needs to be done. Thanks! In my initial report, I was talking only about module-level names that are documented as code (``sys.path``) instead of module-level data (:data:`sys.path`

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-06 Thread Ezio Melotti
Ezio Melotti added the comment: For global there's :keyword:. Also note that :data: should be used for module-level variables (or constant) not for attributes of e.g. classes and instances. If there are other ``...`` that can be fixed (even using something else like e.g. :func: or :meth:),

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-06 Thread Terry J. Reedy
Terry J. Reedy added the comment: I presume so. I believe ``x`` is meant for general code like ``for thing in group: print(thing)``. While Éric specifically mentioned the :data: role, I presume the same idea applies to :func: and possibly other link-generating roles. Is there a statement rol

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-06 Thread Bryce Verdier
Bryce Verdier added the comment: Is this more what was in mind for the bug? -- Added file: http://bugs.python.org/file22850/issue12301.test_patch ___ Python tracker ___

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-06 Thread Ezio Melotti
Ezio Melotti added the comment: Nope, ``...`` can be used for generic pieces of code, whereas e.g. :data:`sys.stdout` indicates that stdout is a "data" attribute of the sys module. If you use :data:`...` and rebuild the doc (cd Doc/; make html), you will see that e.g. sys.stdout will be then

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-08-06 Thread Bryce Verdier
Bryce Verdier added the comment: I would like to help out with this, as there seems to be a lot of work that needs to be done. I guess I'm a little unsure about what you mean by ``code`` instead of :data:. Is ``code`` generic? Like in Doc/tutorials/classes.rst I see a lot of things similar t

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-07-20 Thread Ezio Melotti
Ezio Melotti added the comment: +1 -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-06-10 Thread Terry J. Reedy
Terry J. Reedy added the comment: Links are good ;-). -- nosy: +terry.reedy stage: -> needs patch ___ Python tracker ___ ___ Python-

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

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

[issue12301] Use :data:`sys.thing` instead of ``sys.thing`` throughout

2011-06-09 Thread Éric Araujo
New submission from Éric Araujo : In a great number of files, the ``code`` markup is used instead of the :data: role, which would create a link to the appropriate definition. Unless someone objects, I would like to change all of them. -- assignee: eric.araujo components: Documentation