On 07:55 pm, [email protected] wrote: > >On Sep 5, 2012, at 12:11 PM, [email protected] wrote: >>On 06:41 pm, [email protected] 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:" > >A note for posterity - if we are ever to implement a generalized 'run >an inferior twistd process', or even 'run an inferior python >interpreter' mechanism, warning information like this is one of the >bits of runtime state that ought to be communicated.
It would be nice if Python preserved its own command-line arguments somewhere, but it doesn't seem to. :/ So figuring out what the runtime state is is somewhat non-trivial in this case. Otherwise, I completely agree. Jean-Paul >-glyph >_______________________________________________ >Twisted-Python mailing list >[email protected] >http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python _______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
