Re: People choosing Python 3

2017-09-13 Thread Michael Torrie
On 09/11/2017 06:00 AM, Pavol Lisy wrote: >> Debian follows PEP 394, which recommends that "python" point to python2, >> and I don't see that changing any time soon (certainly not before RHEL >> includes python3 by default. > > Which part of third party ecosystem surrounding Python 3 is not (and >

Re: People choosing Python 3

2017-09-13 Thread Michael Torrie
On 09/11/2017 01:47 AM, Stephan Houben wrote: > Op 2017-09-10, Marko Rauhamaa schreef : >> Stephan Houben : >>> >>> Why not bundle the Python interpreter with your application? >>> It seems to work for Windows developers... >> >> I've seen that done for Python and other technologies. It is an >> ex

Re: People choosing Python 3

2017-09-13 Thread Michael Torrie
On 09/10/2017 03:25 AM, Leam Hall wrote: > From a non-rpm perspective Python 3.6.2 compiles nicely on CentOS 6. > Once compiled it seems easy to use pip3 to install stuff without > trampling on the OS's Python 2 install. In the last place I worked, our servers usually did not have compilers inst

Re: People choosing Python 3

2017-09-11 Thread Paul Moore
On 11 September 2017 at 15:53, Dennis Lee Bieber wrote: > > As for Windows itself... I use the ActiveState installers and see: > > Directory of c:\Python35 > > > 06/26/2017 07:22 PM41,240 python.exe > 06/26/2017 07:22 PM41,240 python3.5.exe > 06/26/2017 07:18 P

Re: People choosing Python 3

2017-09-11 Thread Matt Ruffalo
On 2017-09-10 05:42, Chris Warrick wrote: > > RHEL’s release process starts at forking a recent Fedora release. It > wouldn’t make much sense for them to undo the Python 3 progress that > happened over the past few years in Fedora — including dnf, an > improved package manager written in Python 3.

Re: People choosing Python 3

2017-09-11 Thread Chris Angelico
On Mon, Sep 11, 2017 at 10:40 PM, Paul Moore wrote: > On 11 September 2017 at 13:07, Chris Angelico wrote: >> Fortunately, it's not that hard to type "python3" all the time. OS >> distributions can progressively shift to using that name, and then >> eventually not ship a Py2 until/unless somethin

Re: People choosing Python 3

2017-09-11 Thread Paul Moore
On 11 September 2017 at 13:07, Chris Angelico wrote: > Fortunately, it's not that hard to type "python3" all the time. OS > distributions can progressively shift to using that name, and then > eventually not ship a Py2 until/unless something depends on it, all > without losing backward compatibili

Re: People choosing Python 3

2017-09-11 Thread Chris Angelico
On Mon, Sep 11, 2017 at 10:00 PM, Pavol Lisy wrote: > On 9/11/17, Thomas Jollans wrote: >> On 2017-09-10 09:05, INADA Naoki wrote: >>> I saw encouraging tweet from Kenneth Reitz. >>> >>> https://twitter.com/kennethreitz/status/902028601893294081/photo/1 >>> >>> On Heroku, most people choose Pytho

Re: People choosing Python 3

2017-09-11 Thread leam hall
On Mon, Sep 11, 2017 at 8:00 AM, Pavol Lisy wrote: > > > Which part of third party ecosystem surrounding Python 3 is not (and > could not be any time soon) sufficiently mature? > -- > > yum, twisted. -- https://mail.python.org/mailman/listinfo/python-list

Re: People choosing Python 3

2017-09-11 Thread Pavol Lisy
On 9/11/17, Thomas Jollans wrote: > On 2017-09-10 09:05, INADA Naoki wrote: >> I saw encouraging tweet from Kenneth Reitz. >> >> https://twitter.com/kennethreitz/status/902028601893294081/photo/1 >> >> On Heroku, most people choose Python 3! >> I know, it's because Python 3 is the default Python o

Re: People choosing Python 3

2017-09-11 Thread Thomas Jollans
On 2017-09-10 09:05, INADA Naoki wrote: > I saw encouraging tweet from Kenneth Reitz. > > https://twitter.com/kennethreitz/status/902028601893294081/photo/1 > > On Heroku, most people choose Python 3! > I know, it's because Python 3 is the default Python on Heroku. > > I can't wait Python 3 is t

Re: People choosing Python 3

2017-09-11 Thread Marko Rauhamaa
Stephan Houben : > Op 2017-09-10, Marko Rauhamaa schreef : >> I've seen that done for Python and other technologies. It is an >> expensive route to take. Also, it can be insecure. When >> vulnerabilities are found, they are communicated to the maintainers >> of, say, Python. When Python is fixed a

Re: People choosing Python 3

2017-09-11 Thread Stephan Houben
Op 2017-09-10, Marko Rauhamaa schreef : > Stephan Houben : >> >> Why not bundle the Python interpreter with your application? >> It seems to work for Windows developers... > > I've seen that done for Python and other technologies. It is an > expensive route to take. Also, it can be insecure. When v

Re: People choosing Python 3

2017-09-10 Thread Marko Rauhamaa
Stephan Houben : > Op 2017-09-10, Marko Rauhamaa schreef : >> As an application developer, I can't make the customers depend on EPEL. >> It's Python2 until the distro comes with Python3. > > Why not bundle the Python interpreter with your application? > It seems to work for Windows developers...

Re: People choosing Python 3

2017-09-10 Thread Stephan Houben
Op 2017-09-10, Marko Rauhamaa schreef : > As an application developer, I can't make the customers depend on EPEL. > It's Python2 until the distro comes with Python3. Why not bundle the Python interpreter with your application? It seems to work for Windows developers... Stephan -- https://mail.py

Re: People choosing Python 3

2017-09-10 Thread Gene Heskett
On Sunday 10 September 2017 05:25:51 Leam Hall wrote: > On 09/10/2017 04:19 AM, Chris Warrick wrote: > > On 10 September 2017 at 09:30, Marko Rauhamaa wrote: > >> INADA Naoki : > >>> I can't wait Python 3 is the default Python of Red Hat, and > >>> "python" command means Python 3 on Debian and U

Re: People choosing Python 3

2017-09-10 Thread Chris Warrick
On 10 September 2017 at 11:24, Leam Hall wrote: > On 09/10/2017 04:19 AM, Chris Warrick wrote: >> >> On 10 September 2017 at 09:30, Marko Rauhamaa wrote: >>> >>> INADA Naoki : >>> I can't wait Python 3 is the default Python of Red Hat, and "python" command means Python 3 on Debian and U

Re: People choosing Python 3

2017-09-10 Thread Marko Rauhamaa
Chris Warrick : > On 10 September 2017 at 09:30, Marko Rauhamaa wrote: >> I can't wait till Python 3 is available on Red Hat. > > Python 3.4 is available in EPEL. As an application developer, I can't make the customers depend on EPEL. It's Python2 until the distro comes with Python3. > RHEL 8 w

Re: People choosing Python 3

2017-09-10 Thread Leam Hall
On 09/10/2017 04:19 AM, Chris Warrick wrote: On 10 September 2017 at 09:30, Marko Rauhamaa wrote: INADA Naoki : I can't wait Python 3 is the default Python of Red Hat, and "python" command means Python 3 on Debian and Ubuntu. I can't wait till Python 3 is available on Red Hat. Python 3.4

Re: People choosing Python 3

2017-09-10 Thread Chris Warrick
On 10 September 2017 at 09:30, Marko Rauhamaa wrote: > INADA Naoki : > >> I can't wait Python 3 is the default Python of Red Hat, and "python" >> command means Python 3 on Debian and Ubuntu. > > I can't wait till Python 3 is available on Red Hat. Python 3.4 is available in EPEL. RHEL 8 will switc

Re: People choosing Python 3

2017-09-10 Thread Marko Rauhamaa
INADA Naoki : > I can't wait Python 3 is the default Python of Red Hat, and "python" > command means Python 3 on Debian and Ubuntu. I can't wait till Python 3 is available on Red Hat. Marko -- https://mail.python.org/mailman/listinfo/python-list

People choosing Python 3

2017-09-10 Thread INADA Naoki
I saw encouraging tweet from Kenneth Reitz. https://twitter.com/kennethreitz/status/902028601893294081/photo/1 On Heroku, most people choose Python 3! I know, it's because Python 3 is the default Python on Heroku. I can't wait Python 3 is the default Python of Red Hat, and "python" command means