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

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

[Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?

• Previous message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
• Next message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 17 August 2014 15:08, Guido van Rossum <guido at python.org> wrote:
> I think this would be a great topic for a blog post. Once you've written it
> I can even bless it by Tweeting about it. :-)

Sounds like a plan - I'll try to put together something coherent this week :)

> PS. Why isn't PEP 387 accepted yet?

Not sure - it mostly looks correct to me. I suspect it just fell off
the radar since it's a "describe what we're already doing anyway" kind
of document.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

• Previous message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
• Next message: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4