This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients bazwal, berker.peksag, ezio.melotti, lilydjwg, phd, python-dev, serhiy.storchaka, ssokolow
Date 2016-11-03.11:53:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1478174000.56.0.0467828527323.issue23262@psf.upfronthosting.co.za>
In-reply-to
Content
I don't understand with what you disagree. I can imagine old Python 2.7 with old browser, old Python 2.7 with new browser, new Python 2.7 with new browser, and even new Python 2.7 with old browser on the same computer (but the latter is very unlikely).

Old Python 2.7 don't work with new browser and we can't do anything with this. We can make new Python 2.7.12 working with new browser. But I'm not sure that we can break the compatibility with old browser that could be installed when Python 2.7 was first installed on the same computer.
History
Date User Action Args
2016-11-03 11:53:20serhiy.storchakasetrecipients: + serhiy.storchaka, phd, bazwal, ssokolow, ezio.melotti, python-dev, lilydjwg, berker.peksag
2016-11-03 11:53:20serhiy.storchakasetmessageid: <1478174000.56.0.0467828527323.issue23262@psf.upfronthosting.co.za>
2016-11-03 11:53:20serhiy.storchakalinkissue23262 messages
2016-11-03 11:53:20serhiy.storchakacreate