On 14 May 2018 at 12:34, Chris Barker via Python-Dev
wrote:
> On Sat, May 12, 2018 at 8:14 AM, Skip Montanaro
> wrote:
>
>> > I have found 2to3 conversion to be remarkably easy and painless.
>>
>> > And the whole Unicode thing is much easier.
>>
>
> Another point here:
>
> between 3.0 and 3.6 (.
> between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it
>> easier to write py2/py3 compatible code.
>> u"string", b'bytes %i' % something -- and when where the various
>> __future__ imports made available?
>>
>
> You'll need to be more specific. __future__ has been around for
On Monday, May 14, 2018, Ethan Furman wrote:
> On 05/14/2018 09:34 AM, Chris Barker via Python-Dev wrote:
>
> between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it
>> easier to write py2/py3 compatible code.
>> u"string", b'bytes %i' % something -- and when where the various
On 05/14/2018 09:34 AM, Chris Barker via Python-Dev wrote:
between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it
easier to write py2/py3 compatible code.
u"string", b'bytes %i' % something -- and when where the various __future__
imports made available?
If these had been
On Sat, May 12, 2018 at 8:14 AM, Skip Montanaro
wrote:
> > I have found 2to3 conversion to be remarkably easy and painless.
>
> > And the whole Unicode thing is much easier.
>
Another point here:
between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it
easier to write py2/py3
[esr]
> All this code runs under either 2 nor 3 without requiring six or any other
> shim library.
We've got an application that's about 500k loc, runs under both 2 and 3.
It has only one shim, a 'metaclass' decorator similar to what six provides,
other than that it's all quite clean 2- and 3-wise
> I have found 2to3 conversion to be remarkably easy and painless.
> And the whole Unicode thing is much easier.
The intersection of bytes, str and unicode has been the only pain point for
me. Everything else I've encountered has been pretty trivial.
Skip
Steven D'Aprano :
> So not all Python 3 migration stories turn into horror stories :-)
Peter Donis and wrote "Practical Python porting for systems programmers":
http://www.catb.org/esr/faqs/practical-python-porting/
We developed and applied these techniques on src (a lightweight version-control
On Fri, May 11, 2018 at 11:15:11AM -0700, Chris Barker - NOAA Federal via
Python-Dev wrote:
> > while the changes introduced by Python 3
> > affect pretty much everyone, even people who only write small simple
> > scripts.
>
> Sure they do, but the *hard stuff* not so much.
>
> I have found 2to3
> while the changes introduced by Python 3
> affect pretty much everyone, even people who only write small simple
> scripts.
Sure they do, but the *hard stuff* not so much.
I have found 2to3 conversion to be remarkably easy and painless.
And the whole Unicode thing is much easier.
CHB
> Regar
2018-04-28 3:33 GMT+02:00 Greg Ewing :
> Victor Stinner wrote:
>>
>> In my opinion, the largest failure of Python 3 is that we failed to
>> provide a smooth and *slow* transition from Python 2 and Python 3.
>
> Although for some things, such as handling of non-ascii text, it's
> hard to see how a s
On Fri, 27 Apr 2018 14:13:32 +0200
Victor Stinner wrote:
>
> I don't think that having Python X.Y which introduces backward
> incompatible changes is an issue by itself. We did it multiple times
> during the Python 3 cycle: my PEP 446 (non-inheritable file
> descriptors) and PEP 475 (retry syscal
On Sat, Apr 28, 2018 at 10:36 AM Greg Ewing
wrote:
> Victor Stinner wrote:
> > In my opinion, the largest failure of Python 3 is that we failed to
> > provide a smooth and *slow* transition from Python 2 and Python 3.
> Although for some things, such as handling of non-ascii text, it's
> hard to
On 2018-04-28, 01:33 GMT, Greg Ewing wrote:
>> In my opinion, the largest failure of Python 3 is that we
>> failed to provide a smooth and *slow* transition from Python
>> 2 and Python 3.
>
> Although for some things, such as handling of non-ascii text, it's
> hard to see how a smooth transition
Victor Stinner wrote:
In my opinion, the largest failure of Python 3 is that we failed to
provide a smooth and *slow* transition from Python 2 and Python 3.
Although for some things, such as handling of non-ascii text, it's
hard to see how a smooth transition *could* have been achieved.
Is it a
On 04/27/2018 04:34 AM, Serhiy Storchaka wrote:
27.04.18 13:25, Nick Coghlan пише:
and PEP 3099 (explicitly
rejected ideas that also didn't get their own PEPs).
"There will be no alternative binding operators such as :=."
Which is why changing that requires a PEP now.
--
~Ethan~
On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow wrote:
> In pondering our approach to future Python major releases, I found
> myself considering the experience we've had with Python 3. The whole
> Py3k effort predates my involvement in the community so I missed a
> bunch of context about the motivati
In my opinion, the largest failure of Python 3 is that we failed to
provide a smooth and *slow* transition from Python 2 and Python 3. It
can be explained by the long list of backward incompatible changes.
My advice would be to restrict the number of backward incompatible
changes per release, and
27.04.18 13:25, Nick Coghlan пише:
and PEP 3099 (explicitly
rejected ideas that also didn't get their own PEPs).
"There will be no alternative binding operators such as :=."
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/ma
On Thursday, April 26, 2018, Eric Snow wrote:
> In pondering our approach to future Python major releases, I found
> myself considering the experience we've had with Python 3. The whole
> Py3k effort predates my involvement in the community so I missed a
> bunch of context about the motivations,
I gave the talk "Python 3: 10 years later" at FOSDEM and Pycon Italy
and will give it again at Pycon US next month:
https://fosdem.org/2018/schedule/event/python3/
My talk is focused on the migration path. How to "port" Python 2 code
to Python 3, 2to3 tool, six module, things done to make the migr
On 27 April 2018 at 03:18, Barry Warsaw wrote:
> On Apr 26, 2018, at 09:28, Eric Snow wrote:
>>
>> On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow
>> wrote:
>>> In pondering our approach to future Python major releases, I found
>>> myself considering the experience we've had with Python 3. The who
On 04/26/2018 09:02 PM, Alex Walters wrote:
http://pyvideo.org/pycascades-2018/bdfl-python-3-retrospective.html link to
Guido’s talk, for your convenience
Many thanks!
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python
Retrospective on the Move to Python 3
Also see my talk at PyCascades and Victor's upcoming talk at PyCon.
On Thu, Apr 26, 2018, 12:02 Brett Cannon mailto:br...@python.org> > wrote:
On Thu, 26 Apr 2018 at 10:19 Barry Warsaw mailto:ba...@python.org> > wrote:
On Apr 26, 201
Also see my talk at PyCascades and Victor's upcoming talk at PyCon.
On Thu, Apr 26, 2018, 12:02 Brett Cannon wrote:
>
>
> On Thu, 26 Apr 2018 at 10:19 Barry Warsaw wrote:
>
>> On Apr 26, 2018, at 09:28, Eric Snow wrote:
>> >
>> > On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow <
>> ericsnowcurren.
On Thu, 26 Apr 2018 at 10:19 Barry Warsaw wrote:
> On Apr 26, 2018, at 09:28, Eric Snow wrote:
> >
> > On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow
> wrote:
> >> In pondering our approach to future Python major releases, I found
> >> myself considering the experience we've had with Python 3. Th
On Apr 26, 2018, at 09:28, Eric Snow wrote:
>
> On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow
> wrote:
>> In pondering our approach to future Python major releases, I found
>> myself considering the experience we've had with Python 3. The whole
>> Py3k effort predates my involvement in the commu
On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow wrote:
> In pondering our approach to future Python major releases, I found
> myself considering the experience we've had with Python 3. The whole
> Py3k effort predates my involvement in the community so I missed a
> bunch of context about the motivati
In pondering our approach to future Python major releases, I found
myself considering the experience we've had with Python 3. The whole
Py3k effort predates my involvement in the community so I missed a
bunch of context about the motivations, decisions, and challenges.
While I've pieced some of th
29 matches
Mail list logo