Also note that the following is supposed to be true (or should be?):
From: https://docs.python.org/2/library/warnings.html#warning-categories
>>> DeprecationWarning: Base category for warnings about deprecated
>>> features (ignored by default).
>>> Changed in version 2.7: DeprecationWarning is ignored by default.
So by default these should be off/ignored:
Now projects can change that as they wish (and maybe we should have it
be set to 'once' during development, and 'ignore' at release?), where
these levels are at:
https://docs.python.org/2/library/warnings.html#the-warnings-filter
I believe I put the 'once' into cinder code:
https://github.com/openstack/cinder/blob/master/cinder/cmd/all.py#L34
But feel free to change it (this seems like it should be something
consistent across projects)...
-Josh
John Griffith wrote:
On Thu, Mar 12, 2015 at 10:48 AM, Doug Hellmann <d...@doughellmann.com
<mailto:d...@doughellmann.com>> wrote:
On Thu, Mar 12, 2015, at 05:24 AM, Duncan Thomas wrote:
> ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync
> /usr/local/lib/python2.7/dist-packages/oslo_db/_i18n.py:19:
> DeprecationWarning: The oslo namespace package is deprecated.
Please use
> oslo_i18n instead.
> from oslo import i18n
> /opt/stack/cinder/cinder/openstack/common/policy.py:98:
> DeprecationWarning:
> The oslo namespace package is deprecated. Please use oslo_config
instead.
> from oslo.config import cfg
> /opt/stack/cinder/cinder/openstack/common/policy.py:99:
> DeprecationWarning:
> The oslo namespace package is deprecated. Please use
oslo_serialization
> instead.
> from oslo.serialization import jsonutils
> /opt/stack/cinder/cinder/objects/base.py:25: DeprecationWarning:
The oslo
> namespace package is deprecated. Please use oslo_messaging instead.
> from oslo import messaging
>
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/openstack/common/fileutils.py:22:
> DeprecationWarning: The oslo namespace package is deprecated.
Please use
> oslo_utils instead.
> from oslo.utils import excutils
>
Yay, the system is working as designed!
Oslo "froze" early to prepare releases to integrate with the downstream
projects. You found an issue and reported it. Dims and others worked on
patches, and we're releasing new versions. All before your feature
freeze, so you can adopt them.
>
> What are normal, none developer users supposed to do with such
warnings,
> other than:
> a) panic or b) Assume openstack is beta quality and then panic
Next time, please try to be less snide. It makes it difficult to take
you seriously.
Doug
>
> --
> Duncan Thomas
>
__________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Very cool!! I think there may have been some misunderstanding here on
how this would all shake out, but yes as Doug and Dims pointed out this
worked great. Thanks everyone!!
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
