On Fri, Feb 4, 2011 at 7:43 PM, Chris Withers ch...@simplistix.co.uk 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
On Sun, Feb 6, 2011 at 4:26 PM, nick.coghlan python-check...@python.org 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
+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 Mon, Feb 7, 2011 at 12:06 AM, Éric Araujo mer...@netwok.org 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
On Sun, Feb 6, 2011 at 04:14, anatoly techtonik techto...@gmail.com wrote:
On Fri, Feb 4, 2011 at 7:43 PM, Chris Withers ch...@simplistix.co.uk
wrote:
I've helped quite a few python newbies on Windows who are also
surprised / frustrated on learning that python on the command line
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
On Sun, Feb 6, 2011 at 09:22, Chris Withers ch...@simplistix.co.uk 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
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 Mon, Feb 7, 2011 at 1:27 AM, Chris Withers ch...@simplistix.co.uk 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
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon python-check...@python.org 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
On 6 February 2011 15:35, Nick Coghlan ncogh...@gmail.com wrote:
On Mon, Feb 7, 2011 at 1:27 AM, Chris Withers ch...@simplistix.co.uk 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
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, what is
Le 06/02/2011 17:15, Antoine Pitrou a écrit :
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon python-check...@python.org 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
On 6 February 2011 17:07, Stephen J. Turnbull step...@xemacs.org 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
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
On Sun, 06 Feb 2011 19:10:37 +0100
Éric Araujo mer...@netwok.org wrote:
Le 06/02/2011 17:15, Antoine Pitrou a écrit :
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon python-check...@python.org wrote:
To create your patch, you should generate a unified diff from your
checkout's
On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon python-check...@python.org wrote:
To create your patch, you should generate a unified diff from your
checkout's
top-level directory::
- svn diff patch.diff
+
On Sunday, 06 February 2011 at 12:13, Brett Cannon wrote:
On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon python-check...@python.org wrote:
To create your patch, you should generate a unified diff from your
On Sun, Feb 6, 2011 at 12:36, Brendan Cully bren...@kublai.com wrote:
On Sunday, 06 February 2011 at 12:13, Brett Cannon wrote:
On Sun, Feb 6, 2011 at 08:15, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 06 Feb 2011 02:10:15 +0100
brett.cannon python-check...@python.org wrote:
To
On Mon, Feb 7, 2011 at 6:53 AM, Brett Cannon br...@python.org 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
On Mon, Feb 7, 2011 at 6:08 AM, raymond.hettinger
python-check...@python.org 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,
21 matches
Mail list logo
