A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-September/121632.html below:

[Python-Dev] Online docs: make index search available everywhere

[Python-Dev] Online docs: make index search available everywhere [Python-Dev] Online docs: make index search available everywhereChris Jerdonek chris.jerdonek at gmail.com
Sat Sep 8 22:18:05 CEST 2012
On Thu, Sep 6, 2012 at 10:26 AM, R. David Murray <rdmurray at bitdance.com> wrote:
> On Thu, 06 Sep 2012 13:15:14 -0400, Terry Reedy <tjreedy at udel.edu> wrote:
>> My understanding is that the tracker is for the cpython repository at
>> hg.python.org and my impression is that web code is elsewhere.
>
> That is true.  However, the appearance and functionality of the doc web
> pages is entirely controlled by Sphinx, and thus by the sources checked
> in to the code repository.

This raises a related question.  Where should we file issues for
Python-controlled things that are outside the scope of the cpython
repository (or the devguide) and that are not issues with the tracker
(which has its own tracker -- the meta tracker).

For example, where should we file an issue for hg.python.org if we
suspect the issue is with how we've customized things rather than with
Mercurial's hgweb itself.  The main bugs tracker has a component for
"Devguide" but not for other non-cpython repository things like
hg.python.org.

--Chris
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4