Huh. I have complete unit test coverage and was using trial, but somehow I managed to miss that... I guess I will have to pay more attention or something?! I will try to recreate a situation where the warnings should pop up.
Thanks! On Wed, Sep 5, 2012 at 9:11 PM, <exar...@twistedmatrix.com> wrote: > On 06:41 pm, _...@lvh.cc wrote: > >Hey, > > > >What is the appropriate way to run twistd apps in such a way that I get > >nice and loud deprecation warnings? > > 1) Have complete unit test coverage and run your tests with trial. All > deprecation warnings will be written out as part of the test suite run. > > 2) Run twistd with Python 2.6 > > 3) Run twistd with Python 2.7 and pass "-W::DeprecationWarning:" > > Jean-Paul > >I ran into an issue with one of my apps with the new release because > >t.w.error.NoResource is now t.w.resource.NoResource, I would like to > >make > >my code as forward compatible as possible as we go along, of course :) > > > >(Actually this issue was because I stole some non-released code from > >#4173, > >which wasn't being tested, but the not being tested part is now fixed.) > > > >-- > >cheers > >lvh > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > -- cheers lvh
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
