On behalf of the Python development team and the Python community,
I'm happy to announce the release of Python 2.5.1 (release
candidate 1).
This is the first bugfix release of Python 2.5. Python 2.5 is now
in bugfix-only mode; no new features are being added. According to
the release notes, ov
On Wednesday 11 April 2007 07:07, Martin v. Löwis wrote:
> Raymond Hettinger schrieb:
> > It looks like the release candidate has been held-up for a bit.
> > If it is going to stay held-up for a few days, can we unfreeze
> > it so some bugfixes can go in (fixing the +0/-0 problem,
> > eliminating
[Facundo Batista]
>The names, as the new functions will be discussed here in the second
>step. For example, I'm not absolute sure that something like...
>
Decimal("1100").xor(Decimal("0110")
>Decimal("1010")
>
>...is actually needed.
>
It doesn't matter. We promise to offer a full impleme
Raymond Hettinger wrote:
> As promised in the decimal.py header, the spec
> updates should all be considered as bugs and backported at some point
> after they are fully tested and we're happy with them all around.
> Also, as promised, the module should continue to run on Py2.3.
Ok. So far, I'm
On Tue, Apr 10, 2007 at 07:30:13AM -0400, A.M. Kuchling wrote:
> Something's broken; I'm looking into it.
David Goodger found the problem and repaired it. It was nothing to do
with the PEPs; another directory was causing the build process to stop
with an error.
--amk
___
> No, the release binaries are all produced, and just await upload.
Woohoo!
> If it's an urgent issue, we need another RC.
> If it isn't urgent (e.g. not a regression relative to 2.5.0),
> I think it should wait for 2.5.2. (IMHO all, of course)
These bug fixes will have to wait.
Raymond
---
Raymond Hettinger schrieb:
> It looks like the release candidate has been held-up for a bit. If
> it is going to stay held-up for a few days, can we unfreeze it so
> some bugfixes can go in (fixing the +0/-0 problem, eliminating some
> segfaults, and fixing some exception code)?
No, the release b
Do any of the Iceland sprinters (Fredrik or Andrew perhaps) know why the
USE_FAST section is segregated and whether it is supposed to be on or off by
default?
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
It looks like the release candidate has been held-up for a bit. If it is going
to stay held-up for a few days, can we unfreeze it so some bugfixes can go in
(fixing the +0/-0 problem, eliminating some segfaults, and fixing some
exception code)?
Raymond
On 4/10/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
The PEP I checked in for Travis hasn't turned up on the website, despite
building without warnings when I run pep2html.py. The changes I made to
PEP 0 haven't turned up either.
I thought the subversion commit hook for the PEPs folder caused th
Now that the checkin is done, I don't think it needs to be reverted. But, in
general, we should probably abstain from making wholesale revisions that add
zero value for the users.
The stylistic change from:
ValueError, 'foo'
ValueError('foo')
is fine.
Changing MockThreading to subcla
Facundo Batista wrote:
> Martin v. Löwis wrote:
> ...
>
>> think it should treat all 2xx responses as success. Callers can
>> then still check the response code themselves if they need to.
>
> The same I think. If nobody has a conflic with this decission, I'll fix
> this.
Nobody raised any object
On Tue, Apr 10, 2007 at 07:58:02PM +1000, Nick Coghlan wrote:
> Have I forgotten a step in the process somewhere, or is something broken?
Something's broken; I'm looking into it.
--amk
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python
Carl Banks wrote:
> Another little mistake I made: looking at the Python source, it seems
> that most C defines do not use the Py_ prefix, so probably we shouldn't
> here. Sorry.
Most of the #define's aren't exposed via Python.h and aren't part of the
public C API. The public ones are meant to
The PEP I checked in for Travis hasn't turned up on the website, despite
building without warnings when I run pep2html.py. The changes I made to
PEP 0 haven't turned up either.
I thought the subversion commit hook for the PEPs folder caused the
website to update automatically.
Have I forgotten
On 09/04/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> > I have skimmed (briefly, I'll admit!) the pre-PEP, but I've found it
> > extremely difficult to find a simple example of the basic (in my view)
> > use case of an undifferentiated block of bytes.
> >
>
> This is a great suggestion and it w
16 matches
Mail list logo
