No hurry! As long as we eventually have an PyPI version that is API-compatible with Python 3.4, I’m happy.
I asked because a user of my websockets library stumbled upon this difference: https://github.com/aaugustin/websockets/pull/11#issuecomment-34522177 The other change I noticed is readexactly(n) raising IncompleteReadError instead of returning fewer than n bytes. The new behavior is obviously better. For your information, I’m currently integrating the APIs introduced over the last months, mainly StreamReaderProtocol and drain(), and it’s forcing me to clean up my handling of connection termination, which is good! -- Aymeric. On 8 févr. 2014, at 17:53, Guido van Rossum <[email protected]> wrote: > You're right, I've been neglectful of the PyPI releases. My original plan was > to track each beta or RC with a Tulip PyPI release, but I got distracted, and > nobody asked me for it. In the past I've always done the Tulip release right > *after* the CPython release. Is it okay if I do the release this Monday > (assuming the RC comes out on schedule)? > > I can do a source release any time, but for a Windows release I need to be in > the office where I have a Windows laptop. So if you're in a hurry I can do > just a source release now and catch up with Windows Monday -- I am not > expecting any more changes over the weekend. (The main issue still being > discussed is the exception handling API but I don't want to rush it in -- it > can go into RC2 if we agree on the API.) > > PS. Have you noticed other incompatible changes? I've tried to be very > conservative about this (but honestly haven't received much feedback on this > aspect). > > > On Sat, Feb 8, 2014 at 12:03 AM, Aymeric Augustin > <[email protected]> wrote: > Hello, > > asyncio recently received some small but breaking API changes like > http://code.google.com/p/tulip/source/detail?r=5054d00a5fb10e5d09db6e419f2891c1b042036f. > > Since 3.4 RC1 is due tomorrow, I assume the API has stabilized. Would it be > possible to push a new release to PyPI? > > That would spare me the choice between keeping up with the development and > supporting the version available on PyPI :-) > > Thank you, > > -- > Aymeric. > > > > > > > -- > --Guido van Rossum (python.org/~guido)
