$Revision: 61470 $
Last-Modified: $Date: 2008-03-17 19:27:00 -0500 (Mon, 17 Mar 2008) $
Author: Neal Norwitz, Barry Warsaw
Status: Draft
Type: Informational
Created: 29-June-2006
Python-Version: 2.6
Python-Version: 3.0
Post-History: 17-Mar-2008
Abstract
This document describes the devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 17, 2008, at 11:35 PM, Guido van Rossum wrote:
> What do I do for something that should absolutely go into the 2.6final
> release (say) but is otherwise pretty minor? I've been using critical
> to make sure it doesn't get put off until past the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2008, at 12:11 AM, Guido van Rossum wrote:
> Hm... This feels a bit like inflation of priorities to me; there would
> be lots of critical bugs and quite a few release blockers... The
> highest priority just pertains to the upcoming release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2008, at 2:04 AM, Travis Oliphant wrote:
>
> Hey Barry,
>
> Thanks for putting this PEP together. This is really helpful.
Hi Travis... thanks!
> I didn't see discussion of PEP 3118 and it's features back-ported to
> Python 2.6. I've alre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 19, 2008, at 3:20 AM, Jeffrey Yasskin wrote:
> +1 to assert* from me. the fail* variants always feel like
> double-negatives. I also always use assertTrue instead of assert_. But
> I don't care enough to argue about it. :)
I'm in the camp that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 19, 2008, at 3:57 AM, Jeff Rush wrote:
>
> I and others appreciate your call for more patches on various
> topics. However
> a long delay in applying them will discourage contribution. Are you
> open to
> giving certain others patch view/c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm happy to announce that we now have available for public
consumption, the Python source code for 2.5, 2.6 and 3.0 available
under the Bazaar distributed version control system.
The current Subversion repository is still the master copy of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 20, 2008, at 3:58 PM, Christian Heimes wrote:
> Barry Warsaw schrieb:
>> I'm happy to announce that we now have available for public
>> consumption, the Python source code for 2.5, 2.6 and 3.0 available
>> un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 20, 2008, at 5:49 PM, Christian Heimes wrote:
> Barry Warsaw schrieb:
>> I'm happy to announce that we now have available for public
>> consumption, the Python source code for 2.5, 2.6 and 3.0 available
>> under the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 21, 2008, at 5:28 PM, Paul Moore wrote:
>
> One thing I really like the idea of with Mercurial for my situation
> (non-committer) is the mq extension, which lets me manage my changes
> as a "stack of patches" - so I'm completely working with pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 17, 2008, at 12:27 AM, Martin v. Löwis wrote:
>> 'critical' is fine (or 'immediate'). My problem before was that I
>> couldn't do one query that gave me all the critical issues for
>> both 2.6 and 3.0. That certainly could have been pebk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 22, 2008, at 11:31 AM, Martin v. Löwis wrote:
>> Thanks Martin, I think this will work for now. Is there any way
>> you can allow me to edit this query too?
>
> Not easily.
>
> I could just remove it, and allow you to create a new one (or you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've missed most of this thread, but let me just put my two cents in.
I'd still like a future import to turn on unicode string literals (or
more accurately, treat unadorned string literals as unicodes). As
someone who is striving mightily to ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 24, 2008, at 11:06 PM, [EMAIL PROTECTED] wrote:
>Barry> All the gory details are documented here:
>
>Barry> http://www.python.org/dev/bazaar
>
> Thanks. I checked out, made a branch named test3, changed
> Makefile.pre.in
> to ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2008, at 2:21 AM, Neal Norwitz wrote:
> The next releases of 2.6/3.0 are planned for April 2, just over a week
> from now. There is much work that needs to be done. The buildbots
> are in a pretty sad state and the gods are seeing too much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2008, at 8:14 AM, Facundo Batista wrote:
> 2008/3/26, Neal Norwitz <[EMAIL PROTECTED]>:
>
>> We need to get the tests for Python to be more stable so we can push
>> out solid releases. In order to achieve this result, we need tests
>> that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2008, at 5:10 PM, Benjamin Peterson wrote:
> There are also some backporting issues in that pile. Should those
> hold up
> betas? (when we get there)
Yes, but I would simply release the monthly alpha and push the beta
back a month.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 29, 2008, at 5:11 PM, Benjamin Peterson wrote:
> Once you've pushed the branches, is there a way to remove them?
Do you mean the local branches? If yes, then 'rm -rf mymergedbranch'
does exactly what you want. :)
- -Barry
-BEGIN PGP S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 29, 2008, at 6:00 PM, Benjamin Peterson wrote:
>
> No, I mean the pushed version on code.python.org.
Not unless you have shell or sftp access, which you probably don't.
It's not a big deal though except for a mild feeling of
uncleanliness.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2008, at 3:35 AM, Martin v. Löwis wrote:
> Likewise, if you are accessing the repository over bzr+ssh, in
> general,
> you can just ssh to the machine, and do a regular ls. In the specific
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just another heartbeat reminder that I intend to release the next
alphas for Python 2.6 and 3.0 this Wednesday April 2nd, at
approximately 6pm Eastern time (UTC 2200).
Current status: the buildbots for both the trunk and 3.0 look
relatively good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a reminder that I am going to start building the next alpha
releases for Python 2.6 and 3.0 now. Please, no checkins unless you
get approval from me, and until you hear that the freeze is lifted.
I am now on freenode #python-dev, IM, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 2, 2008, at 6:00 PM, Barry Warsaw wrote:
>
> This is a reminder that I am going to start building the next alpha
> releases for Python 2.6 and 3.0 now. Please, no checkins unless you
> get approval from me, and until you h
Barry
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR/WImHEjvBPtnXfVAQJmoQP+MzqNDI+Xt8zua/FE7Ca4TVXoIIy2uoOm
I1i3+vmevZ9vtAb9hcGwfEgPY4LSwb9Js4KnJJWMPaMuFJK4NgGoiMdj+t4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 4, 2008, at 3:03 PM, Terry Reedy wrote:
>
> "Gerhard Häring" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> | In case you don't know already, the website is not fully updated,
> yet:
> |
> | http://www.python.org/download/rele
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 25, 2008, at 2:05 PM, [EMAIL PROTECTED] wrote:
>
>>> Did I misread the directions or do I really need the --create-prefix
>>> arg?
>
>Barry> You do, the first time you push a user branch because
> users/skip
>Barry> doesn't exist yet.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 17, 2008, at 10:48 AM, Guido van Rossum wrote:
> This is going to be a major administrative hassle. Obviously you have
> to be extremely cautious with the private part of the certificate, or
> it's worthless. That means that there will probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 17, 2008, at 11:32 AM, Christian Heimes wrote:
> Barry Warsaw schrieb:
>> MvL is leading this effort and is currently trying to get a code
>> signing certificate (my attempts having utterly failed on the Mac ;).
>> Pleas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a reminder that the LAST planned alpha releases of Python 2.6
and 3.0 are scheduled for next Wednesday, 07-May-2008. Please be
diligent over the next week so that none of your changes break
Python. The stable buildbots look moderately
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2008, at 6:33 PM, Andrew McNabb wrote:
On Thu, May 01, 2008 at 12:55:22PM -0700, Guido van Rossum wrote:
I'm not proud of this, but I don't see a way around it. The
alternative would be to make it a keyword, which seemed excessive
(plus,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2008, at 7:45 PM, Guido van Rossum wrote:
On Thu, May 1, 2008 at 2:27 PM, Christian Heimes <[EMAIL PROTECTED]>
wrote:
Barry Warsaw schrieb:
This is a reminder that the LAST planned alpha releases of Python
2.6
and 3.0 are sch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 2, 2008, at 1:48 AM, [EMAIL PROTECTED] wrote:
etc, though. In the long term, if everyone followed suit on
~/.local, that would be great. But I don't want a ~/Python, ~/Java,
~/Ruby, ~/PHP, ~/Perl, ~/OCaml and ~/Erlang and a $PATH as long
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2008, at 5:05 AM, Nick Coghlan wrote:
The major reasons why I think staying out of people's way by default
is important:
- for people like me (glyph, Georg, etc), it allows us to keep our
home directory organised the way we like it. As
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2008, at 8:03 PM, [EMAIL PROTECTED] wrote:
Am I the only guy who finds software that insists on visible, fixed
files in my home directory rude? vmware, for example, wants a "~/
vmware" directory, but pretty much every other application
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 6, 2008, at 6:38 PM, Christian Heimes wrote:
Guido has accepted my user site directory PEP today.
http://python.org/dev/peps/pep-0370/
I'm about the merge the code. But first I like to let you know some
things and get your opinion.
Very aw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Just a reminder that I'm going to be cutting the releases tonight.
Because of work, I didn't make the 6pm EDT goal, and now I have to run
out for a few hours. I will send another message when I'm ready to
start spinning the release, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 7, 2008, at 9:25 PM, Christian Heimes wrote:
Christian Heimes schrieb:
The py3k branch has a major show stopper, It's leaking references
to the
max.
Fixed ;)
Thanks!
Folks, I apologize. I had some system problems tonight so I fell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 7, 2008, at 9:41 PM, Hirokazu Yamamoto wrote:
Hello.
The py3k branch has a major show stopper, It's leaking references
to the
max.
Is there any chance this leak also will be fixed?
http://bugs.python.org/issue
Not for the alphas,
-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
-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
-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.
-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 w
September 3, 2008.
See PEP 361 for release details:
http://www.python.org/dev/peps/pep-0361/
Enjoy,
- -Barry
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 6:05 PM, Christian Heimes wrote:
I'm working on some extra cool and useful additions to PEP 370. It's
going to make compilation and usage of custom libraries very easy. Sit
back and watch the slide show. :)
Comments? :)
Christi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 3:03 PM, Georg Brandl wrote:
While I'm +0 on the commit hook, it would help if a mail that
announces
a freeze would
- not be hidden in a thread on python-dev and
- have a easily recognizable title, like "[TRUNK FREEZE] ".
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 9, 2008, at 6:44 AM, M.-A. Lemburg wrote:
On 2008-05-08 13:59, Barry Warsaw wrote:
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 bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 9, 2008, at 8:15 AM, [EMAIL PROTECTED] wrote:
In the past I seem to recall that the Python code proper might be
frozen
(for a day or two) before a release, but that it was okay to still
commit
changes to non-code files such as documentatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 9, 2008, at 8:56 AM, Nick Coghlan wrote:
Barry Warsaw wrote:
Single quotes are easier to type so I prefer them. I very rarely
find myself using apostrophes in non-triple quoted strings. I like
it when things are easier to type, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 9, 2008, at 12:25 PM, Jim Kleckner wrote:
Barry Warsaw wrote:
...
For more information and downloadable distributions, see the Python
2.6 website:
http://www.python.org/download/releases/2.6/
The .msi for 2.6a3 seems to be missing from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 12, 2008, at 9:47 AM, Alexandre Vassalotti wrote:
On Mon, May 12, 2008 at 9:24 AM, "Martin v. Löwis"
<[EMAIL PROTECTED]> wrote:
The idea was to replace the orignial module file with its stub.
However, the "svn copy" and edit process isn't t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 12, 2008, at 5:16 PM, Benji York wrote:
On Sat, May 10, 2008 at 10:51 PM, <[EMAIL PROTECTED]> wrote:
It might be useful to have a wiki page which identified some of the
conventions people use.
One such entry could be "Do what python does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 13, 2008, at 7:12 PM, Martin v. Löwis wrote:
If you generated your python subversion ssh key during this time on a
machine fitting the description above, please consider replacing your
keys.
apt-get update ; apt-get upgrade on debian will pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 29, 2008, at 9:14 PM, Aahz wrote:
I just processed two weeks of backlog on python-dev (I'm only a backup
moderator). Would anyone object to changing the list policy so that
non-member posts get discarded instead of held?
How about we recru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are going to postpone the first beta releases by one week. We had
some problems with mail.python.org today, which prompted a query to
Guido from me about the postponement. mail.python.org should now be
back up normally now, as evidenced by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 3, 2008, at 6:55 AM, Eric Smith wrote:
Did some checkin emails get lost yesterday? I didn't see mail for a
checkin of mine, r63895. Looking at http://mail.python.org/pipermail/python-checkins/2008-June/date.html
, it looks like r63887-r63
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 10, 2008, at 9:08 AM, Georg Brandl wrote:
Nick Coghlan schrieb:
Josiah Carlson wrote:
On Mon, Jun 9, 2008 at 7:19 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
On Mon, Jun 9, 2008 at 8:42 PM, Josiah Carlson <[EMAIL PROTECTED]
> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 9, 2008, at 6:33 AM, Jesse Noller wrote:
For the multiprocessing module all I have left is the docs in rest
format - given I'm a rest newbie, it's taking longer than I thought
It's okay if docs don't make it into the beta. That's the kind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So I had planned to do a bunch of work last night looking at the
release blocker issues, but nature intervened. A bunch of severe
thunderstorms knock out my 'net access until this morning.
I'll try to find some time during the day to look at th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 9, 2008, at 7:28 AM, Nick Coghlan wrote:
Benjamin Peterson wrote:
As we approach the planned first betas for 2.6/3.0, my heart sinks
when I see the imposing list of 16 release blockers. [1] Luckily,
most
of the issues have patches that ju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 10, 2008, at 8:07 PM, Guido van Rossum wrote:
I've been sick since Saturday and still don't feel up to much. I've
collected a severe email backlog going back to June 6th. If there's
anything someone really needs me to look at ASAP (e.g. a BDF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 11, 2008, at 1:02 PM, Guido van Rossum wrote:
On Wed, Jun 11, 2008 at 4:35 AM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
So I had planned to do a bunch of work last night looking at the
release
blocker issues, but nature interven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 11, 2008, at 1:15 AM, Stefan Behnel wrote:
Guido van Rossum wrote:
anything someone really needs me to look at ASAP (e.g. a BDFL
decision
affecting the impending beta release) please send me an email
This seems to require a BDFL decision
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 11, 2008, at 1:58 PM, Benjamin Peterson wrote:
On Wed, Jun 11, 2008 at 12:54 PM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
http://bugs.python.org/issue2997
Guido's approved the patch. Please go ahead and apply it. If no
o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 11, 2008, at 4:54 PM, Alexandre Vassalotti wrote:
On Wed, Jun 11, 2008 at 7:35 AM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
My plan is to begin building the betas tonight, at around 9 or 10pm
EDT
(0100 to 0200 UTC Thursday).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, we have a potential showstopper for the betas today. All the
3.0 buildbots are bloody red:
http://www.python.org/dev/buildbot/stable/
Running the tests locally on OS X 10.5 and Ubuntu 8.04 confirm that
the tests hang after test_xmlrpc.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 11, 2008, at 10:16 PM, Guido van Rossum wrote:
On Wed, Jun 11, 2008 at 2:42 PM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
On Jun 11, 2008, at 4:54 PM, Alexandre Vassalotti wrote:
I have two release blockers pending review:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Much thanks to Benjamin Peterson and Alexandre Vassalotti for
providing much help today trying to get the betas out. Unfortunately,
it's not gonna happen today. There are two issues blocking the release.
http://bugs.python.org/issue3088
http:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 5:48 AM, anton wrote:
could someone look for this ... or I am the only one which noticed
that.
ping works but http://bugs.python.org giges after a timeout:
Proxy Error
The proxy server received an invalid response from an u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 7:08 AM, Jesse Noller wrote:
That's odd - I've been doing all of the mp work on osx 10.5.3 - I'll
run the units in a loop today to see if I can catch it.
-Jesse
Thanks. It's definitely reproducible on both my Leopard boxes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 11, 2008, at 2:03 PM, Raymond Hettinger wrote:
"Function names should be lowercase, with words separated by
underscores as necessary to improve readability." -- PEP 8
If I'm reading this correctly, then underscores are not required
ever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 8:29 AM, Facundo Batista wrote:
2008/6/12 Barry Warsaw <[EMAIL PROTECTED]>:
function:: active_count()
method:: Thread.get_name()
method:: Thread.is_alive()
method:: Thread.is_daemon()
method:: Thread.set_daemon(daemonic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 11:21 AM, [EMAIL PROTECTED] wrote:
Should it be...
2.n : .is_alive()
2.n+1 : .is_alive() (deprecated), .alive (recommended)
2.n+2 : .alive
Barry> Personally, I'd go with a property .is_alive
I'm not fond of using a prope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's unfortunate that I was not able to release the first betas on
Wednesday. The primary reason was that none of the 3.0 buildbots were
green.
My proposal is this: I will spin another release this coming
Wednesday, June 18. If we can get bo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 11:41 PM, Guido van Rossum wrote:
My colleague and SVN developer Ben Sussman-Collins occasionally blogs
about the social side of (mostly open source) software development. He
just posted a new one that struck a chord:
http://blo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 13, 2008, at 9:54 AM, Facundo Batista wrote:
2008/6/13 Barry Warsaw <[EMAIL PROTECTED]>:
My proposal is this: I will spin another release this coming
Wednesday, June
18. If we can get both the 2.6 and 3.0 buildbots green by then,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 15, 2008, at 1:43 AM, Raymond Hettinger wrote:
For an insertion order dictionary, there was also a question about
how to handle duplicate keys.
Given odict([(k1,v1), (k2,v2), (k1,v3)]), what should the
odict.items() return?
[(k1,v3), (k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A colleague just forward this to me and it blew my fscking mind to
smithereens. It also brings back a lot of memories. Enjoy!
- -Barry
http://www.vimeo.com/1093745
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFbK8XEjv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 17, 2008, at 3:44 PM, Amaury Forgeot d'Arc wrote:
I am in the process of merging changes from trunk to the py3k branch.
(If somebody else is already doing it, please tell me quickly!)
BTW, I will be hanging out on #python-dev @ freenode fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I'm going to try again tonight to release beta one for Python
2.6 and 3.0. I'm planning on starting the release at 6pm US/Eastern
or 2200 UTC.
Right now the Python 2.6 buildbots look pretty good. We have /one/
green buildbot for Python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are enough green buildbots and I think all the showstoppers are
resolvable, so I'm going ahead and releasing beta 1 tonight. Please
refrain from any commits unless I ask you to check something in.
We've got a major thunderstorm blowing th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 18, 2008, at 7:54 AM, Jesse Noller wrote:
Please let me know about 3088 - I've disabled the more unreliable
tests until I can give the entire suite some TLC. I'm still trying to
work around/identify the "Function not Implemented" error in iss
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFnIbnEjvBPtnXfVAQKCMgP+L9Vpk9vQgYw01KShtF9HyvCKE0guSy86
0Q/IRbkXGahXg910D4nVLY9NORaOSq/VP8Kx+fOU8egUDHvVF9MuKkY75ZHYoixR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2008, at 4:43 AM, Paul Moore wrote:
On 19/06/2008, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community,
I am
happy to announ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 21, 2008, at 5:45 PM, Leif Walsh wrote:
There is a typo on the download page (http://python.org/download/releases/3.0/
):
Fixed, thanks!
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSF2G5nEjvBPtnXfVAQJbqwQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 24, 2008, at 4:13 PM, Guido van Rossum wrote:
[Mark Dickinson]
I think there may also still be room for some additional discussion
on the output format;
[Martin v. Löwis]
If so, I think the change should be reverted, and the feature
defe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 26, 2008, at 10:40 AM, Nick Coghlan wrote:
Well, that and the beta deadline (we have to draw the line
somewhere, or we'll be stuck in an eternal spiral of "just one more
feature")
Guido wanted to get the beta out when we did exactly so w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 26, 2008, at 11:42 AM, Nick Coghlan wrote:
If the community buildbots aren't largely green by the time beta 2
comes out, that's when I'll agree we have a problem - they should
definitely be green by the time first release candidate comes o
lanket complaint that this is a disgrace. So why is it?
and already discussed:
http://mail.python.org/pipermail/python-dev/2008-April/078421.html
Following that trail of breadcrumbs, I ended up here:
http://bugs.python.org/issue2235
with a message from some guy named "Barry Warsaw"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 26, 2008, at 5:20 PM, Georg Brandl wrote:
Barry Warsaw schrieb:
I don't know if this "Barry" guy has the appropriate permissions
on the bugtracker to increase priorities, so I've taken the
liberty of upgrading it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 26, 2008, at 5:54 PM, Martin v. Löwis wrote:
I just added a "deferred blocker" priority -- that implements one
half
of your wish. Mass issue updating must be done by someone who knows
Roundup better than me, I'm afraid.
I doubt true mass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow, I bet this one crept up on you as quickly as it did me!
We have our second planned beta releases for 2.6 and 3.0 tomorrow. As
usual I will start looking at blockers and buildbots tomorrow
afternoon (UTC-4 time) with a plan to start building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:25 PM, Guido van Rossum wrote:
I think we should put this one off. The previous betas were done on
June 18, and IMO the next beta should be about a month afterwards,
not 2 weeks.
I will not be able to make releases the week
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL PROTECTED]>
wrote:
From: "Barry Warsaw" <[EMAIL PROTECTED]>
There are two options. I could shift everything for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 7:04 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 10:42 PM, Benjamin Peterson wrote:
On Tue, Jul 1, 2008 at 8:44 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
Is a Google Ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 14, 2008, at 6:43 PM, Neil Schemenauer wrote:
In case anyone is interested, I have git repositories for both the
trunk and the py3k branch of the Python source code. They are
up-to-date and so using them with git-svn would be much faster tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 15, 2008, at 6:41 AM, Paul Moore wrote:
On 15/07/2008, Barry Warsaw <[EMAIL PROTECTED]> wrote:
In case anyone is interested, I have git repositories for both the
trunk and the py3k branch of the Python source code. They are
up-to-da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A reminder: the second betas of Python 2.6 and 3.0 are schedule for
tomorrow. I will try to hang out on #python-dev today and will start
looking at the trackers and buildbots. Hopefully, we're on track to
get the releases out!
If there is an
1801 - 1900 of 2704 matches
Mail list logo
