+5
-5
lines changedFilter options
+5
-5
lines changed Original file line number Diff line number Diff line change
@@ -290,11 +290,11 @@ deprecation warnings. Most notably:
290 290
all warnings emitted *by* a particular dependency prior to upgrading it
291 291
(the third-party ``warn`` module [3_] does provide this, but enabling it
292 292
involves monkeypatching the standard library's ``warnings`` module).
293 -
* Re-enabling deprecation warnings by default in ``__main__`` doesn't help in
294 -
handling cases where software has been factored out into support modules, but
295 -
those modules still have little or no automated test coverage. Near term, the
296 -
best currently available answer is to run such applications with
297 -
``PYTHONWARNINGS=default::DeprecationWarning`` or
293 +
* When software has been factored out into support modules, but those modules
294 +
have little or no automated test coverage, re-enabling deprecation warnings
295 +
by default in ``__main__`` isn't likely to help find API compatibility
296 +
problems. Near term, the best currently available answer is to run affected
297 +
applications with ``PYTHONWARNINGS=default::DeprecationWarning`` or
298 298
``python -W default::DeprecationWarning`` and pay attention to their
299 299
``stderr`` output. Longer term, this is really a question for researchers
300 300
working on static analysis of Python code: how to reliably find usage of
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4