-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 12:35 AM, raymond.hettinger wrote:
Author: raymond.hettinger
Date: Thu May 8 06:35:20 2008
New Revision: 62848
Log:
Frozensets do not benefit from autoconversion.
Since the trunk buildbots appear to be mostly happy (well those
On Thu, May 8, 2008 at 6:32 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Since the trunk buildbots appear to be mostly happy (well those that are
> connected anyway), and because I couldn't get the releases out last night,
> I'll let this one slide. I'd like to find a way to more forcefully enfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 7:54 AM, Benjamin Peterson wrote:
On Thu, May 8, 2008 at 6:32 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
Since the trunk buildbots appear to be mostly happy (well those
that are
connected anyway), and because I couldn't get the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
From: "Barry A. Warsaw" <[EMAIL PROTECTED]>
Date: May 8, 2008 7:55:10 AM EDT
To: [EMAIL PROTECTED]
Subject: [issue2547] Py30a4 RELNOTES only cover 30a1 and 30a2
Reply-To: Tracker <[EMAIL PROTECTED]>
Barry A. Warsaw <[EMAIL
Barry Warsaw schrieb:
> This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical problems.
All community members with svn write privileges must subscribe to the
Python developer list. Committers must check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 8:21 AM, Christian Heimes wrote:
Barry Warsaw schrieb:
This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical problems.
In this case
Christian Heimes wrote:
Barry Warsaw schrieb:
This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical problems.
All community members with svn write privileges must subscribe to the
Python developer li
On Thu, May 8, 2008 at 8:20 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Or aggressively back out any changes from freeze time to tag time. If we
> don't add the commit hook lock, I will be very strict about this come the
> betas.
I know this way is fairly entrenched in the python release proces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've created the tags for 3.0a5 and 2.6a3, and the tarballs look good,
so I'm lifting the commit freeze for these two branches. Thanks
everyone, and look for the release announcements in a little while.
- -Barry
-BEGIN PGP SIGNATURE-
V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 9:41 AM, Michael Urman wrote:
On Thu, May 8, 2008 at 8:20 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
Or aggressively back out any changes from freeze time to tag time.
If we
don't add the commit hook lock, I will be very stric
On Thu, May 8, 2008 at 5:03 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> So there was a release critical issue open about making sure to update
> Py3k's RELNOTES file. I've updated the release script so that I'll be sure
> to edit this file, however I'm not sure what the policy is on updating it
On 2008-05-06 15:55, Atsuo Ishimoto wrote:
(I changed subject)
Thank you for your comment.
On Tue, May 6, 2008 at 8:45 PM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
For sys.stdout this doesn't make sense at all, since it hides encoding
errors for all applications using sys.stdout as piping m
On 2008-05-06 16:10, Nick Coghlan wrote:
Atsuo Ishimoto wrote:
I proposed to make the Unicode repr() output a regular encoding
that's being implemented by a codec. You could then easily
change the encoding to whatever you need for your application
or console.
I think global setting is not
Barry Warsaw schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 8:21 AM, Christian Heimes wrote:
Barry Warsaw schrieb:
This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical p
Given that we cannot depend on timely mail/news propagation or on exact
day-ahead scheduling of a freeze, a current freeze notice either from the
repository or on a .../dev/status page might work better.
___
Python-3000 mailing list
Python-3000@pyth
Functions that map unicode->unicode or bytes->bytes could be called
transcoders. Each type could be given a .transcode method to go along with
but contrast with .encode or .decode.
tjr
___
Python-3000 mailing list
Python-3000@python.org
http://mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the third alpha release of Python 2.6, and the
fifth alpha release of Python 3.0.
Please note that these are alpha releases, and as such are not
suitable
Terry Reedy schrieb:
Given that we cannot depend on timely mail/news propagation or on exact
day-ahead scheduling of a freeze, a current freeze notice either from the
repository or on a .../dev/status page might work better.
Nobody is going to look at such a page before making a commit :)
Ge
18 matches
Mail list logo
