[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2012-10-27 Thread Éric Araujo
Changes by Éric Araujo : -- resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ Py

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2012-10-27 Thread Georg Brandl
Georg Brandl added the comment: I'm not very attached to it, so I'm fine with closing. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2012-10-27 Thread Éric Araujo
Éric Araujo added the comment: Unless Georg would still like this, I retract the proposal. Ezio: > Disabling `...` sounds OK to me (I don't think we have many left, if any). I think some of them crept up in logging and unittest docs, but they are easy to find with Doc/tools/rst-lint.py ---

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2012-09-18 Thread Ezio Melotti
Ezio Melotti added the comment: I think I'm -1 on this, for the following reasons: * it's less explicit; * it gives you less control (I'm thinking e.g. at the () added by :func:/:meth: but not :class:, so that :func:`int` and :class:`int` are rendered in different ways); * even though this m

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2012-07-05 Thread Éric Araujo
Éric Araujo added the comment: > for example, as a result of documentation merge it both > :func:`someref` and :class:`someref` can appear I think this would cause a warning from Sphinx, as all class/meth/func/mod/etc roles look up in the same namespace (what Georg said). Benjamin is -1 for ex

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2012-05-15 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2010-06-20 Thread anatoly techtonik
anatoly techtonik added the comment: `someref` would be more convenient than :func:`someref` but in case of namespace conflict (for example, as a result of documentation merge it both :func:`someref` and :class:`someref` can appear) - it would be necessary to go through all the links in both

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2010-06-19 Thread Benjamin Peterson
Benjamin Peterson added the comment: -1 I like how explicit it is now. -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-b

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2010-06-14 Thread Georg Brandl
Georg Brandl added the comment: The type doesn't matter anyway, no need to find it by questionable means. -- nosy: +georg.brandl ___ Python tracker ___ __

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

2010-06-14 Thread Éric Araujo
New submission from Éric Araujo : Following a discussion on IRC: I would even prefer having more of just `object` instead of :func:`object` or :class:`object` I think it would be feasible to write a reST role that would use inspect or pydoc to find the type. It would not violate “In the face