[Python-Dev] Deleting with setting C API functions

[Nick Coghlan]

On 3 December 2015 at 02:35, Guido van Rossum <guido at python.org> wrote:
> On Wed, Dec 2, 2015 at 7:32 AM, Emanuel Barry <vgr255 at live.ca> wrote:
>>
>> Nick Coghlan made a pretty elaborated blog post about that here:
>> http://opensource.com/life/14/9/why-python-4-wont-be-python-3
>
> I wholeheartedly agree with what Nick writes there -- but I can't resist
> noting that the title is backwards -- the whole point is that Python 4
> *will* be like Python 3, i.e. it will *not* differ (in a
> backward-incompatible way) from Python 3. What Nick probably meant is "Why
> the *transition to* Python 4 won't be like the transition to Python 3." And
> that is exactly right.

Yeah, the full title was actually "Why Python 4.0 won't be like Python
3.0" which I think better conveys the implied "transition to" aspect,
but the zeros got left out in the opensource.com URL. The RHEL dev
blog version uses the full title in the URL as well:
https://developerblog.redhat.com/2014/09/17/why-python-4-0-wont-be-like-python-3-0/

I also wrote the article before you mentioned you might be amenable to
doing a 3.10 instead of rolling over to 4.0 (although I suspect there
are even more systems that assume XY is sufficient to identify a
Python feature release than assumed XYZ was sufficient to identify
maintenance releases prior to 2.7.10)

Cheers,
Nick.

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