On Mon, Feb 7, 2011 at 6:08 AM, raymond.hettinger
wrote:
> +In addition, the :func:`~dis.dis` function now accepts string arguments
> +so that the common idiom ``dis(compile(s, '', 'eval'))`` can be shortened
> +to ``dis(compile(s))``::
That should be ``dis(s)``.
Cheers,
Nick.
--
Nick Coghlan
On Mon, Feb 7, 2011 at 6:53 AM, Brett Cannon wrote:
> I would rather not have new hg users have to install an extension just
> to get a simple workflow going.
I may still keep my Rdiff-based FAQ entry around as an example of how
to get a collapsed diff regardless of personal workflow, though.
In
On Sun, Feb 6, 2011 at 12:36, Brendan Cully wrote:
> On Sunday, 06 February 2011 at 12:13, Brett Cannon wrote:
>> On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou wrote:
>> > On Sun, 06 Feb 2011 02:10:15 +0100
>> > brett.cannon wrote:
>> >>
>> >> To create your patch, you should generate a unified
On Sunday, 06 February 2011 at 12:13, Brett Cannon wrote:
> On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou wrote:
> > On Sun, 06 Feb 2011 02:10:15 +0100
> > brett.cannon wrote:
> >>
> >> To create your patch, you should generate a unified diff from your
> >> checkout's
> >> top-level directory::
On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou wrote:
> On Sun, 06 Feb 2011 02:10:15 +0100
> brett.cannon wrote:
>>
>> To create your patch, you should generate a unified diff from your
>> checkout's
>> top-level directory::
>>
>> - svn diff > patch.diff
>> + hg outgoing --path > patch.dif
On Sun, 06 Feb 2011 19:10:37 +0100
Éric Araujo wrote:
> Le 06/02/2011 17:15, Antoine Pitrou a écrit :
> > On Sun, 06 Feb 2011 02:10:15 +0100
> > brett.cannon wrote:
> >> To create your patch, you should generate a unified diff from your
> >> checkout's
> >> top-level directory::
> >>
> >> -
> I'd like to see this in 3.2 release, of course.
As Brian already asserted: that's not feasible. I still haven't
managed to test your installer, and may not be able to for the
next few weeks. It's also against the policy for release candidates
to add such a change at this point. I believe the cha
On 6 February 2011 17:07, Stephen J. Turnbull wrote:
> Paul Moore writes:
>
> > "Before any existing Python directories, otherwise at the end" is the
> > closest to what I suspect most users want (certainly it matches my
> > preferences, and anything else would have me manually editing PATH
>
Le 06/02/2011 17:15, Antoine Pitrou a écrit :
> On Sun, 06 Feb 2011 02:10:15 +0100
> brett.cannon wrote:
>> To create your patch, you should generate a unified diff from your
>> checkout's
>> top-level directory::
>>
>> -svn diff > patch.diff
>> +hg outgoing --path > patch.diff
>
> S
Paul Moore writes:
> "Before any existing Python directories, otherwise at the end" is the
> closest to what I suspect most users want (certainly it matches my
> preferences, and anything else would have me manually editing PATH
> anyway, so is of no use to me in practice).
Unfortunately, wha
On 6 February 2011 15:35, Nick Coghlan wrote:
> On Mon, Feb 7, 2011 at 1:27 AM, Chris Withers wrote:
>> On 06/02/2011 15:25, Brian Curtin wrote:
>>>
>>> So put the new path before the old path, or replace it? The current
>>> patch appends to the end.
>>
>> I believe the last path wins in Windows
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon wrote:
>
> To create your patch, you should generate a unified diff from your checkout's
> top-level directory::
>
> -svn diff > patch.diff
> +hg outgoing --path > patch.diff
Should be --patch.
The problem is that it will show one seve
On Mon, Feb 7, 2011 at 1:27 AM, Chris Withers wrote:
> On 06/02/2011 15:25, Brian Curtin wrote:
>>
>> So put the new path before the old path, or replace it? The current
>> patch appends to the end.
>
> I believe the last path wins in Windows land, so that would be fine.
Not that I've ever experi
On 06/02/2011 15:25, Brian Curtin wrote:
So put the new path before the old path, or replace it? The current
patch appends to the end.
I believe the last path wins in Windows land, so that would be fine.
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
On Sun, Feb 6, 2011 at 09:22, Chris Withers wrote:
> On 06/02/2011 15:20, Brian Curtin wrote:
>
>> There are still outstanding considerations in the various issues on the
>> tracker, so it would be best to address them before requesting
>> integration. Example: What should happen when there is an
On 06/02/2011 15:20, Brian Curtin wrote:
There are still outstanding considerations in the various issues on the
tracker, so it would be best to address them before requesting
integration. Example: What should happen when there is another Python
installation on the path?
Same as happens with mo
On Sun, Feb 6, 2011 at 04:14, anatoly techtonik wrote:
> On Fri, Feb 4, 2011 at 7:43 PM, Chris Withers
> wrote:
> >>
> >> I've helped quite a few "python newbies" on Windows who are also
> >> surprised / frustrated on learning that "python" on the command line
> >> doesn't work after installing
On Mon, Feb 7, 2011 at 12:06 AM, Éric Araujo wrote:
>>> +How do I compare my working copy to a remote repository?
>>
>> To save anyone else pointing this out, I'm now aware that "hg
>> incoming" and "hg outgoing" are the actual commands I want.
>
> incoming and outgoing compare your repository to
>> +How do I compare my working copy to a remote repository?
>
> To save anyone else pointing this out, I'm now aware that "hg
> incoming" and "hg outgoing" are the actual commands I want.
incoming and outgoing compare your repository to a remote repository,
not your working copy.
Regards
__
On Sun, Feb 6, 2011 at 4:26 PM, nick.coghlan wrote:
> +How do I compare my working copy to a remote repository?
> +---
To save anyone else pointing this out, I'm now aware that "hg
incoming" and "hg outgoing" are the actu
On Fri, Feb 4, 2011 at 7:43 PM, Chris Withers wrote:
>>
>> I've helped quite a few "python newbies" on Windows who are also
>> surprised / frustrated on learning that "python" on the command line
>> doesn't work after installing python.
>
> Yes, I've always found it a surprising disappointment tha
21 matches
Mail list logo
