Re: [Python-Dev] Fwd: [Python-committers] Pulling from contributors repositories
Le 13/06/2011 07:36, Hirokazu Yamamoto a écrit : > I've read the Python-committers thread "Pulling from contributors > repositories", which is about version control system. It seems there are > two main issues, linear (cleaner) history on pushing, and NEWS merging. > I'm newby of bazaar, but it seems to have a solution for first issue. We are using Mercurial. Regards ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] pysetup as a top script
Le 31/05/2011 08:45, Tarek Ziadé a écrit : > On Tue, May 31, 2011 at 7:13 AM, Nick Coghlan wrote: >> On Tue, May 31, 2011 at 2:44 AM, Tarek Ziadé wrote: >>> If no one objects, I'll promote Tools/scripts/pysetup3 to a top level >>> script that gets installed in scripts/ like 2to3, pydoc etc.. >>> >>> That way, people will be able to use it directly when installing, >>> removing projects, or studying what's installed >> Cool. >> >> Now I'm trying to remember if it was a list discussion or the language >> summit where you got the initial consensus on that approach... > The thread starts here: > http://mail.python.org/pipermail/python-dev/2010-October/104535.html > > The pysetup top-level script was mentioned here: > http://mail.python.org/pipermail/python-dev/2010-October/104581.html A few other reasons that were not mentioned previously: - In 2.4, we can’t run “-m distutils2.run”, but a pysetup2.4 script works - It’s nice for users to have something shorter than “python3.3 -m packaging.run run sdist” (I like to take “make” as the ideal goal) - It sends a message that we care about packaging (personal opinion) Regards ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Some additions to .hgignore
On 2011-06-01, Michael Foord wrote: > That sounds good to me. An issue certainly wouldn't hurt. So be it: http://bugs.python.org/issue12341 :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Parser/intrcheck.c
Hello, I may be missing something, but I'm wondering whether Parser/intrcheck.c is still used anywhere. It's only mentioned in some comments: $ grep -r intrcheck.c * Modules/signalmodule.c:1197:/* Replacements for intrcheck.c functionality PC/os2vacpp/makefile.omk:217: # intrcheck.c -- Not Referenced by Anyone (?) Python/sigcheck.c:3: interrupt occurs. It can't be in the intrcheck.c file since that And if I remove it and "make clean", I can still rebuild successfully. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
