Hi barry,
Thanks for your answer.
On 09/06/2014 05:38 AM, Barry Warsaw wrote:
> On Sep 05, 2014, at 11:16 PM, Thomas Goirand wrote:
>
>> Surprisingly, when I just do (as root):
>>
>> echo "" >/usr/lib/python3/dist-packages/oslo/__init__.py
>>
>> then everything works again, and subunit under Pyt
On Sep 05, 2014, at 11:16 PM, Thomas Goirand wrote:
>Surprisingly, when I just do (as root):
>
>echo "" >/usr/lib/python3/dist-packages/oslo/__init__.py
>
>then everything works again, and subunit under Python3.4 can find the
>local version of oslo.serialization.
Is there by any chance a /usr/lib
On Sep 05, 2014, at 11:28 AM, Paul Tagliamonte wrote:
>Empty init is totally valid - http://legacy.python.org/dev/peps/pep-0420/
Right, but just to be clear, as you noted the presence of *any* __init__.py
regardless of contents, makes it a "regular" (i.e. concrete) package instead
of a namespace
On Fri, Sep 05, 2014 at 11:16:53PM +0800, Thomas Goirand wrote:
> But in Python 3.4, there's no such a file. While this doesn't seem to be
> a problem with the packages once installed, it is breaking unit tests.
> For example, building python-oslo.serialization and running the unit
> tests, I get:
Hi,
It took me a long time to figure out what was going on, but now I think
I get it. Let me explain my issue.
In OpenStack, there's lots of modules sharing the same "oslo" namespace.
Here's the list of what's currently in Debian:
- python-oslo.config
- python-oslo.messaging
- python-oslo.rootwr
5 matches
Mail list logo
