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
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
I have two areas of questions about updating turtle.py. First the module
itself, then a turtle tracker issue versus code cleanup policies.
A. Unlike most stdlib modules, turtle is copyrighted and licensed by an
individual.
'''
# turtle.py: a Tkinter based turtle graphics module for Python
# Ve
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 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 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
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 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
>
On Fri May 30 2014 at 3:39:47 PM, Eric Snow
wrote:
> On Fri, May 30, 2014 at 12:55 PM, brett.cannon
> wrote:
> > http://hg.python.org/cpython/rev/b26d021081d2
> > changeset: 90915:b26d021081d2
> > parent: 90913:69011f6ce573
> > user:Brett Cannon
> > date:Fri May 30 14:55:
On Fri, May 30, 2014 at 12:55 PM, brett.cannon
wrote:
> http://hg.python.org/cpython/rev/b26d021081d2
> changeset: 90915:b26d021081d2
> parent: 90913:69011f6ce573
> user:Brett Cannon
> date:Fri May 30 14:55:29 2014 -0400
> summary:
> Issue #20383: Introduce importlib.util
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 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 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 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 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
ACTIVITY SUMMARY (2014-05-23 - 2014-05-30)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4635 (+13)
closed 28750 (+40)
total 33385 (+53)
Open issues wit
16 matches
Mail list logo
