On Tue, Apr 14, 2015 at 10:00:07AM -0400, Scott Kitterman wrote: > It is, as I think it was you said, easy enough to write Python code these days > that works for both python and python3. As an upstream developer, go ahead > and do that and leave it to the distros to packageit appropriately for their > environment. FWIW; the only place I even touch Python 2 code is in Debian, 100% of work and personal software is Python 3. So, I'm a bit of a radical here, but I'm pretty anti-Python 2. Most of my projects don't support Python 2 at all. > I don't think it's possible to have something that at runtime call python2.7 > or python3 based on what's in the code. I believe the shim would be to yell at the user to install a legacy thing, not switch between the two, that was a joke Barry made during the Language summit. Howabout we wait until *after* we try to hash this out in person. I'll write up thoughts and we can form consensus after, on list and in a public way. I think the spread of opinions voiced in this thread will be well represented in the room, so it should go well to figure out stuff that would be practical and implementable.. If anyone has *different* oppinions, you should give me an off-thread ping with your thoughts so I can bring them up today. Cheers, Tag -- .''`. Paul Tagliamonte <paultag@debian.org> | Proud Debian Developer : :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `. `'` http://people.debian.org/~paultag `- http://people.debian.org/~paultag/conduct-statement.txt
Attachment:
signature.asc
Description: Digital signature