Re: [Python-Dev] [Python-checkins] cpython (2.7): Fix closes Issue12722 - link heapq source in the text format in the
On Wed, Aug 10, 2011 at 21:55, Terry Reedy <tjreedy@udel.edu> wrote:
Latest version of the `heapq Python source code
-<http://svn.python.org/view/python/branches/release27-maint/Lib/heapq.py?view=markup>`_
Should links be to the hg repository instead of svn? Is svn updated from hg? I thought is was (mostly) historical read-only.
I made the same remark to Senthil on IRC, and came out that web frontend for hg.p.o doesn't allow for a nice way to specify a branch (different than 'default'), it's something like hg.python.org/cpython/<last cset id on a given branch>/path/to/file.py which is almost always outdated :) What do we use to provide the web part of hg.p.o? maybe we can just ask the developers of this tool to provide (or advertize) a proper way to select a branch. If some can provide me some info, I can do the "ask the devs" part. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
On 11/08/2011 0.02, Sandro Tosi wrote:
On Wed, Aug 10, 2011 at 21:55, Terry Reedy<tjreedy@udel.edu> wrote:
Latest version of the `heapq Python source code
-<http://svn.python.org/view/python/branches/release27-maint/Lib/heapq.py?view=markup>`_
Should links be to the hg repository instead of svn? Is svn updated from hg? I thought is was (mostly) historical read-only. I made the same remark to Senthil on IRC, and came out that web frontend for hg.p.o doesn't allow for a nice way to specify a branch (different than 'default'), it's something like hg.python.org/cpython/<last cset id on a given branch>/path/to/file.py which is almost always outdated :)
hg.python.org/cpython/2.7/path/to/file.py should work just fine. IIRC the reason why we don't do it on 2.x is because we don't have the 'source' directive available in Sphinx and therefore we would have to update all the links manually to link to h.p.o instead of s.p.o. Best Regards, Ezio Melotti
What do we use to provide the web part of hg.p.o? maybe we can just ask the developers of this tool to provide (or advertize) a proper way to select a branch. If some can provide me some info, I can do the "ask the devs" part.
Cheers,
On Wed, Aug 10, 2011 at 11:58:24PM +0300, Ezio Melotti wrote:
hg.python.org/cpython/2.7/path/to/file.py should work just fine.
The correct path seems to be: http://hg.python.org/cpython/file/2.7/Lib/<modulefile.py>
IIRC the reason why we don't do it on 2.x is because we don't have the 'source' directive available in Sphinx and therefore we would have to update all the links manually to link to h.p.o instead of s.p.o.
I see. Does sphinx have any such directive already? How is it supposed to behave? -- Senthil
Hi,
IIRC the reason why we don't do it on 2.x is because we don't have the 'source' directive available in Sphinx and therefore we would have to update all the links manually to link to h.p.o instead of s.p.o.
In 3.2 and higher, there is a custom source role in Doc/tools/sphinxext/pyspecific.py. For 2.7, I volunteered to change all links manually (sed being, as usual, my friend) but just lacked time. Cheers
On Thu, Aug 11, 2011 at 16:33, Éric Araujo <merwok@netwok.org> wrote:
Hi,
IIRC the reason why we don't do it on 2.x is because we don't have the 'source' directive available in Sphinx and therefore we would have to update all the links manually to link to h.p.o instead of s.p.o.
In 3.2 and higher, there is a custom source role in Doc/tools/sphinxext/pyspecific.py. For 2.7, I volunteered to change all links manually (sed being, as usual, my friend) but just lacked time.
Is there a reason we can't use the same sphinx role in 2.7 too? And also the same sphinx (thus sphinxext) versions on 2.7 and 3.x? that would probably help in keeping the diffs on the documentation smaller. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
Le 11/08/2011 16:47, Sandro Tosi a écrit :
Is there a reason we can't use the same sphinx role in 2.7 too? And also the same sphinx (thus sphinxext) versions on 2.7 and 3.x? that would probably help in keeping the diffs on the documentation smaller.
Even though the pyspecific module is wholly private and used only for our build process, Georg seems to follow the rule that we don’t add new features in stable branches. I think that’s why the new role was added in 3.2 when in was in dev phase but not to 2.7 (see #10334). We also use different versions of Sphinx. Regards
Am 11.08.2011 17:01, schrieb Merwok:
Le 11/08/2011 16:47, Sandro Tosi a écrit :
Is there a reason we can't use the same sphinx role in 2.7 too? And also the same sphinx (thus sphinxext) versions on 2.7 and 3.x? that would probably help in keeping the diffs on the documentation smaller.
Even though the pyspecific module is wholly private and used only for our build process, Georg seems to follow the rule that we don’t add new features in stable branches. I think that’s why the new role was added in 3.2 when in was in dev phase but not to 2.7 (see #10334).
I think I just put it in default as a test, and intended to backport it later when it proved useful. You're welcome to do so now.
We also use different versions of Sphinx.
That doesn't matter for this role. Georg
participants (7)
-
Ezio Melotti -
Georg Brandl -
Merwok -
Raymond Hettinger -
Sandro Tosi -
Senthil Kumaran -
Éric Araujo