Re: Considering dropping Python 2 support (was Re: Python.h quirk)

2019-09-23 Thread Eric S. Raymond via devel
Gary E. Miller via devel : > Yo Mark! > > On Sat, 21 Sep 2019 14:33:37 -0700 > Mark Atwood via devel wrote: > > > Given that the Python community is driving hard on deprecating > > Python2 on 2020-01-01, I'm inclined to drop Python2 support on that > > date. > > > > https://pythonclock.org/ >

Re: Python.h quirk

2019-09-22 Thread Gary E. Miller via devel
Yo Eric! On Sat, 21 Sep 2019 14:03:28 -0400 "Eric S. Raymond via devel" wrote: > > It turns out that building ntpc.so had used the Python.h from > > python2 rather than the one for python3 Downhill from there. > > The problem, of course, is that the Python 2 and Python3 development > package bo

Re: Considering dropping Python 2 support (was Re: Python.h quirk)

2019-09-22 Thread Gary E. Miller via devel
Yo Mark! On Sat, 21 Sep 2019 14:33:37 -0700 Mark Atwood via devel wrote: > Given that the Python community is driving hard on deprecating > Python2 on 2020-01-01, I'm inclined to drop Python2 support on that > date. > > https://pythonclock.org/ Python 2 has been deprecated since before 2015.

Re: Python.h quirk

2019-09-22 Thread Hal Murray via devel
e...@thyrsus.com said: > The problem, of course, is that the Python 2 and Python3 development package > both want to own Python.h, and the name is not versioned. They are in different directories. The version number is in the directory. [murray@hgm raw]$ locate Python.h /usr/include/pytho

Re: Considering dropping Python 2 support (was Re: Python.h quirk)

2019-09-22 Thread Hal Murray via devel
> Given that the Python community is driving hard on deprecating Python2 on > 2020-01-01, I'm inclined to drop Python2 support on that date. That doesn't give us an excuse to screwup just because somebody has an old file around. Lots of people run old unsupported software. > the distros wil

Considering dropping Python 2 support (was Re: Python.h quirk)

2019-09-21 Thread Mark Atwood via devel
On Sat, Sep 21, 2019, at 11:03, Eric S. Raymond via devel wrote: > > The problem, of course, is that the Python 2 and Python3 development > package both want to own Python.h, > and the name is not versioned. > > I don't see any fix for this other than "have the right dev kit > installed whebn

Re: Python.h quirk

2019-09-21 Thread Eric S. Raymond via devel
Hal Murray via devel : > > I'm on Fedora. I've been using python2 for ages. I just tried to switch to > python3. > My "python" command now links to python3.7 > > It all builds, then dies trying to run the version printout tests which > really > test that it can load all the libraries it need

Python.h quirk

2019-09-20 Thread Hal Murray via devel
I'm on Fedora. I've been using python2 for ages. I just tried to switch to python3. My "python" command now links to python3.7 It all builds, then dies trying to run the version printout tests which really test that it can load all the libraries it needs. That died in util.py while trying