[tahoe-dev] [tahoe-lafs] #859: Starting Tahoe-lafs throws multiple DeprecationWarnings

tahoe-lafs trac at allmydata.org
Fri Jan 29 22:39:37 UTC 2010


#859: Starting Tahoe-lafs throws multiple DeprecationWarnings
--------------------------------------------------------------+-------------
 Reporter:  imhavoc                                           |           Owner:  imhavoc
     Type:  defect                                            |          Status:  new    
 Priority:  minor                                             |       Milestone:  1.6.0  
Component:  code                                              |         Version:  1.5.0  
 Keywords:  DeprecationWarning foolscap nevow usability easy  |   Launchpad_bug:         
--------------------------------------------------------------+-------------
Changes (by zooko):

  * keywords:  DeprecationWarning foolscap nevow usability =>
               DeprecationWarning foolscap nevow usability
               easy
  * milestone:  undecided => 1.6.0


Comment:

 So if Foolscap v0.5.0 gets into Ubuntu 10.04 then that !DeprecationWarning
 will be fixed in 10.04. Here is the issue ticket for Debian requesting
 that Debian upgrade foolscap: http://bugs.debian.org/cgi-
 bin/bugreport.cgi?bug=567145 .

 For Nevow it doesn't look like it is going to get fixed in Nevow trunk, a
 new version of Nevow released, and that new version accepted into Ubuntu
 in time for 10.04, so I think we should suppress the !DeprecationWarning
 in Tahoe-LAFS.  There is sample code to do that in the Nevow ticket:
 http://divmod.org/trac/ticket/2994#comment:15

 To apply this to Tahoe-LAFS you find the line that emits the warning,
 which I assume is {{{import nevow}}}, and wrap it in:

 {{{
 import warnings
 warnings.filterwarnings("ignore", category=DeprecationWarning,
     message="object.__new__\(\) takes no parameters",
     append=True)
 try:
     import nevow
 finally:
     warnings.filters.pop()
 }}}

 Also we should update [source:src/allmydata/test/test_runner.py] to make
 the code-under-test fail if it emits anything to stderr when the
 {{{tahoe}}} command is executed.  (test_runner.py used to do that, but I
 made it stop doing that and allow the code-under-test to pass while
 emitting !DeprecationWarnings. Oh, here is the patch: [20090601225007
 -4233b-0fe172ffe82288a846f7305f47524aaea66f6af6].)

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/859#comment:14>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid


More information about the tahoe-dev mailing list