RetroSearch Browse

Sun Jun 22 01:10:41 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-June/135147.html

On Sun, Jun 22, 2014 at 8:00 AM, Steve Dower <Steve.Dower at microsoft.com> wrote:
> We can always lie about the version in sys.version. Existing code is
> unaffected and new code will have to use version_info (Windows developers
> will know that Windows pulls tricks like this every other version... doesn't
> make it a great idea, but it works).

I'd prefer a change of format to an outright lie. Something like
"2.7._10" which will sort after "2.7.9". But ideally, nothing at all -
just go smoothly to "2.7.10" and let broken code be broken. It'll
think it's running on 2.7.1, and if anything needs to distinguish
between 2.7.1 and 2.7.x, hopefully it's using version_info.

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-June/135147.html below:

[Python-Dev] Python 2.7 patch levels turning two digit