[tahoe-lafs-trac-stream] [tahoe-lafs] #1741: consider suppressing all DeprecationWarnings (and maybe RuntimeWarnings and UserWarnings?)

[tahoe-lafs]

#1741: consider suppressing all DeprecationWarnings (and maybe RuntimeWarnings and
UserWarnings?)
----------------------------+---------------------------------------
     Reporter:  davidsarah  |      Owner:  davidsarah
         Type:  defect      |     Status:  assigned
     Priority:  normal      |  Milestone:  1.10.0
    Component:  code        |    Version:  1.9.1
   Resolution:              |   Keywords:  deprecation warning error
Launchpad Bug:              |
----------------------------+---------------------------------------

Comment (by davidsarah):

 What I was thinking was that we could display unexpected warnings
 (captured using
 [http://docs.python.org/library/logging.html#logging.captureWarnings
 logging.captureWarnings] in a test that gets run last. That would mean
 that previous tests will have imported or exercised any code that would
 have caused a warning, whereas a standalone command option wouldn't
 necessarily do that. Then the definition of which warnings are expected
 would go just in that test, rather than being used by
 [source:src/allmydata/__init__.py].

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1741#comment:6>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage