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 r.david.murray
Recipients dstufft, gvanrossum, hawkowl, ncoghlan, r.david.murray, serhiy.storchaka
Date 2017-10-10.13:19:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507641578.95.0.213398074469.issue31742@psf.upfronthosting.co.za>
In-reply-to
Content
Nick says: "Neither of those situations can be encountered simply by running an existing *application* on a newer version of Python". 

I fail to see the operational difference between running an application on a newer version of Python and doing a pip --upgrade or yum update and then running the application.  So that argument boils down to "this warning should be on by default", which is what we are discussing :)

I'm happy to leave this to the PEP process.
History
Date User Action Args
2017-10-10 13:19:38r.david.murraysetrecipients: + r.david.murray, gvanrossum, ncoghlan, serhiy.storchaka, dstufft, hawkowl
2017-10-10 13:19:38r.david.murraysetmessageid: <1507641578.95.0.213398074469.issue31742@psf.upfronthosting.co.za>
2017-10-10 13:19:38r.david.murraylinkissue31742 messages
2017-10-10 13:19:38r.david.murraycreate