➜

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 Anthony Sottile, BTaskaya, barry, brett.cannon, eric.smith, gousaiyang, gvanrossum, levkivskyi, lukasz.langa, methane, miss-islington, pablogsal, serhiy.storchaka, steven.daprano, terry.reedy, veky
Date 2021-10-17.07:28:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1634455716.92.0.937706635176.issue38605@roundup.psfhosted.org>
In-reply-to
Content 
I think it would help if we could enable some future feature globally by command line option or environment variable, without modifying all source files. It would allow users to quickly test their code base for compatibility with future changes. The problem currently is that nobody bothers to add "from __future__ import ...", so we have surprises every time when try to make it by default.

A tool which automatically adds or removes "from __future__ import ..." in files could help too.
History
Date User Action Args
2021-10-17 07:28:36serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, barry, brett.cannon, terry.reedy, eric.smith, steven.daprano, methane, lukasz.langa, veky, levkivskyi, Anthony Sottile, pablogsal, miss-islington, BTaskaya, gousaiyang
2021-10-17 07:28:36serhiy.storchakasetmessageid: <1634455716.92.0.937706635176.issue38605@roundup.psfhosted.org>
2021-10-17 07:28:36serhiy.storchakalinkissue38605 messages
2021-10-17 07:28:36serhiy.storchakacreate