y to Thomas Wouters who sprinted with me
yesterday on getting the whole infrastructure up and running. Thanks
also to Martin v. Loewis, Sean Reifschneider, and the folks here at
Pycon from the Bazaar project, Ian, Andrew, John, and Edwin.
Enjoy,
- -Barry
-BEGIN PGP SIGNATURE-
Versio
-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
ommit
bzr create thread thirdstuff
bzr commit
bzr down-thread secondstuff
# see what's different between secondstuff and firststuff
bzr diff -r thread:
rinse-and-repeat-ly y'rs,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR+Ufb3
> through URL editing, but not the form (currently). I'm not sure
> whether that would search for issues which are marked both 2.6
> and 3.0, or for issues that are either marked 2.6 *or* 3.0.
Thanks Martin, I think this will work for now. Is there any way you
can allow me to edit
to create a new one (or you
> create
> one yourself, anyway, and I remove mine later).
Naw, no need for the extra work. Thanks!
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR+UpvnEjvBPtnXfVAQLHDAP/WVC9IJpGbe0RgoG/5AkWki0
muscle memory so that by
the time 3.0 comes around, it'll will be a much smoother transition,
for me and other coders.
Now, if it's not feasible to add such a future import, that's one
thing. If it's feasible then I think we should do it.
- -Barry
-BEGIN
-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
&
eeing too much red.
>
> http://www.python.org/dev/buildbot/stable/
> http://www.python.org/dev/buildbot/all/
>
> See my other mail that discusses the stable buildbots. The criteria
> for release is that all the stable buildbots are passing all the
> tests. So we really gott
re separated onto their own page:
>>
>> http://www.python.org/dev/buildbot/stable/
>
> This is for trunk or 3k?
The page has stable buildbots for trunk, 2.5, and 3.0. I'm thinking
that we should remove the 2.5 buildbots from the stable page. Neal,
if you agree, can you do
k a month.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR+q/dXEjvBPtnXfVAQJYJAP9En+87NRtSOKcnEB4Om/BYE+Jw7KZ08JI
HY1MGAHleya8MHIgaEkaQf142pzfHKWxWZLNWD5UShHPlarwfvIxHdT07q5ozGda
l4J95FU2EaLMGxN+5HvxlY+pdXAiVcNAnO12TO1Gqahf9Mmk1eXkKM0p6vBPJHqZ
vtekrWIzeck=
=3v/o
---
-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. :)
- -Bar
uncleanliness. If you ever want to push a completely unrelated branch
overtop that one, just use --overwrite.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR+6+ZnEjvBPtnXfVAQIbdgP+KRv3Uhq9OQrhc6iRI1eEVR+1bbYbFSQs
bwvwSf9SXNaf/YfO5Bm61Yl
could, because bzr+ssh is more efficient.
- - -Barry
- -BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR+/04HEjvBPtnXfVAQI6gAQApMnG/h4qCoSx5rxd6US03DN01hh2ef2N
l7tNnQCJMAd2+By5z/cn/BY2vehZmVZEFhgNsGzhAOHZNbsbFG2kBdJkT5PLCOQN
ZGqdYCgbMbHhDLsPG0XfWorOgpeER/7WlesF/VXGbbGiZq
about the
stable buildbots. Please try to be very conservative in your commits
to the trunk and 3.0 over the next few days. Concentrate on fixing
existing code rather than committing new features. Your release
manager thanks you for your diligence! :)
Cheers,
- -Barry
-BEGIN PGP SIGN
Jabber if you need to
contact me.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR/QB6XEjvBPtnXfVAQLn8QQArynMsNeeb6gqjUCSYuupM2XXAbwP5XOX
LbTeGN+vM13uNK32fI47rDaPEfudfGnrd3Ttc1pg6/S/MOo5T41zs/TX2jdMEQ4g
6zCtk6xJiexGbExKioiTVdYgiqA8C6u
-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
n 3.0 web site:
http://www.python.org/download/releases/3.0/
We are planning one more alpha release of each version, followed by
two beta releases, with the final releases planned for August 2008.
See PEP 361 for release details:
http://www.python.org/dev/peps/pep-0361/
Enjoy,
- -
he 3.0 version:
> |
> | Top of the page still says "3.0a3".
>
> The tops of the pages are fixed, but the left sidebar DOWNLOAD/
> Releases
> list still says 6a1 and 0a3.
I think I fixed these -- at least a grep of my local tree turns up no
other references to 2.
-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/s
#x27;ing such dialogs all the
> time if they are at all used to downloading software from the
> internet.
MvL is leading this effort and is currently trying to get a code
signing certificate (my attempts having utterly failed on the Mac ;).
Please coordinate with him.
-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
it to critical for the next
alpha, but we'll review all the release blocker and critical issues
for the first 2.6 and 3.0 beta releases.
Cheers,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSBonfHEjvBPtnXfVAQLaSwP+IMjYbLryACRColvgTU4ezPHhbBpdDaRA
I2k15c
f).foo() as a shortcut. To me, that addresses the main
rationale of the PEP without the magic (i.e. no need to repeat the
class).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSBpWLHEjvBPtnXfVAQJmOAP+NW1tj67Ls+m6PCbF9wYpPRQhT2RJ1210
0QdYxyYz8
-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
TH as long as
my arm just so I can run a few applications without system-
installing them.
I hate to send a "me too" messages, but I have to say Glyph is exactly
right here.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSBr75XEj
fact that it's hidden helps keep them from
deleting it by accident
- for experienced users (Barry, skip, etc) that want ~/.local to be
more easily accessible, creating a visible ~/local symlink is an
utterly trivial exercise.
Hey Nick, I agree with everything above, except that I'd p
home directory,
but I guess that's the price we pay for a modrin desktopy operatin'
systum.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCBAXHEjvBPtnXfVAQJdrgP+Mw0qZebL+MqUk3wKMsRt5mHzT/uHhQ0Z
NVwyooWKWnvLMMifCbaG3pjVs7MehfcbAK8uLTlF8Ss9/w1Q5SWJ
Very awesome Christian! I'm psyched for this to get into the last
alpha releases, which I remind everyone happens tomorrow. Plan on svn
tree freeze at approximately 6pm EDT (2200 UTC).
Cheers,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCDe+nEjvBPtn
ing the release, but figure it will be at about 10pm EDT.
Please limit your commits between now and then to only things you
absolutely know will improve stability and test passing.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCI6MXEjvBPtnXfVAQIf
please refrain from committing anything.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCKDMXEjvBPtnXfVAQL1CgP9Heg1XlNjpM3wgT4N8PK090HnaGIJ6MzH
Fs3QtngvLB/YPf31VrkYILIIMG/YBs+yqCZFziuSR2alNYNBcvwNVfpIljMuq9AM
qtj+cu2vbhkoh+gR8LjM1J8ZWAKhI5G6eAxHuGlTWykd
lphas, sorry.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCKDRnEjvBPtnXfVAQKjGAP8CFKRDMBYJC8dm+tR/nHucrRa/Nqfy977
I8rx/B5QWN+feBk6LhODaEQ2NPOQaF+iSTaDnOlF9f2+Z6m85b94zsLJPY9EoiAC
qdNmYBmZWYtuzvLmCh5Ef2aCjtfbn4Ik8i3SR9amQJBhuq7ubbdYVUsbcy6HCUUV
K2Xp8LV1HWM=
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 enforce commit freezes for the betas though.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG
-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
-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
Comments? :)
Christian, you get this week's Awesome Award.
:)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCQ/HnEjvBPtnXfVAQK7QgQAumf3wL8nQeH6CVC4hlaqjNQ330KSaVfj
/o2bKusu77R+MYyYq/OV5k3q2/eo1XyPUDlE4+JXldvnhmjmx33zTv+5MDZLIWbN
PPTfmYosHcXMh4CG6iqFqZxCoobhGU
UNK FREEZE] ".
I will make the freeze announcement more recognizable in the future,
but I also want to point out that the entire release schedule has been
published far in advance in PEP 361. At this point, the freeze dates
should come as no surprise.
- -Barry
-BEGIN PGP SIGNATU
-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
se, there may
be a longer freeze. Even in that case, I don't envision more than a
24 hour freeze hopefully.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBSCRR5HEjvBPtnXfVAQLa+gP8CL9koa5eGBvP8g+CA8l61SIuluHNbPkq
SH7uOiPMeuIX392xy82ixnXjYTlCJn9epWouYki
-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
procedure that
avoids this problem completely.
bzr to the rescue .
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSChX5nEjvBPtnXfVAQK2NwQAgA3Gaa7Ew6uAVrqJe3B9wj/lseMuS88j
y4/gtlCcb35Vtff9CpEveCD44IelaB+OFH2iG6TKXxxD47HhYfJD3STRWnphimb8
j4UXJyfJTlMIW7ISWGzv62c+RlyXle
what python does.":
'I am a string.'
'I am a string.'
"I'm a string"
"I'm a string"
Nice. :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSCi2mnEjvBPtnXfVAQJWHAP/b/2Yebt7abj+UuysjYFgzetl+26SFSF
hecking the keys for everyone who has shell
access on the python.org machines.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSCpCXHEjvBPtnXfVAQLy5gP+MZJ7/RKDqw9QKvNr9rlGm7GjOBkuWR3B
UA91clzb4Iuy+51+V4B3iUcdmwGtpfYum8/2+1/qpi7a
ut we recruit additional moderators? Any volunteers?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSD9fl3EjvBPtnXfVAQK+cQP/Xwx5+k9gzBcDLG4QQGvAdMSXTfXjayxL
OxDnWWzDNm+CfzDoY76GHhTPk/Jc3Rx80aTxBmv2DyElq+Z5r0TrqbYp25EFV4Ia
J0P4q2WGkBq71LFYuTrmcYp7Z2oF47M/vm3F1zp
is time to stabilize all APIs and features, both in
Python and C. Next week, I'll do a gut check on critical and release
blocker bugs, so please also take a look at those and try to fix what
you can.
Cheers,
- -Barry
-BEGIN PGP SIGNATURE-
Vers
63887-r63898 are missing from the archive, too.
We should probably make an effort to review those checkins.
mail.python.org had problems yesterday, so if the mail client doesn't
resend, it's very possible that messages got lost. Everything is back
to normal now.
- -Barry
-BEGI
:
test test_asyncore failed -- Traceback (most recent call last):
File "/tmp/python-test/local/lib/python2.6/test/test_asyncore.py",
line 387, in test_recv
self.assertEqual(w.fd, fd)
AssertionError: 6 != 3
Looks like a minor oversight.
This needs to be fixed or backed out if we
he beta. That's the kind of
thing that can (but still, must) be fixed up before the final release.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSE8M5XEjvBPtnXfVAQIBcQP/S5BMgNS/sOXajnU7eLfXGM39/PwStL8b
HOv/MZiHtjmRx5Rtro7lDnjaf9u4Ae+V90a5Pt+
up before
then, I'll email the list. If you think we really aren't ready for
beta, then I would still like to get a release out today. In that
case, we'll call it alpha and delay the betas.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAw
basically looking for a yea or nay from Barry or
Guido. I think it's the best answer we're going to find to the
problem of how to write type-agnostic delegation classes in a Python
world without classic classes.
I've updated the issue with my own opinion. Let's see w
643841
It's a long bug thread, but needs a decision.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSE+/4nEjvBPtnXfVAQJDzQP9FtWLT3+MIBoeRLRqFtXEZxphi+IDU7wp
Jtw82cFgKz/wPPxyyGEtnLSmt6duj3MTTftuVsTKS1plqsd6puC2S1VbEOvS9otp
xQ0E1mn/xb4B/BvH9n3xkS9FTiYle
-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
decision:
http://bugs.python.org/issue2997
Guido's approved the patch. Please go ahead and apply it. If no one
gets to it before tonight, I'll put it in beta 1 if it applies cleanly.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFARanEjvBPtn
-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).
I'll be on #python-dev @ freenode.
Thanks to Benjamin and Alexandre for helping me get through the
current crop of release critical issues today.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFBOHXEjvBPtnXfVAQK6zQP+Nnjt6Q97heAuquZgKEfMxX
-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:
ain. This weekend might be a good time for me.
Please help out by resolving these two issues.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFCtZHEjvBPtnXfVAQLrHQQAoq1RCNeawpJHaefuvmZiS4VZzzvtV5Bm
HFW6FWyO86NNEcCK6Delthf+H1mgjCaoymHojxBJhWm7UJK0WjMz+0
forwarded this
off to the python.org sysadmins.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFEJenEjvBPtnXfVAQL1DwP/cpAACpa7KTL8BZcuQGcqgmbez1PmtXBG
jl85PaULlm6LAvTjtZMy/n2ribZ7TTGLRAHkEoGiQyN03xHFn+w8v6
oth my Leopard boxes. I
haven't tried it on my Tiger box. The buildbots seem unhappy too.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFEJ9HEjvBPtnXfVAQJlNwQAsG2M/hNORYSuCsmKHU+nvbX3cASiFlhj
IIhNfdrtkRbjXBaDgxrr/Ps1+Q3I56lpSg5SDEWxXVufNdBdHXGAKKxnrYN22a
other me too much. For the others you
mention, well I'll invoke ZoP 12 and 13.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
- -Barry
-BEGIN
-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 fo
eases stable by then, Wednesday's release
will be alpha and I will make the July 2 release the first beta,
updating and pushing back the PEP 361 schedule accordingly.
Thanks for all your help in getting 3.0 stable!
- -Barry
-BEGIN PGP SIGNATURE-
Version:
adopt these guidelines. An open
source volunteer project is different than a corporate environment,
even if the latter is very open-source-y. But it is worthwhile to
continually evaluate and improve the process because over time, you
definitely improve efficiency in ways that are happily adopted
-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,
package on the
cheeseshop gain overwhelming popularity, practically forcing us to
include it in the stdlib.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFUEpHEjvBPtnXfVAQIj9QQAtuvlC5YtcSBsddztqD8kwokSrvKz7Nef
oM0JpxjVBQ7oT0F9MnWEvu9Rf8aTVdXsR/zWTf0yw1jt4HtM5
-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
enode from now until
tomorrow night, so if you have questions feel free to ping me. My
userid is 'barry' (so creative ) and I keep generally UTC-0400
time.
The changes I will skip are (for the moment):
- r64114 (gregory.p.smith): a bunch of checks for integer overflows,
contri
heck locally on 3088 over the day.
If you're looking for a way to help out, see if you can turn any of
the other 3.0 buildbots green. I will be hanging out on #python-dev
all day, but ping my nick (barry) if you need my attention.
Thanks, and let's get it done today!
- -Barry
--
-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
t seem to be
skipping/the device exists.
We're going to have to deal with 3088 after the beta release. I'm not
going to let it hold us up this time. I think we're going to have a
tougher time than we think getting the 3.0 release stabilized for
final though.
- -Barry
and downloadable distributions, see the Python
2.6 website:
http://www.python.org/download/releases/2.6/
and the Python 3.0 web site:
http://www.python.org/download/releases/3.0/
See PEP 361 for release schedule details:
http://www.python.org/dev/peps/pep-0361/
Enjoy,
- -Barry
-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
don't want the fact that it was committed
to force our hand. Raymond, if you care about this feature, please
roll it back so we can have a proper discussion without pressure.
FWIW, I concur.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSGFrlnEjvBPtnXfVAQIT
did exactly so we could draw
this line in the sand. I'd much rather people be spending time
getting what features we do have tested, stabilized, bug fixed, and
turning the buildbots green across the board.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwU
ubmit a bug report to the Python
tracker.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSGQEu3EjvBPtnXfVAQIp6QP/bOU+8vImlRkfKCXazYhi3yEXcNwCPpWI
e3AoiOlgKbOhSPraNTyUBjC+OjuqHQttyMJz8TTpexSwhpG/erDIqUjRbkW0Yaas
attvFZBYbJhF3qvHyLzmSp9U3oXY6VyWayL8ZdzIGcukEW7g8DgQNQyoGO
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
The idea being that after each
release, we always bump deferred blockers back to release blocker.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSGQZbHEjvBPtnXfVAQIwWQQAqWoIoqV0S0O8ZpkXpWd3LO4Fo7MBfjRT
LL5QgIPBWdQdZ4RR68LSfdAhiHGnZCZorpNksGaeIxP55qgS1z31fy3JF39
f you know of things that absolutely must go into beta2,
be sure there is an open release-blocker bug on the issue.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSGqQpnEjvBPtnXfVAQLdagP/VooK8+AoPrb1bR7xAxGqg0vC1HOKw5qZ
8VQArzgldz1OnoG24PuKGdaEw7PbHjCMk
weeks of July 21st and 28th.
The next scheduled beta is August 6th.
There are two options. I could shift everything forward 2 weeks and
do the next betas on July 16th. Or we could wait until August 6th.
That would mean 6 weeks between betas. It's fine with me either way.
- -
-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
than
starting from scratch.
If anyone is interested, I will find a place to host them. They are
each about 150 MB in size.
Neil, we should try to host them on code.python.org.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSHv+A3EjvBPtnXfVAQI0zwP9H0lZMvWxwncqg1BmI
-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
re is anything you need a decision on, please follow up to this
thread. I'm inundated with email so I can't watch every thread on the
mailing lists. Or ping me on #python-dev.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSHyY5XEj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I realized that the previous schedule really called for a release
today 7/15 because I'm a bit busy tomorrow night. In any event, let's
try to stick to doing it on 7/16.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 15, 2008, at 2:38 PM, Brett Cannon wrote:
On Tue, Jul 15, 2008 at 5:32 AM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A reminder: the second betas of Python 2.6 and 3.0 are schedule for
to
much time left
to fix things like this.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSH0/MXEjvBPtnXfVAQJoHwP8CFYbafuSTbnVdBBydZJ5k8Fb1L4YYVG/
0ee81N4AiQZ5uGQlk4ywAVBycPa+DMWE+cdrkYiGXkPaarhcOd55dfdvL1Ww6OgO
tor2fh2IxT0ee7gO/vgbyv4ybWsxuPH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 15, 2008, at 8:32 AM, Barry Warsaw wrote:
If there is anything you need a decision on, please follow up to
this thread. I'm inundated with email so I can't watch every thread
on the mailing lists. Or ping me on #python-dev.
ckers. Chat
with me on #python-dev if you think we should release anyway. I will
try to look into 3375, but I'd like to know if anybody else is seeing
these build failures.
I'll note that I plan to hold the beta3 releases until all release
blocker and deferred blockers are r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 17, 2008, at 09:57 AM, Steve Holden wrote:
>Barry Warsaw wrote:
>[...]
>>
>> I'll note that I plan to hold the beta3 releases until all release
>> blocker and deferred blockers are resolved.
>>
>Ian
1901 - 2000 of 2826 matches
Mail list logo
