On Wed, Oct 23, 2013 at 3:26 PM, Robert Collins <robe...@robertcollins.net>wrote:
> On 24 October 2013 08:14, Dolph Mathews <dolph.math...@gmail.com> wrote: > > > > On Wed, Oct 23, 2013 at 1:20 PM, Sean Dague <s...@dague.net> wrote: > > > > > Deprecation warnings! > > > > Based on the approach we're taking in the patch below, we'll be able to > > notate how imminently a feature is facing deprecation. Right now, they're > > just landing in WARNING, but I think we'll surely a desire to silence, > > prioritize or redirect those messages using different log levels (for > > example, based on how imminently a feature is facing deprecation). > > > > https://review.openstack.org/#/c/50486/ > > Huh, I did not see that go by. Python already has built in signalling > for deprecated features; I think we should be using that. We can of > course wrap it with a little sugar to make it easy to encode future > deprecations. > The initial patch used the the warnings modules instead of using the deprecated logging provided by oslo. We talked about it IRC and I switched because there existed a way to do deprecation messaging is olso and it had a configurable way to turn warnings into exceptions. I intend to submit a patch to oslo-incubator based off of the above patch. I'd love to get some feedback about the needs of the other projects. -- David blog: http://www.traceback.org twitter: http://twitter.com/dstanek www: http://dstanek.com
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev