[Python-ideas] Smoothing transition to Python 3

[Brett Cannon]

On Wed, Jun 8, 2016, 03:57 Thomas Güttler <guettliml at thomas-guettler.de>
wrote:

>
>
> Am 07.06.2016 um 17:26 schrieb Guido van Rossum:
> > On Tue, Jun 7, 2016 at 3:42 AM, Thomas Güttler <
> guettliml at thomas-guettler.de <mailto:guettliml at thomas-guettler.de>> wrote:
> >
> >     Am 04.06.2016 um 10:27 schrieb Neil Schemenauer:
> >     > I can't understand why people don't see
> >     > we have a problem.
> >
> >     Imagine you are father of a three years old boy. Some stranger
> >     tells you: "your kid is ugly!"
> >
> >
> > Just in case you didn't realize this can be turned around too, that's
> exactly how it feels to *me* when people complain
> > about Python 3.
>
> Yes, this hurts. But nevertheless you listen and try to understand
> the reasons. That's why Python is successful. Thank you Guido!
>
> >
> >     How does the average man react? Some get sad, some get angry.
> >
> >     Only very few would ask: Why do you think my kid is ugly?
> >
> >     I am not married with Python. Up to now I see no alternative for me,
> >     but I guess sooner or later I will switch to a different
> >     language.
> >
> >     I see only few benefits from porting my code to Python3. I will
> >     use Python2 at least for the next 12 months.
> >
> >
> > That sounds like a threat (or another underhanded insult), but it's
> really up to you.
>
>  From Wikipedia: ... a devil's advocate is someone who, given a certain
> argument, takes a position they do not
> necessarily agree with (or simply an alternative position from the
> accepted norm), for the sake of debate or to explore
> the thought further.
>

The point is that you don't state you're playing devil's advocate and you
phrase your statements in such a way that they can be (mis)construed as an
insult. There's nothing wrong with stating the other view of a discussion,
but you still have to take care to state it politely.


> Back to Python3: I compare the 3.2 and current docs about "Porting Python
> 2 Code to Python 3"
>
> https://docs.python.org/3.2/howto/pyporting.html
> https://docs.python.org/3.5/howto/pyporting.html
>
> The 3.2 version started with "Choosing a Strategy" the current docs start
> with "1. ..., 2. ..., 3. ..."
>
> I read the porting docs years ago, and I was not able to choose a
> strategy. I was unsure. (sheeps don't like fog)
> I think, at least sometimes, docs are more important than code.
>
> The current docs give me a nice roadmap. I will follow them, but not in
> 2016.
>

I changed the docs when it became obvious the community had chosen the 2/3
support structure for porting code.

-brett



> Regards,
>    Thomas Güttler
>
>
>
>
> Regards,
>    Thomas Güttler
>
> --
> Thomas Guettler http://www.thomas-guettler.de/
> _______________________________________________
> Python-ideas mailing list
> Python-ideas at python.org
> https://mail.python.org/mailman/listinfo/python-ideas
> Code of Conduct: http://python.org/psf/codeofconduct/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20160608/cfd87431/attachment.html>