Last modified: 2014-11-14 05:04:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72970, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70970 - use DeprecationWarning system
use DeprecationWarning system
Status: NEW
Product: Pywikibot
Classification: Unclassified
General (Other open bugs)
core-(2.0)
All All
: High major
: ---
Assigned To: Pywikipedia bugs
:
Depends on:
Blocks: pwb20
  Show dependency treegraph
 
Reported: 2014-09-17 22:34 UTC by John Mark Vandenberg
Modified: 2014-11-14 05:04 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description John Mark Vandenberg 2014-09-17 22:34:07 UTC
pywikibot includes a lot of deprecation methods and parameters to support old code.  The deprecation messages are logged using the normal python logging system, but are not routed through warnings.DeprecationWarning, which allows command line control over whether they are displayed (and defaults to not being displayed)

https://docs.python.org/2/library/warnings.html#warnings.warn
Comment 1 John Mark Vandenberg 2014-11-09 20:05:34 UTC
The deprecation notices are too noisy - users with custom scripts get scared when their screen is full of repetitive warnings.
Comment 2 Sorawee Porncharoenwase 2014-11-14 05:04:55 UTC
For me, I prefer to see repetitive warnings which indicate that I should fix my script. Also, I strongly disagree that warning should not be displayed by default. The purpose of warning is to let users know explicitly. If something needs not to show to users, then switch to .debug instead (which will only show in verbose mode).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links