[Python-Dev] hg.python.org should default to defaut, not 2.7
Ned Deily
nad at acm.org
Thu Aug 30 23:51:57 CEST 2012
In article <20120830224616.5b6d4a29 at pitrou.net>,
Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Thu, 30 Aug 2012 13:34:56 -0700
> Ethan Furman <ethan at stoneleaf.us> wrote:
> > Ned Deily wrote:
> > > In article <k1ogk6$uns$1 at ger.gmane.org>, Terry Reedy <tjreedy at udel.edu>
> > > wrote:
> > >
> > >> If one goes to http://hg.python.org/cpython/ and clicks 'browse', it
> > >> defaults to 2.7, not to default (now 3.3). Moreover, there is no
> > >> indication that it is defaulting to an old branch rather than current
> > >> default, as one might reasonably expect. I found this very confusing
> > >> when I was trying to get a link for a python-list post and the code did
> > >> not look right.
> > >
> > > It defaults to "tip" which is the most recently pushed change set. At
> > > the moment, it just so happens that tip is a 2.7 change set. Usually a
> > > change set for "default" will be the most recent but not always. You
> > > just need to check the branch list.
> >
> > So is it not possible to have the default stay at "default" instead of
> > at "tip"?
>
> http://bz.selenic.com/show_bug.cgi?id=2815
Yes, as Matt hints at, what most people really want is a filter for a
particular branch. As it stands, you can always find the (default) head
of a branch:
http://hg.python.org/cpython/shortlog/default
http://hg.python.org/cpython/shortlog/3.2
http://hg.python.org/cpython/shortlog/2.7
etc but note that as you follow the graph for a branch, merge change
sets can take you into other branches depending on which parent you
choose, and the change log shows all earlier change sets regardless of
branch.
--
Ned Deily,
nad at acm.org
More information about the Python-Dev
mailing list