[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-22 Thread Antoine Pitrou
Hi, Just bear in mind that I have read only a couple sentences in the PEP. But as soon as you propose to offer only "partial compatibility" with a previous version, then I think it's worse than useless. You are introducing an additional Python version, i.e. "3.9 bended towards 3.8 partial compa

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-19 Thread Richard Musil
On Fri, Oct 18, 2019 at 3:18 AM Victor Stinner wrote: > If possible, please try to read the whole PEP before replying. I would > prefer to avoid knee-jerk reactions :-) The backward compatibility is > complex topic where things are not black or white: it's more a > grayscale. The proposal seems

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-19 Thread M.-A. Lemburg
Hi Victor, I think this is a nice idea, but I do wonder how this would be used in practice: The problem is that Python projects typically use lots of 3rd party modules and if a few decide to use/rely on the feature, this may create a situation where packages then compete over which compatibility

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-18 Thread Brett Cannon
On Thu, Oct 17, 2019 at 7:39 PM Ethan Furman wrote: > On 10/17/2019 06:02 PM, Victor Stinner wrote: > > > I propose the following PEP to add > > sys.set_python_compat_version(version) to introduce a partial > > compatibility with Python 3.8 in the next Python 3.9 version. > > -1 > -1 from me as

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-18 Thread Victor Stinner
Hi Ethan, Le ven. 18 oct. 2019 à 04:38, Ethan Furman a écrit : > > To remain relevant and useful, Python has to evolve frequently. Some > > enhancements require incompatible changes. Any incompatible change can > > break an unknown number of Python projects. Developers can decide to > > not impl

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-17 Thread Brendan Barnwell
On 2019-10-17 18:02, Victor Stinner wrote: Hi, I propose the following PEP to add sys.set_python_compat_version(version) to introduce a partial compatibility with Python 3.8 in the next Python 3.9 version. I also propose this PEP in a pull request: https://github.com/python/peps/pull/1209 (Plea

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-17 Thread Dong-hee Na
I re-read your proposal. Please ignore my suggestion. :) I misunderstood core concept of your proposal :) 2019년 10월 18일 (금) 오전 10:19, Victor Stinner 님이 작성: > > Hi, > > I propose the following PEP to add > sys.set_python_compat_version(version) to introduce a partial > compatibility with Python 3.8

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-17 Thread Ethan Furman
On 10/17/2019 06:02 PM, Victor Stinner wrote: I propose the following PEP to add sys.set_python_compat_version(version) to introduce a partial compatibility with Python 3.8 in the next Python 3.9 version. -1 If possible, please try to read the whole PEP before replying. Done. TL;DR Besid

[Python-ideas] Re: RFC: PEP xxx: Python Compatibility Version

2019-10-17 Thread Dong-hee Na
The proposal looks awesome to me. Victor :) It could be out of scope for this proposal. How about adding APIs about compatibility implementation in this proposal? e.g compatibility_python_implementation usage will be sys.compatibility_python_implementation(('Cpython', 'PyPy', 'XXXPython')) We ca