http://bugs.python.org/issue3618 is a release blocker due to deadlock
in the io library.
and the related C RLock implementation in
http://bugs.python.org/issue3001 at this point in the release process.
Its obviously missed beta3 which is why I suggested in 3001 that it
was too late. That was bef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I am happy
to announce the third and last planned beta releases of Python 2.6 and Python
3.0.
Please note that these are beta releases, and as such are not suitable for
production envi
Greg Ewing wrote:
Levi wrote:
Recently I've taken some interest in PEP 3106 (revamping dick.keys,
^
Is this a feature related to some kind of chastity belt for men? :-)
I didn't notice that until I recived the message from the list. Truely
an embarrasssing typo to say the least.
Greg Ewing wrote:
Levi wrote:
Recently I've taken some interest in PEP 3106 (revamping dick.keys,
^
Is this a feature related to some kind of chastity belt for men? :-)
Maybe it's a brand new, special feature when a dict cont
Levi wrote:
Recently I've taken some interest in PEP 3106 (revamping dick.keys,
^
Is this a feature related to some kind of chastity belt for men? :-)
--
Greg
___
Python-3000 mailing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pending a resolution of bug 3611 (which has an attached patch that
we're testing now), I plan on releasing 2.6 and 3.0 beta 3 tonight.
Please do not make any commits to the trees unless you ask me first,
until further notice. I am on #python-de
Recently I've taken some interest in PEP 3106 (revamping dick.keys,
etc.) and wrote a rough draft of an experimental implementation in
Python. Along the way I noticed a few things that I think need some
discussion. A lot of them have to do with the interaction with PEP 3119
(Abstract Base Class
On Wed, Aug 20, 2008 at 9:19 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> Am I missing something in front of my nose? Where are the docs for
> 2to3? I've tried, and failed, several times to run this script.
>
> Also, python2.6 -3 did not seem to warn about xrange.
>
Warnings with the -3 flag o
Am I missing something in front of my nose? Where are the docs for
2to3? I've tried, and failed, several times to run this script.
Also, python2.6 -3 did not seem to warn about xrange.
Edward
Edward K. Ream email: [EMAIL PROTEC
Hello Nick,
> At some stage, we should probably put a simple type in the C API testing
> module that we can use to test some of the extra indexing and buffer
> interface features that aren't exercised within the standard library.
Yes, I think that's what we should do. The only problem is that ou
Antoine Pitrou wrote:
> Hi,
>
> Guido van Rossum python.org> writes:
>>> 2394[Py3k] Finish the memoryview object implementation
>>> - - High priority
>>> - - This one is serious enough to hold up the release. I really do not
> think we
>>> should be finishing this implementation in the rc p
On 2008-08-20 08:15, Hye-Shik Chang wrote:
On Mon, Aug 18, 2008 at 12:24 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
I'm -1 on taking this approach this late in the release process.
You are adding a completely new codec, which hasn't received enough
testing. Furthermore, the concept of relying
Hi,
I think the patches for issue 3492 should also be merged in for this beta.
It affects the behaviour of zlib module. I have submitted patches for
zlibmodule.c
and test_zlib.py a few weeks back and they are ready to be merged anytime.
I am forwarding a message where I discussed this with An
13 matches
Mail list logo
