On Thu, Jan 29, 2015, at 09:10 PM, liuxinguo wrote:
> * I have seen that the module 'oslo.config' have changed to
> 'oslo_config' in Kilo but in Juno it is still 'oslo.config'.
>
> I want my code work compatibly both for Juno and Kilo so I import this
> module in this way:
>
> try:
>
The requirements files are being updated so this fallback is unnecessary.
Newer versions of the library (which should be the new minimum version)
will work with the first import without issue. The only reason you would
do this is if you’re not following global-requirements.txt and have a very
low m
Suppose that's the way to do it.
On Fri, Jan 30, 2015, 7:44 AM liuxinguo wrote:
> · I have seen that the module ‘oslo.config’ have changed to
> ‘oslo_config’ in Kilo but in Juno it is still ‘oslo.config’.
>
>
>
> I want my code work compatibly both for Juno and Kilo so I import this
>
* I have seen that the module 'oslo.config' have changed to
'oslo_config' in Kilo but in Juno it is still 'oslo.config'.
I want my code work compatibly both for Juno and Kilo so I import this module
in this way:
try:
from oslo_config import cfg
except:
from oslo.config import cfg
*
