RetroSearch Browse

Fri Jun 6 17:47:24 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-June/134865.html

On 2014-06-06 10:31, Victor Stinner wrote:
> Hi,
>
> I added a new BaseEventLoop.is_closed() method to Tulip and Python
> 3.5 to fix an issue (see Tulip issue 169 for the detail). The problem
> is that I don't want to add this method to Python 3.4 because usually
> we don't add new methods in minor versions of Python (future version
> 3.4.2 in this case).
>
> Guido just wrote in the issue: "Actually for asyncio we have special
> dispensation to push new features to minor releases (until 3.5).
> Please push to 3.4 so the source code is the same everywhere (except
> selectors.py, which is not covered by the exception)."
>
> I disagree with Guido. I would prefer to start to maintain a
> different branch for Python 3.4, because I consider that only
> bugfixes should be applied to Python 3.4.
>
[snip]

Isn't this a little like when bool, True and False were added to
Python 2.2.1, a bugfix release, an act that is, I believe, now regarded
as a mistake not to be repeated?

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-June/134865.html below:

[Python-Dev] asyncio/Tulip: use CPython as the new upstream