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.
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.
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?
> + 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?
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_testinghttp://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
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
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
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 ?
Hi, guys
I'm not sure if python-dev is the right place to write to, but I'm
really curious about this:
>From the Python Language reference:
> It is illegal to unbind a name referenced by an enclosing scope; the compiler will report a SyntaxError.
But when I run the following code:
a = 3
def x():
global a
del(a)
print(a)
x()
it works fine; and when I change the order of calls:
x()
print(a)
I get a NameError, not a SyntaxError.
Now I asked the same question on python-list and people suggested that
the true meaning of that rule is:
>>> def f():
... a = 42
... def g():
... nonlocal a
... del a
...
SyntaxError: can not delete variable 'a' referenced in nested scope
Which looks weird, because the name is referenced in the _enclosed_
scope, not the _enclosing_ scope. Is there a typo in the documentation
or am I missing something?