-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please, no checkins on the 3.0 or 2.6 branches until further notice.
We're a go with the releases tonight. Email is not the quickest way
to get my attention. For that, use irc on freenode, #python-dev.
- -Barry
-BEGIN PGP SIGN
remove it from 2.6, but we can certainly start
end-of-lifing it in 2.6.
+1, but please, after I make tonight's releases. :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSIAFenEjvBPtnXfVAQKEewP+OWCBAH437X4+EptdcuIFFYrCCVXqbrV4
F2dZMyv/RU0jYgd6YTLspklEIzuE
/releases/3.0/
See PEP 361 for release schedule 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.9 (Darwin
we can to stabilize these releases,
address the blockers, and turn those buildbots green.
Thanks everyone.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSIATAHEjvBPtnXfVAQIWLAP+OVUXh3H5j8WN4cm3fHcLkgd+E4FuWWwb
zKr7JPYUHhgvwpYB5iZjQuJe/62qKXh70wNWyDcxLi9/TEbx8NvhQ+nM
stuck with it for
the remaining 2.x, at least we can stop the buildbots from going red
for bugs that we can't debug and probably won't fix.
+1
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSIDsxXEjvBPtnXfVAQJ6egP+O0HQPj9X7te1X3CbPBRN8RhadJucaD
his is the correct place to report this.
It is, thanks. Looks like I forgot to svn add those files. Please
try again now.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSIK9KHEjvBPtnXfVAQLBdwQAok5D6yqAkfOEHjvq5YEVuOwnLLWz1UbV
Y/bH6Q7lxnh4aIKJn2Mty82fLM
I think you mean july.
Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
See http://code.google.com/p/python-incompatibility/source/checkout
Barry
On Jul 19, 2008, at 03:25, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
| On Sun, May 25, 2008 at 6:25 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
|> Since I need to po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 20, 2008, at 3:44 AM, Barry Scott wrote:
I think you mean july.
Thanks, I'll fix that.
- -B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSIMuQXEjvBPtnXfVAQLFVwP/SYQkNNHnReOOuPxnnJQkNqKTnDYLpZqT
t need fixing up going from beta to beta to rc.
Oh and I'm not going to try and make a version of PyCXX that works
on 2.x and 3.x as the changes are too fundamental.
Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailma
I cannot see how I implement decode() for bytes objects using the C API
for PyCXX library,
I'd assuming that I should find a PyBytes_Decode function but cannot
find it
in beta 2.
What is the preferred way to do this?
Barry
___
Python-Dev ma
On Aug 1, 2008, at 14:30, M.-A. Lemburg wrote:
On 2008-08-01 15:06, Barry Scott wrote:
I cannot see how I implement decode() for bytes objects using the
C API
for PyCXX library,
I'd assuming that I should find a PyBytes_Decode function but
cannot find it
in beta 2.
What is the pref
lease
blocker", "critical"
or "high priority" ones (there are quite a lot of them :-)).
Just to add: there's also a 'deferred blocker' state, but right now
there are no issues with that priority.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.
uot;)
return
def I_do_not_like_this():
s = '''a multi line
that break the indent of the function"
return
Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
code review
at this point since we only have one beta left. Barry can correct me
if I am wrong, but dropping a major rewrite of bsddb into 3.0 between
b3 and rc1 is not acceptable. I wouldn't be surprised if all code
after b3 requires a code review since at that point we should just be
squashing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 11, 2008, at 5:51 AM, Antoine Pitrou wrote:
Barry Warsaw python.org> writes:
I agree. Our last beta is scheduled for this wednesday
Are you sure?
According to http://mail.python.org/pipermail/python-3000/2008-July/014269.html
,
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 11, 2008, at 8:27 AM, Barry Warsaw wrote:
Ah darn, that's a typo in the PEP. I definitely meant August 13, as
the Google calendar shows.
Do we think we can be ready for beta3 this Wednesday? If not, I'd
rather stick to
hon-ideas
either, but I'd be willing to start a testing SIG on python.org if
others are interested in getting together for this purpose. The goal
should be to produce something like a unittest-ng, distribute it via
the Cheeseshop, and gather consensus around it for possible inclus
propriate there.
Ah, thanks for the pointer. If there's a good existing list that
people want to keep, let's just raise its profile and point people
there. I'm happy to create a SIG though if that's what people want.
/me-subscribes-now-ly y'rs,
- -Barry
-BEGIN
might be a good place to continue this discussion, at least
until/if unittest-ng is created.
Thanks Titus. I'm subscribing to that list now, but I fear the
bikeshed. :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKGrOHEjvBPtn
ill never get released.
There's a difference between never being released, and unavailable in
the source repository.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKNiEXEjvBPtnXfVAQIQgAP6A84mpv0JUkP4Z904TzoYDuqb3OtCNBMc
wo+VGw00p9JJ0f4lWRmXSkim
esn't get done.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKNjW3EjvBPtnXfVAQLCLwP/QEFeXZstWcEuLbicMuqipREQsruTJW9v
SJURMYCZBdfkgiTm3cr2MVK9e/FpX7FUvhCKlAOpyAFOWM3FFiv/J+wBRNHcli2p
NHYbG8scmUHwVZ1oL1pWr7NLgECh0DsXBTWWubRyR3XqG1bdnk+B0wKuzcxNOH5Y
McLahXhN
for closing 2.6 and 3.0 now, and add
them to PEP 361.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKOvzXEjvBPtnXfVAQImrAP+IZHk711jPL8GdfrFiENt0KgGD5vjjg/g
kxgBsyVWi/wOonM0cFUABzSxBzfCOPd1eWtD54bs4rk32sXA+v3qtoHKylPsv/0O
8WUq4dXZ3LLn7D50WKWrJNIKTlAaxoH+OWCKK+qga
py to arrange things with a Mac expert to put the Mac
binaries on the download site.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKmpOHEjvBPtnXfVAQJNFAQAiQu+ZgeHoi7fzF7NWwqDoP4AAH8UNF5B
6JL74CmJnarhZ40dum3RUz+bEM3Htfik+baMUInCEz+hlOBBbZi9qTyVxTdA9z
, but like Fred, I don't
use it.
I do agree that we could and probably should maintain any Mac Python
content on the main python.org site, but also if Bob wants to donate
the domain, we can just have it forward to www.python.org/allyourmacsarebelongtous
- -Barry
l, but I think it's fine to do what you are proposing.
I think it's fine to commit this. I would put a DeprecationWarning in 3.0 and
a PendingDeprecationWarning in 2.6 (updated to a DW in 2.7).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIqja42YZpQepb
ident this will get fixed before
beta 3.
As for the buildbots, they're not looking so good. It looks like the trunk
has various failures in multiprocessing (hopefully fixed soon) and bsddb3.
Also some crashes in test_anydbm. Hmm.
3.0 is looking better but there's a weird error in tes
, I'm generally available from about 7am to
about 7pm US Eastern (UTC -0400) time.
Cheers,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKrEGHEjvBPtnXfVAQKCZAP+JyldH4bq1MO/0s5cJYDIM1hKNuXTm488
Ys/scWaPb7zBGi5/+Wdbwmle82EAsl3SDH6yDzjzhvgHOkOdsvaCP2bbVaX
t that's what bug
reports are for :).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKrMhXEjvBPtnXfVAQKprwQAsuckU4jw5B+asnd6XNqCjuOuIDYRuv3w
sOlfn76qwoxaA9KJe7aCBOcoXpUnB4ibEm8O403LYV9izRXf62xgGdyVWTS73yEc
Sj6maoeIIO9ph7/p7eWT0Hl3pVmphsiLRgd7usyDSeRf+8ncXmE8Clr7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 19, 2008, at 9:02 AM, Benjamin Peterson wrote:
On Mon, Aug 18, 2008 at 10:29 PM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
1878class attribute cache failure (regression)
- - Medium priority
- - Guido, there are some design choice
Python environment isn't just right.
I think it's a /good/ thing that some OS distros are heavily invested
in Python for their core operation. We just need to understand the
best practices when they are.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Dar
rt that had a
different default.
I will get to this when I can, although I am sure Barry won't be too
upset if this misses b3.
Nope.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKsZd3EjvBPtnXfVAQLGRAQAhVwJLkwi/+ZlW7x53sKyyMEf+pJj7UTK
l0MjS/J
ython-dev if you need an immediate
decision.
Thanks.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKyecnEjvBPtnXfVAQJ4DgQAg7hNzp76nUT8/dA4C2xTqwL+mmtXeu2s
MLbez1xVk3IoU3J/GRRcposaUQKoPToophndj1yk57v/g/AtrXIAjFRXkqH7giU5
eD7Wlt
.6 Windows buildbots looking green after the beta. These will
definitely block the release candidates.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIrLXw2YZpQepbvXERAkn7AJwNNoq+ApgeP/j8TyPL4x71SPju5QCePzdw
KC5QXa1Tk72OSTmQIelU2hs=
=zYog
-END PGP
:
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
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on
1 test in the bsddb3 tests.
Thanks Mark. If we can't get bsddb3 running cleanly, we'll have to
add an item to the release notes about it.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSK1fgHEjvBPtnXfVAQLu2wP8D5dBf6wAeGgOgK
far.
Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
bag over
our heads. Slipping to get yet one more feature in is not (IMO)
acceptable.
An incentive for keeping the schedule: If we hit our October 1st
deadline, then 2.6 and 3.0 will almost certainly be included in some
upcoming major new OS releases. If we slip, then it's unlikel
rguments that allow it
to "just work" on both Windows and non-Windows systems.
Unless I'm misremembering (I no longer have access to Windows), I
believe that if you use ' '.join(cmd) as the first argument, it will
work cross-platform.
- -Barry
-BEGIN PGP SIGNATUR
'd vote no for 2.6/3.0.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSLLtMnEjvBPtnXfVAQKg0wP+LJ1XYXhEQHUAvT3fPbPzStCN8Lb+D7XG
hZOANnTCbPGaeCY19B8mYZbXkvjkCBptauKGB5yGOAnb1KCkSaQWx0wCInkeyIFE
mVMupGZCUsdsO7KreEwvyhBpOJ/HNY0+eacv8GZKCwC9xW3WmhaOjry7sZFhjffw
hAX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 25, 2008, at 1:33 PM, Oleg Broytmann wrote:
On Mon, Aug 25, 2008 at 01:30:58PM -0400, Barry Warsaw wrote:
Unless I'm misremembering (I no longer have access to Windows), I
believe that if you use ' '.join(cmd) as the first ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 25, 2008, at 1:53 PM, Fredrik Lundh wrote:
Barry Warsaw wrote:
I agree. This seriously feels like new, potentially high risk code
to be adding this late in the game. The BDFL can always override,
but unless someone is really
o the Unicode database:
http://www.unicode.org/Public/UNIDATA/UCD.html
The main file used for the unicodedata module is called
"UnicodeData.txt".
That's much less scary.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSLMDCHEjv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 25, 2008, at 3:17 PM, Fredrik Lundh wrote:
Barry Warsaw wrote:
You don't mean the experts claimed they weren't important, right?
Unimportant changes definitely don't need to go in now .
Well, at least Guido managed to fi
org/hg/
Cool! It's nice to have these become "official". My hg branches are
all pointing to your site. Can I easily relocate the parent branch?
Actually, right now anything that's not Subversion is still
experimental. But agreed that it's nice Mercurial and Bazaar are
av
t Thomas and Martin (who are both also probably pretty
swamped) probably know how we did it.
If not before, we should spend time after the releases in making this
available.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSLSS03EjvBPtnXf
ealth of the trees. I
don't think the current list needs to be set in stone, and in fact
several of the "stable" bots have had simple svn or other non-tree
related problems for a while.
As for the "unstable" ones, I personally rarely check them.
- -B
a Windows installer build, I'd suggest to postpone the
RC1 release that's planned for tomorrow to get more feedback for the
Windows builds.
I'd rather still release the rc tomorrow.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 2, 2008, at 5:58 PM, Benjamin Peterson wrote:
On Tue, Sep 2, 2008 at 7:24 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 2, 2008, at 8:09 AM, M.-A. Lemburg wrote:
I suppose this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 3, 2008, at 7:01 PM, Jesus Cea wrote:
Barry Warsaw wrote:
and I know Brett agrees, so that's it. On IRC, I've just asked
Benjamin
to do the honors for 3.0 and Brett will add the deprecations for 2.6.
I just committed the fix
ppreciate any feedback or fixes you can provide on these issues.
You might also want to look at the deferred blockers to see if there's
anything that really should be blocking rc1.
I'd like to try again on Friday and stick to rc2 on the 17th.
- -Barry
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 12:14 AM, Raymond Hettinger wrote:
[Barry]
I'm not going to release rc1 tonight.
Can I go ahead with some bug fixes and doc improvements
or should I wait until after Friday?
Doc fixes are fine. Please have bug fix pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 3:28 AM, Mark Hammond wrote:
Barry writes:
In addition, Mark reported in IRC that there are some regressions in
the logging module.
3772 logging module fails with non-ascii data
Which according to the IRC discussion doesn&#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 7:08 AM, [EMAIL PROTECTED] wrote:
Barry> In addition, Mark reported in IRC that there are some
regressions
Barry> in the logging module.
Vinay apparently checked in some changes to the logging module with no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 7:31 AM, Facundo Batista wrote:
(I'll be hanging around in #python-dev today and tomorrow, btw, ping
me if I can help you)
Me too, though I'm a bit busy at work. Ping my nick 'barry' if you
need a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 9:45 AM, [EMAIL PROTECTED] wrote:
Barry> Or did he commit Mark's patch from bug 3772? If so, that
would
Barry> count as a reviewed patch.
The checkin message says issue 3726:
Author: vinay.sajip
Da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 7, 2008, at 10:51 AM, Fredrik Lundh wrote:
Barry Warsaw wrote:
I'm not going to release rc1 tonight. There are too many open
release blockers that I don't want to defer, and I'd like the
buildbots to churn through the b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 7, 2008, at 4:12 PM, Fredrik Lundh wrote:
Barry Warsaw wrote:
(I have a few minor ET fixes, and possibly a Unicode 5.1 patch,
but have had absolutely no time to spend on that. is the window
still open?)
There are 8 open release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 8, 2008, at 7:37 AM, A.M. Kuchling wrote:
On Sun, Sep 07, 2008 at 12:02:06PM -0400, Barry Warsaw wrote:
There are 8 open release blockers, a few of which have patches that
need
review. So I think we are still not ready to release rc1
ll of these problems in the next day or two.
I propose that we push the entire schedule back two weeks. This means
that the planned rc2 on 17-September becomes our rc1. The planned
final release for 01-October becomes our rc2, and we release the
finals on 15-October.
- -Barry
ceptable. Or at least name it something that doesn't scream "use
me in a way I don't intend!".
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSMZrfHEjvBPtnXfVAQI6DgP8DyNKZyR846u1Qpgbr4X3wOM1J6EcqSlW
74WGUoU80MDWH5wvagAl7Er90oEh0QhX4ogX8UgF8iLSOC7
ehind
If we can close them by Wednesday or Thursday, and the 2.6 bots stay
green, I will cut the 2.6rc1 release this week and the 2.6rc2 and
final on schedule.
If you're on board with this, please do what you can to resolve these
open issues. As always, I'm on irc if you need to disc
's far
enough along, though not as the primary Python version. They clearly
want 2.6 for that.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSMZ4cXEjvBPtnXfVAQL4ygP/fLILvf3NhvmN3R2T7htGm08xt/bOBYGt
+BDrV4rapS4j3jo2Cx+McEdjJZCdq9x7BIaTN+4ITwq02LEY5fmh
for possible integration into the core for 3.1.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSMZ40XEjvBPtnXfVAQK2WQP/e3N2rYD2rbsoynEnXvAjzF8lPoPRFDvl
hbjERsbB93uSoBPHaTdjtXnW+InC0W4GC5ogHF9wARbzYTJaxx09WmjihX+PvgsW
JhXwLpG3gtyclfqSAF8MWZHc4UnKnyUt5UgYBlZ
es. The latter seems like the wisest choice to meet our goals.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSMZ5L3EjvBPtnXfVAQJwSQP/U7FFFI8ao5Xesf6F3QFIUMYFeISrlhof
9ynkQXAskUMelAfayGMSd2nD2+buXA7gyBWplAAEF2rtLhZ3N0+zeh/2HnqcY0b9
EtUM5shAIMlb2948IMoXlxSMplH5auBHM
Sep 2.6rc2, 3.0rc1
Wed 01-Oct 2.6 final, 3.0rc2
Wed 15-Oct 3.0 final
I've updated the Python Release Schedule gcal and will update the PEP
momentarily. We'll close the tree later tonight (UTC-4).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSMp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 12, 2008, at 9:19 AM, Edward K. Ream wrote:
On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
We had a lot of discussion recently about changing the release
schedule and
splitting Python 2.6 and 3.0. The
://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.9 (Darwin)
iQCVAwUBSMsXV3EjvBPtnXfVAQJFsgP9GxZYQocbDTd0Z/0yEjpHfZ/FTd8y83jV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 17, 2008, at 5:59 AM, Jesus Cea wrote:
Barry Warsaw wrote:
On behalf of the Python development team and the Python community,
I am
happy to announce the first release candidate for Python 2.6.
In http://www.python.org/download/releases
/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
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python
xpert . Please let me know if you can help.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSNOLBnEjvBPtnXfVAQIQnAQAm6thEThGufep6hzHxBwAN8MTsLb9jxsu
Z8GAtX1bdMNOrJczYpU6by0oXPLR2pupnGV1YrAyQyoqpk+K7W8by5Qtg8+ZZcYH
GerkqMVtNYn2zY1HhKigivp2JvlqIidRc5D36XS2EJixhZEPc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 21, 2008, at 6:03 AM, Georg Brandl wrote:
Barry Warsaw schrieb:
Martin points out that in the past, as part of the release process,
we've built separate downloadable documentation.
Do we still want to do that for Python 2.6 and 3.0, a
dbots, I think it's fine.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSNlSHXEjvBPtnXfVAQKQ3gP/XJr97CdjZitwSQxrL28xCuLyPfKmtBVA
2hK2ewQxH9Rxrl0BsFZlnBz2vEygPmPWnduu8VT+sjsrFu/Ua9d1Xo06lQ6/fFck
Tp/en0KlAyJ6Pjf/1pWahn4ttwk74YG02LiQgUsfOaIUG+8cMfGfrtyUzwGBoKhW
4
.1 release without causing any major
harm is definitely out - and while a 2x speedup is very nice, it isn't
something to be squeezing in post-rc1.
Still, that should make for a nice incremental improvement when 2.6.1
rolls around.
I concur.
- -Barry
-BEGIN PGP SIGNATURE-
Versio
it flakey until Wednesday, but I
will do my best to get online and follow up as needed.
Please pitch in to help get Python 2.6 released on time!
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSN1hJnEjvBPtnXfVAQIQfQQAgYr0tuzJhm3LZX/1S
ay, just to see
how building the docs and such go. I'm still planning on doing the
final final release at about 2200UTC. If you need to coordinate with
me (e.g. press releases, Windows builds, etc.) please meeting me on
#python-dev on irc.freenode.net.
- -Barry
-BEGIN PGP S
;re willing to actually get stuff done :). Clearly the
current team is too swamped to act effectively, myself included.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOOe3XEjvBPtnXfVAQJ5JgP/dDg+SPLeQ4yBQ/CYxJEh3/Xm2B+2KV5U
9RUjp7W7z2iC/Bz7qwJlui0Z
ad/releases/2.6/
(Please note that due to quirks in the earth's time zones, the Windows
installers will be available shortly.)
Bugs can be reported in the Python bug tracker:
http://bugs.python.org
Enjoy,
- -Barry
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on
d now.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOS6g3EjvBPtnXfVAQKw5wP+I2L6qPZWp1qDs7qSRdlOE5xSAazhnuzE
h7gCUWah0tcewuJC38cE7kNAVkpmp9suBbGgI+FRYTeJJpoO109Io4cF4fRvYd2H
NpVfhIOo6VUchNTnsdtP4UzuaIKnkCKgWxMPPjMW9jEZlHPNdOC8stTsxOq1FWFt
hlJscML5yQA=
=wPLO
-EN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 11:46 PM, Barry Warsaw wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 2.6 final. This is the
production-ready version of the latest in the Python 2
with four active trees, we're going
to a pretty big challenge on our hands. How do other large open
source projects handle similar situations?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOajHXEjvBPtnXfVAQJ5qgP+I6k+kHMG2z
along well. I'm planning to spend some
time next time around on updating large parts of the web site
automatically. Or maybe Benjamin will when he's RM :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOei8XEjvBPtnXfVAQLm+wQAgctR3FuylGaST4Y55JIpo8
ions on what to check please.
I've assumed that if my objects support tp_hash and tp_compare
they can be used as keys to a dictionary. My test scripts shows
hash() and cmp() working.
Why does "key in wc_status_kind_wc" work when I use an object returned
by keys() by not w
need two more betas?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOqxvnEjvBPtnXfVAQIR5QP/coSi2ltsZSpE2dyUg7Y35QcSk/+4ZbGK
zF0AgLaOkGs+DFnxRH9vy9kN3JaEkp1MhEpDjkomE7kNpnJB7bWotTrHI67HD9ma
ZDqqmaCc02IeUtLm7HuELvofjCgh+gryKWvRc71ErRHmn/YxMGr1OcEirPpx4nZ9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 6, 2008, at 9:48 PM, Raymond Hettinger wrote:
[Barry Warsaw]
So, we need to come up with a new release schedule for Python 3.0.
My suggestion:
15-Oct-2008 3.0 beta 4
05-Nov-2008 3.0 rc 2
19-Nov-2008 3.0 rc 3
03-Dec-2008 3.0 final
Given
On Oct 5, 2008, at 22:49, Terry Reedy wrote:
Barry Scott wrote:
for key in [pysvn.wc_status_kind.added,
pysvn.wc_status_kind.replaced,
pysvn.wc_status_kind.unversioned]:
print( '2 key', key, key in wc_status_kind_map, cmp( key,
pysvn.wc_status_kind.u
thing I can think
of. (Hence Martin's question, I presume). I have no idea,
however, how porting could make that happen.
I see no reply from Martin. What was his question?
Barry
___
Python-Dev mailing list
Python-Dev@python.org
p() eq but have different PyObect * values.
This is a change from V2 python where to be a key implementing
tp_hash and tp_compare is sufficient.
In V3 is it your intention that to be a key you must implement
tp_hash and tp_richcompare? If not I'll raise a bug against
3.0 on thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 7, 2008, at 4:28 PM, Guido van Rossum wrote:
On Mon, Oct 6, 2008 at 5:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
So, we need to come up with a new release schedule for Python 3.0.
My
suggestion:
15-Oct-2008 3.0 beta 4
05-No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 7, 2008, at 5:47 PM, Nick Coghlan wrote:
Barry Warsaw wrote:
On Oct 6, 2008, at 9:48 PM, Raymond Hettinger wrote:
[Barry Warsaw]
So, we need to come up with a new release schedule for Python 3.0.
My suggestion:
15-Oct-2008 3.0 beta 4
05
3 and rc4 are planned "if needed".
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOvfg3EjvBPtnXfVAQKDfwP/Sz9Ioe1tIrKtvD7JPG2cg2F+wfDJrc+9
vqfh6/eMWiUIOeSKJu6+gye7oXRcHwQXAPivNza3993HesOu0TjudnwXfkAlfsdE
m09Rh70AXQQiY7JX46etugRC4BwkuNeBo253cvmfo6hPK0ZhO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 7, 2008, at 6:01 PM, Barry Warsaw wrote:
I won't be able to cut another release between the 15th and 5th, so
at least that one should be 2 weeks. If we don't need the
additional rc, then we can release early, which would p
ichcompare.
I've added support already in PyCXX. I'll now implement
tp_richcompare for pysvn and document this in my PyCXX
porting guide.
Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-de
and I'm hopeful we
can still meet that date.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkIL0wACgkQ2YZpQepbvXHxOQCdFUA4Q3frOjG2GX1ME0hc6uoZ
niwAn3deTj4E9KO+K4dMHWlKhKbjbaga
=0Py5
-END PGP SIGNATURE-
__
nterrested by my patches. Sometimes I just get a good reaction
>like "nice patch" and then nothing. Should I stop sending new patches and
>work on another project, improve old patches and send an email everydays to
>the mailing list to get some reaction?
>
>Barry doesn't wa
an open source project. I contributed to
>many many projects, and I can say that Python is already one of the most
>reactive project! But it can be better ;-)
I agree! How can we improve our development process, given that we're an all
volunteer organization?
- -Barry
-BEG
think I just f'd up the Apache conf. I'll try to fix that.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkKyLYACgkQ2YZpQepbvXG2pQCgh61b5hA7ECT5mNO+vbmJICYR
tRoAoJEa3XGzM06qNepsnhHldzLPF4kG
=8JK8
-END PGP SIGNATURE-
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 31, 2008, at 08:58 AM, Barry Warsaw wrote:
>Naw, I think I just f'd up the Apache conf. I'll try to fix that.
And by "I'll" of course I meant "Martin". :)
Thanks Martin!
- -Barry
-BEGIN PGP SIG
thon.org/snapshots/python-bzr-snapshot.tar.bz2, which is
> > a 404. Anyone know the actual URL?
Looks like this is fixed now too.
Aside: Now that Python 2.6 isn't on the trunk, we need to add a bzr mirror for
python26-maint.
- -Barry
-BEGIN PGP SIGNATU
he actual URL?
This is fixed now.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSQ2eDnEjvBPtnXfVAQJf+gP7BvsB7NtENGqbQR7oGMGjie75MrEn362Y
hXcgALWn9UkaiSdcrL+b9DFLY8MYppYUvKEJw92gU9jMzIzgcdH57DGBkudx/PHS
hkvPhtGewdSX1QY88CkOYjJ7UYnhrhZWUzN67Yea16QKBwPKQFljsC26toqX+0
2001 - 2100 of 2826 matches
Mail list logo
