Re: [Python-Dev] Python 2.7 EOL date

2018-08-23 Thread Eric V. Smith
On 8/23/2018 8:14 PM, Barry Warsaw wrote: On Aug 23, 2018, at 15:23, Eric V. Smith wrote: On 8/23/2018 4:30 PM, Victor Stinner wrote: Hi, The reference is the PEP 373 "Python 2.7 Release Schedule". See the "Update" section: https://www.python.org/dev/peps/pep-0373/#update We could probably

Re: [Python-Dev] Python 2.7 EOL date

2018-08-23 Thread Barry Warsaw
On Aug 23, 2018, at 15:23, Eric V. Smith wrote: > > On 8/23/2018 4:30 PM, Victor Stinner wrote: >> Hi, >> The reference is the PEP 373 "Python 2.7 Release Schedule". See the >> "Update" section: >> https://www.python.org/dev/peps/pep-0373/#update > > We could probably make it more clear in this

Re: [Python-Dev] Python 2.7 EOL date

2018-08-23 Thread Eric V. Smith
On 8/23/2018 4:30 PM, Victor Stinner wrote: Hi, The reference is the PEP 373 "Python 2.7 Release Schedule". See the "Update" section: https://www.python.org/dev/peps/pep-0373/#update We could probably make it more clear in this section and/or in https://www.python.org/dev/peps/pep-0373/#id4

Re: [Python-Dev] Python 2.7 EOL date

2018-08-23 Thread Victor Stinner
Hi, The reference is the PEP 373 "Python 2.7 Release Schedule". See the "Update" section: https://www.python.org/dev/peps/pep-0373/#update Victor 2018-08-23 20:53 GMT+02:00 Collin Anderson : > Hi All, > > Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL > date was

Re: [Python-Dev] Let's change to C API!

2018-08-23 Thread Stefan Behnel
Greg Ewing schrieb am 23.08.2018 um 03:34: > Neil Schemenauer wrote: >> Perhaps a "argument clinic on steroids" would be the proper >> approach.  So, extensions would mostly be written in C.  However, we >> would have a pre-processor that does some "magic" to make using the >> Python API cleaner.

Re: [Python-Dev] Let's change to C API!

2018-08-23 Thread Stefan Behnel
Antoine Pitrou schrieb am 23.08.2018 um 09:04: > On Thu, 23 Aug 2018 08:07:08 +0200 > Jeroen Demeyer wrote: >>> - the maintenance problem (how do ensure we can change small things in >>>the C API, especially semi-private ones, without having to submit PRs >>>to Cython as well) >> >> Why

Re: [Python-Dev] Python 2.7 EOL date

2018-08-23 Thread Mariatta Wijaya
No more security fixes after Jan 1, 2020. It is the end of Python 2.7. On Thu, Aug 23, 2018, 12:47 PM Collin Anderson wrote: > Hi All, > > Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL > date was recently set to Jan 1st, 2020. > > My understanding was Python

[Python-Dev] Python 2.7 EOL date

2018-08-23 Thread Collin Anderson
Hi All, Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL date was recently set to Jan 1st, 2020. My understanding was Python releases get 5 years of support from their initial release, and Python 2.7 was extended an additional 5 years. Python 2.7 was originally released

Re: [Python-Dev] Let's change to C API!

2018-08-23 Thread Antoine Pitrou
On Thu, 23 Aug 2018 08:07:08 +0200 Jeroen Demeyer wrote: > > > - the dependency / versioning problem (Cython is a large quick-evolving > >third-party package that we can't decently vendor) > > Is that a real problem? You're sort of doing the same thing with pip > already. Building and

Re: [Python-Dev] Let's change to C API!

2018-08-23 Thread Jeroen Demeyer
On 2018-08-23 07:36, Antoine Pitrou wrote: - the bootstrap problem (Cython self-compiles with CPython) This is not a big problem: we can make sure that all stdlib dependencies of Cython either have PEP 399 pure Python implementations or we keep them in pure C. - the dependency /