[openstack-dev] [mistral] Using __init__.py files

Oleg Gelbukh ogelbukh at mirantis.com
Mon Jun 30 12:26:10 UTC 2014


Renat,

As far as I can tell, it is de-facto standard to not place anything at all
to __init__.py across the majority of OpenStack projects.

--
Best regards,
Oleg Gelbukh


On Mon, Jun 30, 2014 at 3:50 PM, Renat Akhmerov <rakhmerov at mirantis.com>
wrote:

> Hi,
>
> What would be your opinion on the question “Should we place any important
> functionality into __init__.py files or just use it for package level
> initialization and exporting variables from module level to a package
> level?”.
>
> I personally would prefer not to keep there anything like class Engine
> (which is one of the most important parts of Mistral now). It’s somewhat
> confusing to me, especially when I navigate through the project structure.
> It’s not a critical urgent thing, of course, but would be nice if you share
> your opinion.
>
> What do you guys think?
>
> Renat Akhmerov
> @ Mirantis Inc.
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140630/ff8d92f5/attachment.html>


More information about the OpenStack-dev mailing list