On Tue, Aug 06, 2019 at 07:58:12PM -0700, Nathaniel Smith wrote: > For example, all my projects run tests with deprecation warnings > enabled and warnings turned into errors, but I never saw any of these > warnings. What happens is: the warning is issued when the .py file is > byte-compiled; but at this point, deprecation warnings probably aren't > visible. Later on, when pytest imports the file, it has warnings > enabled... but now the warning isn't issued.
This! If Nathaniel's analysis is correct, and I think it is, we've identified a flaw in our deprecation process. We've assumed that library devs will see the warnings long before end users. Since the benefit of this breaking change is quite small, let's delay it long enough to fix the deprecation process. -- Steven _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/D4BLHVLQL4KR5QGAUMOONVH7MJ4ZMR2L/
