On Sun, Sep 9, 2012 at 6:18 AM, Chris Jerdonek <chris.jerdonek at gmail.com> wrote: > 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. As far as I know, we don't have a general ticketing system for python.org infrastructure. That may change at some point in the future, but in the meantime I just email python-committers or python-dev if I notice something that appears broken with the development infrastructure, or pydotorg-www for the website in general. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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