On Sun, 2006-03-19 at 20:40 -0800, Guido van Rossum wrote:
I'm -0 for changing this in 3.0; a larger-scale reorganization could
be undertaken but it's not a big priority.
Before you spend more energy on this, I'd like to address the process
for Python 3000, which is too chaotic right now.
On 3/18/06, Barry Warsaw [EMAIL PROTECTED] wrote:
On Fri, 2006-03-17 at 23:48 -0800, Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C)
On Sun, 2006-03-19 at 19:45 -0800, Guido van Rossum wrote:
-1. See my response in the other thread. The focus on 'Error' is
mistaken, and we have a large body of existing code that derives from
Exception.
Just to be clear, are you saying -1 only for Python 2.5 or -1 also for
Python 3.0? If
On Saturday 18 March 2006 18:48, Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want to
see in 2.5, bring it up now. I want to
On Monday 20 March 2006 00:49, Anthony Baxter wrote:
I'd still like to push 2.4.3rc1 out in a couple of days time, with
2.4.3 final next week, and then maybe aim for 2.5a1 a week or two
later? How does that work for everyone?
I should be fine to build the documentation Wednesday night (US
Neal Norwitz [EMAIL PROTECTED] wrote:
I posted a message to c.l.p about the upcoming alpha 1.
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want
Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want to see
in 2.5, bring it up now. I want to strive for feature completeness by
[Neal]
I posted a message to c.l.p about the upcoming alpha 1.
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want to see
in 2.5, bring it up now. I
On Fri, 2006-03-17 at 23:48 -0800, Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want to see
in 2.5, bring it up now. I want to
On Fri, 2006-03-17 at 23:48 -0800, Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want to see
in 2.5, bring it up now. I want to
Raymond Hettinger [EMAIL PROTECTED] wrote:
They include [...] the str.partition function,
Where is the current version of this patch?
After reharsing the archives, I have an additional suggestion which I didn't
find already mentioned in the discussion. What about:
str.partition() - (left,
[Barry Warsaw]
Oh, also, we have a couple of additions to the PySet C API.
I'll work on putting together an SF patch for them over the weekend.
What are you proposing to add to the PySet API?
Raymond
___
Python-Dev mailing list
[Raymond]
FYI, I have several non-major C components to go in but not in time for alpha
1.
They include some minor fix-ups in the sets module, the str.partition
function,
add gc to itertools.tee, a couple of functions in binascii, add
itertools.izip_longest, Crutcher's patch to make exec
13 matches
Mail list logo
