I also feel this decision was a mistake. If there's a consensus to revert, I'm happy to draft a PEP.
Alex On Nov 6, 2017 1:58 PM, "Neil Schemenauer" <nas-pyt...@arctrix.com> wrote: > On 2017-11-06, Nick Coghlan wrote: > > Gah, seven years on from Python 2.7's release, I still get caught by > > that. I'm tempted to propose we reverse that decision and go back to > > enabling them by default :P > > Either enable them by default or make them really easy to enable for > development evironments. I think some setting of the PYTHONWARNINGS > evironment variable should do it. It is not obvious to me how to do > it though. Maybe there should be an environment variable that does > it more directly. E.g. > > PYTHONWARNDEPRECATED=1 > > Another idea is to have venv to turn them on by default or, based on > a command-line option, do it. Or, maybe the unit testing frameworks > should turn on the warnings when they run. > > The current "disabled by default" behavior is obviously not working > very well. I had them turned on for a while and found quite a > number of warnings in what are otherwise high-quality Python > packages. Obviously the vast majority of developers don't have them > turned on. > > Regards, > > Neil > _______________________________________________ > 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 mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
