[Twisted-Python] Getting deprecation warnings?
Laurens Van Houtven
_ at lvh.cc
Wed Sep 5 17:50:41 EDT 2012
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
On Wed, Sep 5, 2012 at 9:11 PM, <exarkun at twistedmatrix.com> wrote:
> On 06:41 pm, _ at lvh.cc wrote:
> >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:"
> >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
> >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
> >which wasn't being tested, but the not being tested part is now fixed.)
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Twisted-Python