I'm very happy to announce that the core Python repository switch
to Mercurial is complete and the new repository at
http://hg.python.org/cpython/ is now officially open for cloning,
and for commits by those who had commit access to SVN.
The developers' guide at http://docs.python.org/devguide/ has
been updated to talk about Mercurial and should be enough to
get anyone started with a clone.
We'll work on extracting active feature branches into separate
clones next; please let us know which branches these are (we
already know of py3k-cdecimal, pep-3151 and pep-382).
To make new feature "branches" (ie. clones) that are to be
available at hg.python.org, best use the "server side clone"
feature that is available at http://hg.python.org/cpython/
in order to create the new repository.
To look up SVN revisions, use hg.python.org/lookup/rXXXXX.
The tracker has also been updated to link to hg.python.org
for files and revisions. For the future, it will recognize
hg changeset hashes as well (without brackets, see the recent
The buildbots should also now be building from the hg repositories.
Please let me know if you notice any disruptions, or anything
else that needs fixing, or any other question. Also please
redirect praise to Antoine Pitrou and Dirkjan Ochtman who did
most of the actual work.
On Mon, Mar 7, 2011 at 20:57, benjamin.peterson
> changeset: 68323:a7e0cff05597
> branch: 3.1
> parent: 68317:d9125bf3bac5
> user: Benjamin Peterson <benjamin(a)python.org>
> date: Mon Mar 07 22:50:37 2011 -0600
> transform izip_longest #11424
Could we get a little less cryptic checkin messages? I have no idea what
this is supposed to mean (and it doesn't look related to
http://bugs.python.org/issue11424 either.) When looking through the changes
(for example when figuring out when a change was introduced and whether it
was intentional) it's really helpful if the checkin message explains the
intent without having to visit the bugtracker for each one.
Thomas Wouters <thomas(a)python.org>
Hi! I'm a .signature virus! copy me into your .signature file to help me
Yesterday I cloned the hg cpython repository and made several local copies
for various maintenance releases. This morning I tried to hg pull my
cpython repo to get any changes (not really expecting any), but got this
% hg pull
pulling from http://hg.python.org/cpython
searching for changes
abort: repository is unrelated
What did I do wrong?
> Author: victor.stinner
> Date: Wed Mar 2 02:03:14 2011
> New Revision: 88709
> Log: Issue #8923: cache str.encode() result
> When a string is encoded to UTF-8 in strict mode, the result is cached into the
> object. Examples: str.encode(), str.encode('utf-8'), PyUnicode_AsUTF8String()
> and PyUnicode_AsEncodedString(unicode, "utf-8", NULL).
I don’t really understand this message (especially “cached into the
object”) :) Maybe in the Misc/NEWS entry you could also add a line to
explain to users the reason/goal/benefit of this change?
On Sat, Feb 26, 2011 at 12:43 AM, Guido van Rossum <guido(a)python.org> wrote:
> Now that the language moratorium is lifted, let's make sure to get PEP
> 380 implemented for Python 3.3.
How about official RoadMap? There is no visibility into what's going
on in Python development. New people can' t jump in and help do bring
some features faster. http://dungeonhack.sourceforge.net/Roadmap
"yield from" seems useful.
I want to maintain several working copies, as sometimes I have to make bugfix
changes across several revisions. Since we are supposed to use forward-porting,
I tried to set up a 2.5 clone, but building from it fails with a "Fatal Python
error: subversion keywords missing".
What I did (in ~/projects/python):
hg clone ssh://firstname.lastname@example.org/cpython default
hg clone default 2.5
hg update 2.5
gcc -pthread -Xlinker -export-dynamic -o python \
libpython2.5.a -lpthread -ldl -lutil -lm
libpython2.5.a(posixmodule.o): In function `posix_tmpnam':
/home/vinay/projects/python/2.5/./Modules/posixmodule.c:6858: warning: the use
of `tmpnam_r' is dangerous, better use `mkstemp'
libpython2.5.a(posixmodule.o): In function `posix_tempnam':
/home/vinay/projects/python/2.5/./Modules/posixmodule.c:6813: warning: the use
of `tempnam' is dangerous, better use `mkstemp'
case $MAKEFLAGS in \
*-s*) CC='gcc -pthread' LDSHARED='gcc -pthread -shared' OPT='-DNDEBUG -g
-fwrapv -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py -q build;; \
*) CC='gcc -pthread' LDSHARED='gcc -pthread -shared' OPT='-DNDEBUG -g -fwrapv
-O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py build;; \
Fatal Python error: subversion keywords missing
BTW, this is happening on my Ubuntu Jaunty machine which I have been using for
many months with the Subversion repository.
Am I doing something wrong?
I ported the code review support on bugs.python.org to hg,
and reactivated it. Review "issues" are created automatically
if the attached file is recognized as a patch that applies
cleanly. The roundup issue's nosy list is synchronized with the
rietveld issue's cc list, so comments get mailed to the nosy
If there are any problems with that installation, please report
them to the meta tracker.