Re: Offer to help with Python 2 porting

2015-04-17 Thread Ben Finney
Paul Wise writes: > Paul has created a new list for the porting effort, please subscribe there: > > https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel Can someone please subscribe GMane to that new list http://gmane.org/subscribe.php>, perhaps using the name ‘gmane.linux.debian.de

Re: Offer to help with Python 2 porting

2015-04-17 Thread Paul Tagliamonte
GMane has been added to the list, should be up soon, I think! (with that path) We can talk more off-list on other things I need to do (how to import archives?) On Fri, Apr 17, 2015 at 3:36 AM, Ben Finney wrote: > Paul Wise writes: > >> Paul has created a new list for the porting effort, please

Re: Python 2, Python 3, Stretch & Buster

2015-04-17 Thread Barry Warsaw
On Apr 17, 2015, at 12:45 AM, Thomas Goirand wrote: >I'd be happy to share some more links of useful stuff about porting to Python >3 (I have some more on my "other laptop" (tm)). Is there already a page with >some links on the subject in the Debian wiki? Not in the Debian wiki (though it started

Re: Offer to help with Python 2 porting

2015-04-17 Thread Ben Finney
Paul Tagliamonte writes: > GMane has been added to the [‘py3porters-devel’] list, should be up > soon, I think! (with that path [‘gmane.linux.debian.devel.python.py3porters’]) Thanks, Paul, it works fine for me. -- \ “The long-term solution to mountains of waste is not more | `\

/usr/bin/python in Python 2 and 3

2015-04-17 Thread Geoffrey Thomas
I've written up the proposal I made a few days ago for a /usr/bin/python launcher that keeps the API of being Python 2, but lets scripts opt in to running on Python 3: https://ldpreload.com/blog/usr-bin-python-23 I share the desire for /usr/bin/python to maintain its API of being Python 2, bu

Re: /usr/bin/python in Python 2 and 3

2015-04-17 Thread Thomas Kluyver
I think the basic shape of this idea is good - it's a neat way to keep the ubiquitous 'python' command available as Python 2 starts to go away, without breaking compatibility with all the scripts that expect that command to mean Python 2. You're essentially saying that 'python' can be Python 3, but