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 and
me sane (or is it the
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 maintain compatibility, so be it.
There is still the
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 and
[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:
Timcd to the root of your release24-maint
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,
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, functions
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 sure.
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 and
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
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
[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. If
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:
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 manages to
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 here:
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 at
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
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.
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; just let it be documented as
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,
either.
It's
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
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
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 thing you
[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 dev faq
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 in 2.5a2, if I'm
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:
http://docs.python.org/dev/whatsnew/other-lang.html#SECTION000131.
(Fred, is it possible to set the anchors used for
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 incompatibility
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. Email
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 please
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 to keep
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 and
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 and
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
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
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 green
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 bindings on
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 syntax,
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
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 buildbots should
-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 Python dev
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
suggest that it will be
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 be
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 strictly
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 requiring
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 the
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 assigns
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 indexing
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
[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
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 NumPy's view
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???
print A0
What do you
- Original Message -
From: Walter Dörwald [EMAIL PROTECTED]
To: H.Yamamoto [EMAIL PROTECTED]
Cc: python-dev python-dev@python.org
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.
51 matches
Mail list logo
