> > > Unless somebody had committed to the tag - right?
> >
> > That would be insane, right? :)
>
> AFAIK it's not insane, just impossible.
IIRC, I did that for the 2.5.2 tag (or some such), correcting
the spelling of "2st" to "2nd" for the release date.
Regards,
Martin
_
Brett Cannon writes:
> > You need not feel that way. It's not you---the flexibility of dVCS
> > means that until the Powers That Be promulgate a Workflow, this will
> > be ambiguous.
>
> It also took me quite a while to finally grasp exactly how the typical
> workflow could go with a DVCS.
On Wed, Nov 5, 2008 at 17:36, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> In what follows, caveat IANB (I am not Brett, and neither is
> Cosmin), but there is some experience with these systems, and my
> recommendations are based on that.
>
Wow, I'm part of an acronym! That's a first.
> Cosm
On Tue, Nov 4, 2008 at 16:34, Brett Cannon <[EMAIL PROTECTED]> wrote:
> OK, I give: git is in the running. But do realize it will take a lot
> for it to beat out bzr or hg.
>
> I have emailed some people who have shown allegiance to a specific
> DVCS to seeif they are willing to fill in the usage s
Tres Seaver writes:
> svn doesn't have any true tags, AFAIK: everything is a branch.
Yow! I couldn't have imagined that would be true. And didn't
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
In what follows, caveat IANB (I am not Brett, and neither is
Cosmin), but there is some experience with these systems, and my
recommendations are based on that.
Cosmin Stejerean writes:
> On Nov 5, 2008, at 12:16 PM, [EMAIL PROTECTED] wrote:
> > What DVCS fits my poor brain best? I feel I'm li
Barry Warsaw writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 5, 2008, at 2:44 PM, Martin v. Löwis wrote:
> > Unless somebody had committed to the tag - right?
>
> That would be insane, right? :)
AFAIK it's not insane, just impossible.
Of course in any system you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
>> Yes. My understanding, though I haven't tried it yet, is that newer
>> versions of the bzr-svn plugin do a good job at a full conversion.
>> Basically, every svn branch becomes a bzr branch and all svn tags are
>> converted
2008/11/5 Nick Coghlan <[EMAIL PROTECTED]>:
> Paul Moore wrote:
>> While that would be good, my understanding is that stacked branches in
>> Bazaar only work (for history operations) while you're online. So they
>> make Bazaar work a little like a centralised VCS, I guess. Not sure
>> how that's a
Paul Moore wrote:
> 2008/11/5 Barry Warsaw <[EMAIL PROTECTED]>:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Nov 5, 2008, at 6:09 AM, Paul Moore wrote:
>>
>>> I'll freely admit a (not very) hidden bias here - the slowness of an
>>> initial clone (or going through the "download a sha
On Wed, Nov 5, 2008 at 12:45, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> Before we can make the switch to Bazaar, sure -- if we do.
>
> That is my whole point. Before we switch to whatever DVCS, this
> system should have a complete installation, with all pieces in
> place.
>
> I was just point
On Wed, Nov 5, 2008 at 10:16, <[EMAIL PROTECTED]> wrote:
>
> I apologize that I haven't read whatever Brett's written so far, but I just
> haven't had time, and don't know if there's a PEP yet (and if so, what its
> number is). I did want to get my questions/confusion on the record though.
>
It'
On Wed, Nov 5, 2008 at 07:35, Paul Moore <[EMAIL PROTECTED]> wrote:
> 2008/11/5 David Ripton <[EMAIL PROTECTED]>:
>> All timings very approximate:
>>
>> Time for average user to check out Python sources with bzr: 10 minutes
>>
>> Time for average user to check out Python sources with git or hg: 1 m
On Wed, Nov 5, 2008 at 03:09, Paul Moore <[EMAIL PROTECTED]> wrote:
> 2008/11/3 Brett Cannon <[EMAIL PROTECTED]>:
>> At this point I am looking for any suggestions for fundamental usage
>> scenarios that I am missing from the PEP. If you think the few already
>> listed are missing some core part of
> Before we can make the switch to Bazaar, sure -- if we do.
That is my whole point. Before we switch to whatever DVCS, this
system should have a complete installation, with all pieces in
place.
I was just pointing out that the bazaar installation is not
complete in this respect - I was not askin
On Nov 5, 2008, at 12:16 PM, [EMAIL PROTECTED] wrote:
I apologize that I haven't read whatever Brett's written so far, but
I just
haven't had time, and don't know if there's a PEP yet (and if so,
what its
number is). I did want to get my questions/confusion on the record
though.
What
Terry Reedy wrote:
> Stefan Behnel wrote:
>> One really neat feature is that you can put a .pxd file next to your .py
>> file and let it override the function signatures and classes. So you do
>> not even need Py3 annotations, which have the obvious disadvantage of
>> requiring Py3.
>
> That is no
On Wed, Nov 5, 2008 at 20:15, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Without a doubt the bazaar branches need a little more loving attention
> > to make them a full working demo, but it's mostly details. The branches
> > *do* contain the whole history, and not just 'select revisions':
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 2:44 PM, Martin v. Löwis wrote:
Yes. My understanding, though I haven't tried it yet, is that newer
versions of the bzr-svn plugin do a good job at a full conversion.
Basically, every svn branch becomes a bzr branch and all svn t
I wrote a patch to Tom Lee's AST optimization branch, which I have
submitted at http://bugs.python.org/issue4264. Here's a brief
explanation of what the patch does, followed by a little general
discussion of the future.
Python bytecode includes at least one operation which is not directly
accessi
> Yes. My understanding, though I haven't tried it yet, is that newer
> versions of the bzr-svn plugin do a good job at a full conversion.
> Basically, every svn branch becomes a bzr branch and all svn tags are
> converted to bzr tags, which are not separate branches, but actual
> symbolic names
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 2:15 PM, Martin v. Löwis wrote:
Without a doubt the bazaar branches need a little more loving
attention
to make them a full working demo, but it's mostly details. The
branches
*do* contain the whole history, and not just 'sele
> Without a doubt the bazaar branches need a little more loving attention
> to make them a full working demo, but it's mostly details. The branches
> *do* contain the whole history, and not just 'select revisions':
But there are dozens of branches which aren't represented, plus all the
tags (IIUC)
> I think it is also a good idea to write things using pure Python
> syntax in Cython, so that all other Python implementations, like
> Jython, Pypy, IronPython can just take it and run it in pure Python
> mode. Pure Python syntax means that the code runs in Python
> unmodified, but can also be com
Thank you very much for your answer. I have wondered about this for a long time.
From: Guido van Rossum <[EMAIL PROTECTED]>
To: L V <[EMAIL PROTECTED]>
Cc: python-dev@python.org
Sent: Wednesday, November 5, 2008 7:56:23 PM
Subject: Re: [Python-Dev] Why don't ran
On Wed, Nov 5, 2008 at 10:26 AM, L V <[EMAIL PROTECTED]> wrote:
> Why don't range and xrange threat floats as floats?
> Is there any good reason range and xrange don't threat floats as floats but
> as integers?
> When I enter float arguments in a range, the floats are treated as integers.
> (+ some
On Wed, Nov 5, 2008 at 1:26 PM, L V <[EMAIL PROTECTED]> wrote:
> Why don't range and xrange threat floats as floats?
> Is there any good reason range and xrange don't threat floats as floats but
> as integers?
> When I enter float arguments in a range, the floats are treated as integers.
> (+ some
Paul Moore wrote:
2008/11/5 David Ripton <[EMAIL PROTECTED]>:
All timings very approximate:
Time for average user to check out Python sources with bzr: 10 minutes
Time for average user to check out Python sources with git or hg: 1 minute
Time for average user's trivial patch to be reviewed an
Why don't range and xrange threat floats as floats?
Is there any good reason range and xrange don't threat floats as floats but as
integers?
When I enter float arguments in a range, the floats are treated as integers. (+
some warning)
This is how I think it should work:
>>>range(0, 1, 0.1)
[0.0,
I apologize that I haven't read whatever Brett's written so far, but I just
haven't had time, and don't know if there's a PEP yet (and if so, what its
number is). I did want to get my questions/confusion on the record though.
What DVCS fits my poor brain best? I feel I'm like a dinosaur not bei
Stefan Behnel wrote:
Terry Reedy wrote:
Do you have any plans to support/use 3.0 type annotations so that one
could develop function-oriented code in 3.0 and then compile efficient C
(for whatever CPython version) without adding Python-incompatible cdefs?
That is still an official TODO, but
David Ripton wrote:
> Time for average user to check out Python sources with bzr: 10 minutes
> Time for average user to check out Python sources with git or hg: 1 minute
> Time for average user's trivial patch to be reviewed and committed: 1 year
> I love DVCS as much as the next guy, but check
2008/11/5 David Ripton <[EMAIL PROTECTED]>:
> All timings very approximate:
>
> Time for average user to check out Python sources with bzr: 10 minutes
>
> Time for average user to check out Python sources with git or hg: 1 minute
>
> Time for average user's trivial patch to be reviewed and committe
2008/11/5 Barry Warsaw <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 5, 2008, at 6:09 AM, Paul Moore wrote:
>
>> I'll freely admit a (not very) hidden bias here - the slowness of an
>> initial clone (or going through the "download a shared repo, unpack
>> it, cre
Martin v. Löwis wrote:
Ah, that changes my view of it significantly. If the authors want to
contribute it to Python some day, I'm looking forward to that (assuming
that they then close their official branch, and make the version inside
Python the maintained one).
That is also independent of whet
On Tue, Nov 4, 2008 at 23:19, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> FWIW, I don't consider the current bazaar installation sufficient here.
> It does give a useful insight for those of us unfamiliar with that
> kind of system, and certainly allows those who want to develop with bzr
> alre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 6:09 AM, Paul Moore wrote:
I'll freely admit a (not very) hidden bias here - the slowness of an
initial clone (or going through the "download a shared repo, unpack
it, create a branch and update" rigmarole) makes this a nasty test
On 2008.11.05 11:09:24 +, Paul Moore wrote:
> An average user (ie, not a core developer) finds an issue, and has an
> idea how to fix it. He raises a tracker item, checks out the Python
> sources, makes a fix, and wants to upload it to the tracker. Key
> points here are the initial work needed
Terry Reedy wrote:
> Stefan Behnel wrote:
>> I think the main advantage for stdlib modules is actually the maintenance
>> cost. Having a single, easy-to-read code base for extension modules that
>> compiles without modification in Py2.6/7 and Py3.0/3.1 (and 2.3, 2.4 and
>> 2.5), makes life a lot ea
(working on spam system - just hit 'd')
___
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
2008/11/3 Brett Cannon <[EMAIL PROTECTED]>:
> At this point I am looking for any suggestions for fundamental usage
> scenarios that I am missing from the PEP. If you think the few already
> listed are missing some core part of a VCS, please let me know.
My apologies, I can't check if this is alrea
2008/11/5 Stephen J. Turnbull <[EMAIL PROTECTED]>:
> > I see no excuse to let the fact that it's Python make it acceptable
> > to have an application with otherwise unacceptable performance.
>
> Barry and many others obviously find the performance of non-git VCSes
> acceptable. On the other hand
On Tue, Nov 4, 2008 at 9:06 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> The project has made inclusion into Python's stdlib a goal right from the
>> beginning.
>
> Ah, that changes my view of it significantly. If the authors want to
> contribute it to Python some day, I'm looking forward to
43 matches
Mail list logo
