Mailman 3 July 2017 - Linux-sig

Re: [Linux-SIG] Revisit of PEP 394 -- The "python" Command on Unix-Like Systems
by Barry Warsaw July 31, 2017

July 31, 2017

On Jul 26, 2017, at 00:29, Nick Coghlan <ncoghlan(a)gmail.com> wrote: > > At the PEP 394 level, what I'd personally like to see us do is to > split the "Recommendations" section into two separate sections: > "Python User Recommendations" and "Platform Publisher Recommendations” I’d like to keep PEP 394 as short and proscriptive as possible. I’ve always read PEP 394 as being aimed at “platform publisher recommendations”, i.e. distributions who provide. I think a user guide … [View More]

2 1

Revisit of PEP 394 -- The "python" Command on Unix-Like Systems
by Charalampos Stratakis July 31, 2017

July 31, 2017

Hello everyone, tl;dr Let's make sure that PEP 394 says "/usr/bin/python should be Python 3 by early 2020" As Python 2's end of life is approaching, various Linux distributions are taking measures to tackle the issue, raising awareness, porting packages and tools to Python 3, having only Python 3 preinstalled on their base images, and some have even made the ultimate change: making /usr/bin/python point to the Python 3 interpreter. Some references [0][1][2][3][4]. Various upstream Python … [View More]

4 4

Re: [Linux-SIG] Revisit of PEP 394 -- The "python" Command on Unix-Like Systems
by Guido van Rossum July 31, 2017

July 31, 2017

I hope I don't have to read that (I am behind on so many things to review already). It's just an informational PEP, so you can just write whatever you want without seeking approval. Right? On Mon, Jul 31, 2017 at 3:44 AM, Nick Coghlan <ncoghlan(a)gmail.com> wrote: > On 26 July 2017 at 15:53, Chris Angelico <rosuav(a)gmail.com> wrote: > > On Wed, Jul 26, 2017 at 2:29 PM, Nick Coghlan <ncoghlan(a)gmail.com> > wrote: > >> There's unfortunately no completely … [View More]non-disruptive way to manage this > >> shift (hence why it's taking so long), but we think this is a > >> reasonable approach that allows each distro to devise a migration plan > >> that makes sense for them and their userbase while still allow Python > >> end users to write readable cross-distro code that doesn't particular > >> care whether it's run under Python 2 or Python 3, and for open source > >> Python project maintainers to provide developer guidelines that are > >> entirely independent of particular distro's choices about default > >> Python runtimes. > >> > >> Before taking this proposal to python-dev, I'd turn the general > >> concept into an actual PR with specific proposed wording changes, but > >> I figured it made sense for us to seek some initial feedback here > >> before doing that. > > Draft updated PEP is posted at https://github.com/python/peps/pull/315 > > I ended up proposing a replacement PEP to supersede 394, rather than > proposing changes to 394 itself. > > It's essentially a PEP 394 superset that allows for a few more > "endorsed" configurations for redistributors (essentially saying > "Arch's move was ~5 years ahead of its time"), with more of an > emphasis on "What might a post-2020 sans-Python-2 platform release > look like?" > > Structurally, it clearly separates the recommendations into 3 distinct > sets (ad hoc scripting, app development, and platform publication) > > > Sounds good to me. (I'm not subbed to linux-sig, though perhaps I > > should be.) Did I get copied in on this for assistance with the PEP > > writing? In any case, I'm wholly in favour of the transition. > > I'm not sure how you ended up receiving it, unless there's something > odd going on with the configuration of linux-sig-owner in the mail > server. > > Cheers, > Nick. > > -- > Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia > _______________________________________________ > Linux-sig mailing list > Linux-sig(a)python.org > https://mail.python.org/mailman/listinfo/linux-sig > -- --Guido van Rossum (python.org/~guido) [View Less]

1 0

Re: [Linux-SIG] Revisit of PEP 394 -- The "python" Command on Unix-Like Systems
by Nick Coghlan July 31, 2017

July 31, 2017

On 26 July 2017 at 15:53, Chris Angelico <rosuav(a)gmail.com> wrote: > On Wed, Jul 26, 2017 at 2:29 PM, Nick Coghlan <ncoghlan(a)gmail.com> wrote: >> There's unfortunately no completely non-disruptive way to manage this >> shift (hence why it's taking so long), but we think this is a >> reasonable approach that allows each distro to devise a migration plan >> that makes sense for them and their userbase while still allow Python >> end users to write … [View More]

1 0

Re: [Linux-SIG] Revisit of PEP 394 -- The "python" Command on Unix-Like Systems
by Chris Angelico July 26, 2017

July 26, 2017

On Wed, Jul 26, 2017 at 2:29 PM, Nick Coghlan <ncoghlan(a)gmail.com> wrote: > There's unfortunately no completely non-disruptive way to manage this > shift (hence why it's taking so long), but we think this is a > reasonable approach that allows each distro to devise a migration plan > that makes sense for them and their userbase while still allow Python > end users to write readable cross-distro code that doesn't particular > care whether it's run under Python 2 or … [View More]

1 0