Mailman 3 February 2011 - Python-Dev

Re: [Python-Dev] r88676 - peps/trunk/pep-0385.txt
by Antoine Pitrou 01 Mar '11

01 Mar '11

On Mon, 28 Feb 2011 13:36:11 -0500 Terry Reedy <tjreedy(a)udel.edu> wrote: > > > + an existing branch. The pusher then has to merge the superfetatory heads > > 'superfetatory'? I have no idea of what this is, neither does > merriam-webster.com ;-). There are some Google hits, though... Not sure if they are of people making the same mistakes as I do ;) Regards Antoine.

7 11

Re: [Python-Dev] devguide (hg_transition): Advertise hg import over patch.
by Antoine Pitrou 28 Feb '11

28 Feb '11

On Sun, 27 Feb 2011 04:17:06 +0100 eric.araujo <python-checkins(a)python.org> wrote: > Advertise hg import over patch. > > hg import understands the extended git diff format, which supports renames, > changes to the executable bit and changes in binary files. Yes, but it's too easy to forget the awkward "--no-commit" option. "patch" doesn't involve such quirks. > patch doesn?t > do anything useful with that information, and also requires downloading and > setup on Windows. Well, chances are TortoiseHG comes with an UI to apply patches (TortoiseSVN had one), so the command-line instructions may be of little use to them. Regards Antoine.

4 6

hg extensions was Mercurial conversion repositories
by Dj Gilcrease 27 Feb '11

27 Feb '11

So reading the thread about the conversion and the dev guide at http://potrou.net/hgdevguide/ there seems to not be a list of recommended extensions that the python devs should have and use, only a few examples of their use. so I figured I would build up a list for other people to add to / comment on File Format Management eol http://mercurial.selenic.com/wiki/EolExtension required flake8 http://pypi.python.org/pypi/flake8/ recommended especially for new commiters as it will validate pep8 compliance and check for common errors *Maybe update it to do pep7 compliance checks on the c files as well? Patch Management mq http://mercurial.selenic.com/wiki/MqExtension This is the one the devguide uses in examples rebase http://mercurial.selenic.com/wiki/RebaseExtension used with the --collapse option it is very easy to build up a patch patch with incremental commits, but discard the private history of the developer This one makes more sense to me personally then mq and fits how my standard workflow goes better shelve http://mercurial.selenic.com/wiki/ShelveExtension Store un commited changes away so they dont affect generation of the patch transplant http://mercurial.selenic.com/wiki/TransplantExtension required to port patches between major versions record http://mercurial.selenic.com/wiki/RecordExtension Allows cherry picking of commits to build a patch, Also works with mq Crecord http://mercurial.selenic.com/wiki/CrecordExtension appears to be a c optimized version or record Branch Management bookmarks http://mercurial.selenic.com/wiki/BookmarksExtension Great for tracking bug fix work without needing to create a separate working directory recommended that the central repo NOT have the extension enabled so as to ensure bookmarks are a local only tracking system

7 14

Re: [Python-Dev] devguide (hg_transition): Minor edits and typo fixes.
by Antoine Pitrou 27 Feb '11

27 Feb '11

On Sun, 27 Feb 2011 04:17:09 +0100 eric.araujo <python-checkins(a)python.org> wrote: > > - Move a link target after its use > - Add a todo about tracker markup > - Remove one XXX that was in a warning block, not a comment Well, this is a XXX because that means we could find something else to advocate, not because the reader must take it as a warning.

2 1

Re: [Python-Dev] devguide (hg_transition): patchcheck does work
by Antoine Pitrou 27 Feb '11

27 Feb '11

On Sun, 27 Feb 2011 04:17:07 +0100 eric.araujo <python-checkins(a)python.org> wrote: > summary: > patchcheck does work How does it find out which changesets it should operate on?

2 1

Re: [Python-Dev] [Python-checkins] hooks: Fix checkbranch hook
by Éric Araujo 27 Feb '11

27 Feb '11

> + if branch in ('trunk', 'legacy-trunk', > + '2.0', '2.1', '2.2', '2.3', '2.4', '3.0'): Wouldn’t using a whitelist instead of a blacklist protect against new named branches too?

5 5

Re: [Python-Dev] [Python-checkins] devguide: List common gotchas people might come across when doing coverage work.
by Sandro Tosi 27 Feb '11

27 Feb '11

On Sun, Feb 27, 2011 at 06:31, brett.cannon <python-checkins(a)python.org> wrote: > +When writing new tests to increase coverage, do take note of the style of tests > +already provided for a module (e.g., whitebox, blackbox, etc.). As > +some modules are primarily maintained by a single core developer they may have > +a specific preference as to what kind of test is used (e.g., whitebox) and > +prefer that other types of tests not be used (e.g., blackbox). When in doubt, > +stick with whitebox testing in order to properly exercise the code. Do you think it could be nice to have a reference to what whitebox/blackbox testing is, ie http://en.wikipedia.org/wiki/White-box_testing http://en.wikipedia.org/wiki/Black-box_testing ? Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi

1 0

Re: [Python-Dev] [Python-checkins] devguide (hg_transition): patchcheck does work
by Sandro Tosi 27 Feb '11

27 Feb '11

On Sun, Feb 27, 2011 at 03:17, eric.araujo <python-checkins(a)python.org> wrote: > eric.araujo pushed f325d743c385 to devguide: > > http://hg.python.org/devguide/rev/f325d743c385 > changeset: 331:f325d743c385 > branch: hg_transition > user: ?ric Araujo <merwok(a)netwok.org> > date: Sat Feb 26 17:30:51 2011 +0100 > summary: > patchcheck does work > > files: > patch.rst > > diff --git a/patch.rst b/patch.rst > --- a/patch.rst > +++ b/patch.rst > @@ -114,15 +114,13 @@ > Generation > '''''''''' > > -.. XXX [commented out] make patchcheck doesn't work with non-SVN workflow > +To perform a quick sanity check on your patch, you can run:: > > - To perform a quick sanity check on your patch, you can run:: > + make patchcheck > > - make patchcheck > - > - This will check and/or fix various common things people forget to do for > - patches, such as adding any new files needing for the patch to work (do not > - that not all checks apply to non-core developers). > +This will check and/or fix various common things people forget to do for > +patches, such as adding any new files needing for the patch to work (do not (do note Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi

1 0

set iteration order
by Hagen Fürstenau 27 Feb '11

27 Feb '11

Hi, I just hunted down a change in behaviour between Python 3.1 and 3.2 to possibly changed iteration order of sets due to the optimization in issue #8685. Of course, this order shouldn't be relied on in the first place, but the side effect of the optimization might be worth mentioning in "What's new", maybe also pointing out that the old behaviour can be simulated with {x for x in a if x not in b} in place of "a-b". Cheers, Hagen

6 7

Re: [Python-Dev] pymigr: Ask for hgeol-checking hook.
by Antoine Pitrou 27 Feb '11

27 Feb '11

On Sat, 26 Feb 2011 18:48:17 +0100 martin.v.loewis <python-checkins(a)python.org> wrote: > * some hook should prevent pushing python files indented by tabs. > * some hook should prevent pushing to the 2.x trunk. > +* some hook should prevent breaking EOL conventions. We don't have such hook in SVN, why would we need one with Mercurial ?

4 7