At the language summit, Alex and I volunteered to put together some
recommendations on what changes could be made to Python (the language) in order
to facilitate a smoother transition from Python 2 to Python 3. One of the
things that motivated this was the (surprising, to us) consideration that
On Wed May 28 2014 at 10:14:39 PM, Glyph Lefkowitz
wrote:
> At the language summit, Alex and I volunteered to put together some
> recommendations on what changes could be made to Python (the language) in
> order to facilitate a smoother transition from Python 2 to Python 3. One
> of the things t
Thanks for for putting this together.
On Wed, May 28, 2014 at 4:26 PM, Glyph Lefkowitz
wrote:
> At the language summit, Alex and I volunteered to put together some
> recommendations on what changes could be made to Python (the language) in
> order to facilitate a smoother transition from Python 2
On Wed, May 28, 2014, at 15:26, Glyph Lefkowitz wrote:
> Add some warnings about python 3 compatibility.
> It should at least be possible to get a warning for every single implicit
> string coercion.
> Old-style classes.
> Old-style division.
Fun fact: This can be achieved with the -Qwarn comman
> We would like to stress that we don't believe anything on this list is as
> important as the continuing efforts that everyone in the broader ecosystem
> is making. If you just want to ease the transition by working on anything
> at all, the best use of your time right now is porting
> https://wa
On 5/29/2014 1:22 AM, INADA Naoki wrote:
We would like to stress that we don't believe anything on this list is as
important as the continuing efforts that everyone in the broader ecosystem
is making. If you just want to ease the transition by working on anything
at all, the best use of your tim
On 29 May 2014 08:26, Glyph Lefkowitz wrote:
Thanks for the write-up!
> Here are some ideas for Python 2.7+.
>
> Add ensurepip to the installers. Having pip reliably available increases
> the availability of libraries that help with porting, and will generally
> strengthen the broader ecosystem
On 5/28/2014 6:26 PM, Glyph Lefkowitz wrote:
I hope it's
not controversial to say that most new Python code is still being
written against Python 2.7 today;
Given that Python 3 downloads now outnumber Python 2 downloads, I think
'most' might be an overstatement. But I think it a moot point.
On Thu, May 29, 2014 at 4:43 AM, Nick Coghlan wrote:
> For that last point, my interest is as much educational as it is in
> easing the transition from Python 2. The parentheses in "print('Hello
> world!')" mean introducing the idea of function calls early to explain
> how it works, while being a
On Thu, May 29, 2014 at 9:30 AM, Terry Reedy wrote:
> On 5/28/2014 6:26 PM, Glyph Lefkowitz wrote:
>
> I hope it's
>> not controversial to say that most new Python code is still being
>> written against Python 2.7 today;
>>
>
> Given that Python 3 downloads now outnumber Python 2 downloads, I th
On Sat, May 31, 2014 at 3:40 AM, Mark Roberts wrote:
> What I'd really like to see is a Python 2.8 that makes sufficient changes to
> Python 2 that writing libraries which cross the boundary between 2 and 3 is
> relatively easy instead of a painful nightmarish chore. Because when push
> comes to
On 30/05/2014 18:40, Mark Roberts wrote:
What I'd really like to see is a Python 2.8 that makes sufficient
changes to Python 2 that writing libraries which cross the boundary
between 2 and 3 is relatively easy instead of a painful nightmarish
chore. Because when push comes to shove, Python 2 su
On 05/30/2014 09:46 AM, Chris Barker wrote:
On Thu, May 29, 2014 at 4:43 AM, Nick Coghlan wrote:
For that last point, my interest is as much educational as it is in
easing the transition from Python 2. The parentheses in "print('Hello
world!')" mean introducing the idea of function calls early
On Wed, 28 May 2014 15:26:38 -0700
Glyph Lefkowitz wrote:
> Backport 'yield from' to allow people to use Tulip and Tulip-compatible code,
> and to facilitate the development of Tulip-friendly libraries and a Tulip
> ecosystem. A robust Tulip ecosystem requires the participation of people who
>
2to3 is poorly named. With different fixers it is a fine tool for
converting 2-only code to 2-and-3 straddling code. Even when using six, you
need to do things like convert print statements to print() calls with
future import, use 'as' in except clauses, and so on.
On Fri, May 30, 2014 at 1:47 PM
On 31 May 2014 08:42, "Guido van Rossum" wrote:
>
> 2to3 is poorly named. With different fixers it is a fine tool for
converting 2-only code to 2-and-3 straddling code. Even when using six, you
need to do things like convert print statements to print() calls with
future import, use 'as' in except
On 31 May 2014 02:47, "Chris Barker" wrote:
> However, I also believe that when teaching it's better to introduce the
"right way" to do something up front, rather than a "beginners' way", then
later say, well, you really SHOULD do it this other way... So if we want
our students to use print as a f
On 31 May 2014 03:42, "Mark Roberts" wrote:
>
> What I'd really like to see is a Python 2.8 that makes sufficient changes
to Python 2 that writing libraries which cross the boundary between 2 and 3
is relatively easy instead of a painful nightmarish chore.
That's what projects like python-future
On Fri, May 30, 2014 at 7:05 PM, Nick Coghlan wrote:
> I already have too many other things on my todo list to work this up into
> a full PEP, but the proof of concept (along with IPython's existing
> support) shows there's no *technical* barrier to adding the feature.
>
That doesn't follow. A P
Right. The point is that the current HOWTO gives information that is not
useful for most people who are tasked with a port.
On Fri, May 30, 2014 at 6:46 PM, Nick Coghlan wrote:
>
> On 31 May 2014 08:42, "Guido van Rossum" wrote:
> >
> > 2to3 is poorly named. With different fixers it is a fine
Chris Barker writes:
> that way. Saying that their very first easy program is:
>
> print("hello world")
>
> is fine
I have had similar experience on a small scale.
Also I've been teaching R recently. The students who know Python
(Python 3, we don't have backward compatibility issues in o
21 matches
Mail list logo
