Re: [Python-Dev] beta1 coming real soon

Neal Norwitz wrote: > It's June 9 in most parts of the world. The schedule calls for beta 1 > on June 14. That means there's less than 4 days until the expected > code freeze. Please don't rush to get everything in at the last > minute. The buildbots should remain green to keep Anthony happy an

Re: [Python-Dev] Subversion repository question - back up to older versions

[EMAIL PROTECTED] wrote: > >> I have three Python branches, trunk, release23-maint and > >> release24-maint. In the (for example) release24-maint, what > svn up >> command would I use to get to the 2.4.2 version? > > Tim> First question: > > Tim>cd to the root of your rele

[Python-Dev] UUID module

Quite a few people have expressed interest in having UUID functionality in the standard library, and previously on this list some suggested possibly using the uuid.py module i wrote: http://zesty.ca/python/uuid.py This module provides a UUID class, functions for generating version 1, 3, 4, an

Re: [Python-Dev] UUID module

Ka-Ping Yee wrote: > Quite a few people have expressed interest in having UUID > functionality in the standard library, and previously on this > list some suggested possibly using the uuid.py module i wrote: > > http://zesty.ca/python/uuid.py +1! > This module provides a UUID class, functio

Re: [Python-Dev] Python Benchmarks

Fredrik Lundh wrote: > M.-A. Lemburg wrote: > >> The results were produced by pybench 2.0 and use time.time >> on Linux, plus a different calibration strategy. As a result >> these timings are a lot more repeatable than with pybench 1.3 >> and I've confirmed the timings using several runs to make

Re: [Python-Dev] beta1 coming real soon

Neal Norwitz wrote: > It's June 9 in most parts of the world. The schedule calls for beta 1 > on June 14. That means there's less than 4 days until the expected > code freeze. Please don't rush to get everything in at the last > minute. The buildbots should remain green to keep Anthony happy an

Re: [Python-Dev] UUID module

Fredrik> 6. Combine 2 and 3: require the user to pass in a MAC argument Fredrik> to uuid1, but provide a SlowGetMacAddress helper that wraps Fredrik> the existing code. Or make the MAC address an optional arg to uuid1. If given, use it. If not, use the slow lookup (then

Re: [Python-Dev] Python Benchmarks

M.-A. Lemburg wrote: > You can download a current snapshot from: > > http://www.egenix.com/files/python/pybench-2.0-2006-06-09.zip believe it or not, but this hangs on my machine, under 2.5 trunk. and it hangs hard; nether control-c, break, or the task manager manages to kill it. if it's any

Re: [Python-Dev] UUID module

[EMAIL PROTECTED] wrote: > Fredrik> 6. Combine 2 and 3: require the user to pass in a MAC argument > Fredrik> to uuid1, but provide a SlowGetMacAddress helper that wraps > Fredrik> the existing code. > > Or make the MAC address an optional arg to uuid1. If given, use it.

[Python-Dev] beta1 coming real soon

> If you plan to make a checkin adding a feature (even a simple one), > you oughta let people know by responding to this message. Please get > the bug fixes in ASAP. Remember to add tests! Is there any chance to fix mbcs bug? I think this is critical... My patch is here: http://python.org/sf/145

Re: [Python-Dev] Python Benchmarks

Fredrik Lundh wrote: > M.-A. Lemburg wrote: > >> You can download a current snapshot from: >> >> http://www.egenix.com/files/python/pybench-2.0-2006-06-09.zip > > believe it or not, but this hangs on my machine, under 2.5 trunk. and > it hangs hard; nether control-c, break, or the task manager

Re: [Python-Dev] beta1 coming real soon

H.Yamamoto wrote: >> If you plan to make a checkin adding a feature (even a simple one), >> you oughta let people know by responding to this message. Please get >> the bug fixes in ASAP. Remember to add tests! > > Is there any chance to fix mbcs bug? I think this is critical... > My patch is he

Re: [Python-Dev] UUID module

Fredrik> the reason for making it a required argument is to make it Fredrik> clear that the code is using a "suboptimal" way to get at the Fredrik> MAC value. Fredrik> explicit is better than implicit etc etc. Can't we expect there will be a faster way to get at the MAC address a

Re: [Python-Dev] Subversion repository question - back up to older versions

Giovanni> If you realize that each file/directory in Subversion is Giovanni> uniquely identified by a 2-space coordinate system [url, Giovanni> revision] ... Thanks, I found this very helpful. I found it so helpful that I added a question to the dev faq with this as the answer. Hope

Re: [Python-Dev] 2.5 issues need resolving in a few days

There was also discussion of a change to the way "quit" works in interactive mode. I see no record of it, so I guess that's not going in, either. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "I saw `cout' being shifted "Hello world" times to the left and stopped

Re: [Python-Dev] 2.5 issues need resolving in a few days

On 6/9/06, Aahz <[EMAIL PROTECTED]> wrote: > There was also discussion of a change to the way "quit" works in > interactive mode. I see no record of it, so I guess that's not going in, > either. It's already in 2.5a2, if I'm thinking of the same thing you are... Paul.

Re: [Python-Dev] UUID module

On 6/9/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:    6.  Combine 2 and 3: require the user to pass in a MAC argument   to uuid1, but provide a SlowGetMacAddress helper that wraps   the existing code.That sounds like the right thing to do, although I wouldn't call it "slow"; ju

Re: [Python-Dev] 2.5 issues need resolving in a few days

Paul Moore wrote: > On 6/9/06, Aahz <[EMAIL PROTECTED]> wrote: >> There was also discussion of a change to the way "quit" works in >> interactive mode. I see no record of it, so I guess that's not going in, >> either. > > It's already in 2.5a2, if I'm thinking of the same thing you are... > Paul.

Re: [Python-Dev] 2.5 issues need resolving in a few days

On Friday, June 09, 2006, at 03:34PM, Georg Brandl <[EMAIL PROTECTED]> wrote: >Paul Moore wrote: >> On 6/9/06, Aahz <[EMAIL PROTECTED]> wrote: >>> There was also discussion of a change to the way "quit" works in >>> interactive mode. I see no record of it, so I guess that's not going in, >>> ei

Re: [Python-Dev] beta1 coming real soon

Thanks for the reminder. What I intend to add is to finalize the PCBuild8 directory, and fix CRT runtime error handling for VC8. The change as proposed involves adding macros around a select few CRT calls (fopen, strftime, etc) where user supplied parameters are passed to the CRT innards. Code w

Re: [Python-Dev] 2.5 issues need resolving in a few days

On 6/8/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: > The most important outstanding issue is the xmlplus/xmlcore issue. > It's not going to get fixed unless someone works on it. There's only > a few days left before beta 1. Can someone please address this? If > that means reverting changes to ma

Re: [Python-Dev] 2.5 issues need resolving in a few days

On Fri, Jun 09, 2006, Paul Moore wrote: > On 6/9/06, Aahz <[EMAIL PROTECTED]> wrote: >> >> There was also discussion of a change to the way "quit" works in >> interactive mode. I see no record of it, so I guess that's not going in, >> either. > > It's already in 2.5a2, if I'm thinking of the same

Re: [Python-Dev] Subversion repository question - back up to older versions

[EMAIL PROTECTED] wrote: > Giovanni> If you realize that each file/directory in Subversion is > Giovanni> uniquely identified by a 2-space coordinate system [url, > Giovanni> revision] ... > > Thanks, I found this very helpful. I found it so helpful that I > added a question to the de

Re: [Python-Dev] 2.5 issues need resolving in a few days

On 6/9/06, Aahz <[EMAIL PROTECTED]> wrote: On Fri, Jun 09, 2006, Paul Moore wrote:> On 6/9/06, Aahz <[EMAIL PROTECTED]> wrote: There was also discussion of a change to the way "quit" works in >> interactive mode.  I see no record of it, so I guess that's not going in,>> either.>> It's already i

Re: [Python-Dev] 2.5 issues need resolving in a few days

On Fri, Jun 09, 2006 at 07:28:47AM -0700, Aahz wrote: > Okay, I guess I mis-remembered what had been agreed to. Should this go > into What's New? Already there: . (Fred, is it possible to set the anchors used for

Re: [Python-Dev] 2.5 issues need resolving in a few days

On Friday 09 June 2006 10:28, Guido van Rossum wrote: > Really? The old situation is really evil, and the new approach is at > least marginally better by giving users a way to migrate to a new > non-evil approach. What exactly is the backwards incompatibility you > speak of? The "incompatibili

Re: [Python-Dev] Some more comments re new uriparse module, patch 1462525

On Thursday, Jun 8, 2006, Mike Brown writes: > >It appears that Paul uploaded a new version of his library on June 3: >http://python.org/sf/1462525 >I'm unclear on the relationship between the two now. Are they both up for >consideration? That version was in response to comments from JJ Lee. Ema

Re: [Python-Dev] 2.5 issues need resolving in a few days

I will be looking at the open AST issues today. Jeremy On 6/9/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: > The most important outstanding issue is the xmlplus/xmlcore issue. > It's not going to get fixed unless someone works on it. There's only > a few days left before beta 1. Can someone plea

Re: [Python-Dev] beta1 coming real soon

"Neal Norwitz" <[EMAIL PROTECTED]> writes: > It's June 9 in most parts of the world. The schedule calls for beta 1 > on June 14. That means there's less than 4 days until the expected > code freeze. Please don't rush to get everything in at the last > minute. The buildbots should remain green

Re: [Python-Dev] beta1 coming real soon

Neal Norwitz wrote: > It's June 9 in most parts of the world. The schedule calls for beta 1 > on June 14. That means there's less than 4 days until the expected > code freeze. Please don't rush to get everything in at the last > minute. The buildbots should remain green to keep Anthony happy an

Re: [Python-Dev] beta1 coming real soon

Neal Norwitz wrote: > It's June 9 in most parts of the world. The schedule calls for beta 1 > on June 14. That means there's less than 4 days until the expected > code freeze. Please don't rush to get everything in at the last > minute. The buildbots should remain green to keep Anthony happy an

[Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Hello, Recently I discovered that a small change to the Python grammar that could help me a lot. It's simply this: Currently, the expression "x[]" is a syntax error. I suggest that it will be a valid syntax, and equivalent to "x[()]", just as "x[a, b]" is equivalent to "x[(a, b)]" right now. I d

Re: [Python-Dev] [Web-SIG] wsgiref doc draft; reviews/patches wanted

At 02:56 PM 6/7/2006 -0400, Joe Gregorio wrote: >Phillip, > >1. It's not really clear from the abstract 'what' this library >provides. You might want >to consider moving the text from 1.1 up to the same level as the abstract. Done. >2. In section 1.1 you might want to consider dropping the

Re: [Python-Dev] beta1 coming real soon

On 9-jun-2006, at 8:23, Neal Norwitz wrote: > It's June 9 in most parts of the world. The schedule calls for beta 1 > on June 14. That means there's less than 4 days until the expected > code freeze. Please don't rush to get everything in at the last > minute. The buildbots should remain gree

Re: [Python-Dev] beta1 coming real soon

On 9-jun-2006, at 17:34, Thomas Heller wrote: > > > The other question is about feature freeze on external libraries. > Is it strictly forbidden to add new features in ctypes during the > (Python) beta period? Now that you mention the feature freeze... The tools that generate the Carbon binding

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

This is an elaborate joke, right? On 6/9/06, Noam Raphael <[EMAIL PROTECTED]> wrote: > Hello, > > Recently I discovered that a small change to the Python grammar that > could help me a lot. > > It's simply this: Currently, the expression "x[]" is a syntax error. I > suggest that it will be a valid

[Python-Dev] FYI: wsgiref is now checked in

The checked-in code substantially matches the public 0.1 release of wsgiref. There are some minor changes to the docs and the test module, but these have also been made in the SVN trunk of wsgiref's home repository, so that future releases don't diverge too much. The plan is to continue to ma

Re: [Python-Dev] beta1 coming real soon

On 6/9/06, Thomas Heller <[EMAIL PROTECTED]> wrote: Neal Norwitz wrote:> It's June 9 in most parts of the world.  The schedule calls for beta 1> on June 14.  That means there's less than 4 days until the expected> code freeze.  Please don't rush to get everything in at the last > minute.  The build

Re: [Python-Dev] beta1 coming real soon

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 9 Jun 2006 09:54:29 -0700 "Brett Cannon" <[EMAIL PROTECTED]> wrote: > Do enough people use Google Calendar or a calendar app that support > iCal feeds that it would be useful for someone to maintain a Gcal > calendar that has the various Pytho

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

On 6/9/06, Nicko van Someren <[EMAIL PROTECTED]> wrote: > On 9 Jun 2006, at 17:44, Guido van Rossum wrote: > > > This is an elaborate joke, right? > > > > On 6/9/06, Noam Raphael <[EMAIL PROTECTED]> wrote: > ... > >> It's simply this: Currently, the expression "x[]" is a syntax > >> error. I > >> s

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

On 9 Jun 2006, at 17:44, Guido van Rossum wrote: > This is an elaborate joke, right? > > On 6/9/06, Noam Raphael <[EMAIL PROTECTED]> wrote: ... >> It's simply this: Currently, the expression "x[]" is a syntax >> error. I >> suggest that it will be a valid syntax, and equivalent to "x[()]", >> ju

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

On 6/9/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: ... > The language doesn't have zero-dimensional arrays, although it doesn't > prevent users from defining them. but why would one want to index a > zero-dimensional array, since it has no dimensions? It should be > written as x, not x[]. W

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Guido van Rossum wrote: > On 6/9/06, Nicko van Someren <[EMAIL PROTECTED]> wrote: [...] > > The language doesn't have zero-dimensional arrays, although it doesn't > prevent users from defining them. but why would one want to index a > zero-dimensional array, since it has no dimensions? It should b

Re: [Python-Dev] beta1 coming real soon

Thomas Heller wrote: >> If you plan to make a checkin adding a feature (even a simple one), >> you oughta let people know by responding to this message. Please get >> the bug fixes in ASAP. Remember to add tests! > > The other question is about feature freeze on external libraries. > Is it stric

Re: [Python-Dev] beta1 coming real soon

Ronald Oussoren wrote: > How hard is the feature freeze? Would it be possible to update the > Carbon bindings after beta1? Given Apple's focus on backward > compatibility the update should only add new functionality, not > remove existing functions/types. I'd say it's absolute wrt. to requir

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Noam Raphael wrote: > This PEP suggests to allow the use of an empty subscript list, for > example ``x[]``, which is currently a syntax error. It is suggested > that in such a case, an empty tuple will be passed as an argument to > the __getitem__ and __setitem__ methods. This is consistent with t

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Alex Martelli wrote: > Well, x=23 on one side, and x[]=23 aka x[()]=23 on the other, have > drastically different semantics. Indexing refers to the contents of > the zero-dimensional container, rather than to a name to which the > container happens to be bound (but isn't any more, once one assign

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Tim Hochberg wrote: > In Numpy, a 0-D array [for example, array(5)] is almost, but not quite, > equivalent to scalar [for example, 5]. The difference is that the > former is mutable. Hmmm, I hadn't considered that. I suppose this is something that arises from NumPy's "view" semantics of indexi

[Python-Dev] -Wi working for anyone else?

I discovered last night that if you run ``./python.exe -Wi`` the interpreter exists rather badly::  Fatal Python error: PyThreadState_Get: no current threadAnyone else seeing this error on any other platforms or have an inkling of what checkin would cause this? -Brett __

Re: [Python-Dev] -Wi working for anyone else?

[Brett Cannon] > I discovered last night that if you run ``./python.exe -Wi`` the interpreter > exists rather badly:: > > Fatal Python error: PyThreadState_Get: no current thread > > Anyone else seeing this error on any other platforms or have an inkling of > what checkin would cause this? See c

[Python-Dev] Inject some tracing ...

Hello I use the code below to inject a tracing function in my builtins that prints out the file and line number where it occurs, and automatically nicely formats the objects it receives. This allows me to get traces like that in my web server log files, or in my cmdline program outputs: [Fri Jun

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

On Jun 9, 2006, at 4:55 PM, Greg Ewing wrote: ... > Think about how you get from an N dimensional array to > an N-1 dimensional array: you index it, e.g. > > A2 = [[1, 2], [3, 4]] # a 2D array > > A1 = A2[1] # a 1D array > > A0 = A1[1] # a 0D array??? > > print A0 > > What do you think

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Greg Ewing wrote: > Tim Hochberg wrote: > >> In Numpy, a 0-D array [for example, array(5)] is almost, but not quite, >> equivalent to scalar [for example, 5]. The difference is that the >> former is mutable. > > Hmmm, I hadn't considered that. I suppose this is > something that arises from Num

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Alex Martelli wrote: > On Jun 9, 2006, at 4:55 PM, Greg Ewing wrote: > ... > >>Think about how you get from an N dimensional array to >>an N-1 dimensional array: you index it, e.g. >> >> A2 = [[1, 2], [3, 4]] # a 2D array >> >> A1 = A2[1] # a 1D array >> >> A0 = A1[1] # a 0D array??? >> >>

Re: [Python-Dev] beta1 coming real soon

- Original Message - From: "Walter Dörwald" <[EMAIL PROTECTED]> To: "H.Yamamoto" <[EMAIL PROTECTED]> Cc: "python-dev" Sent: Friday, June 09, 2006 7:56 PM Subject: Re: [Python-Dev] beta1 coming real soon > The best way to throughly test the patch is of course to check it in. ;) Is it to

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Nick Coghlan wrote: > I think it more comes from the n-dimensional array approach - 'n=0' is > then a natural issue to consider. But only if it makes sense. I still think there are some severe conceptual difficulties with 0D arrays. One is the question of how many items it contains. With 1 or mo

Re: [Python-Dev] Pre-PEP: Allow Empty Subscript List Without Parentheses

Greg Ewing wrote: > I'm having trouble seeing a real use for a 0D array as > something distinct from a scalar, as opposed to them > just being an oddity that happens to arise as a side > effect of the way Numeric/Numpy are implemented. This has been rehashed over and over again on numpy-discussio