Re: [python-committers] Python 4.0 or Python 3.10?
On Thu, Sep 27, 2018 at 2:19 PM Brett Cannon wrote: > > Since there isn't a way to do this in any fashion I never really thought > about it. I think most people either set the shebang to the version of Python > they want it to work with, have pip install the entry point which will also > set the entry point, or assume that e.g. python3 is new enough to work. > > But even setting a minimum is potentially troublesome if there's an > incompatibility, e.g. you used 'async' as a variable name and suddenly you > installed Python 3.7. :) So I don't know if the desire/utility of having a > minimum is worth the added complexity. I agree. Yury ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Python 4.0 or Python 3.10?
Since there isn't a way to do this in any fashion I never really thought about it. I think most people either set the shebang to the version of Python they want it to work with, have pip install the entry point which will also set the entry point, or assume that e.g. python3 is new enough to work. But even setting a minimum is potentially troublesome if there's an incompatibility, e.g. you used 'async' as a variable name and suddenly you installed Python 3.7. :) So I don't know if the desire/utility of having a minimum is worth the added complexity. On Wed, 26 Sep 2018 at 10:54, Yury Selivanov wrote: > On Wed, Sep 26, 2018 at 1:25 PM Paul Moore wrote: > [..] > > but I don't know how > > useful it would be in practice - can you give some examples of use > > cases?) > > It's hard to give a real life example as "py" doesn't support this, > but I can imagine the following scenario: if I have a script that uses > some new 3.6 feature I could probably run it from other scripts with > 'py --min=3.6 myscript.py'. That way I wouldn't need to write more > code or use other tools to check if the target system has a Python > 3.6+ interpreter. > > Yury > ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] [RELEASE] Python 3.7.1rc1 and 3.6.7rc1 now available for testing
Python 3.7.1rc1 and 3.6.7rc1 are now available. 3.7.1rc1 is the release preview of the first maintenance release of Python 3.7, the latest feature release of Python. 3.6.7rc1 is the release preview of the next maintenance release of Python 3.6, the previous feature release of Python. Assuming no critical problems are found prior to 2018-10-06, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.1 and 3.6.7. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find these releases and more information here: https://www.python.org/downloads/release/python-371rc1/ https://www.python.org/downloads/release/python-367rc1/ -- Ned Deily n...@python.org -- [] ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
