openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00289
Re: Lazy import of modules
On Fri, Jan 14, 2011 at 11:28 AM, John Purrier <john@xxxxxxxxxxxxx> wrote:
> Another thought, as we envision moving OpenStack forward we will likely be including code and projects that are not written in Python. Being forward looking should we structure openstack-common to segment along language lines?
That wasn't the original intent of openstack-common, but I suppose we
could adapt it. Generally, though, I've found that open source
libraries are separated by language. I don't think I've seen a
packaged open-source library that served two languages. I think for
other languages (especially bindings), it's better to have them in a
separate project that can be packaged according to the customs of that
programming language/platform.
-jay
Follow ups
References
-
Lazy import of modules
From: Ewan Mellor, 2011-01-12
-
Re: Lazy import of modules
From: Ewan Mellor, 2011-01-12
-
Re: Lazy import of modules
From: Jay Pipes, 2011-01-13
-
Re: Lazy import of modules
From: Ewan Mellor, 2011-01-13
-
Re: Lazy import of modules
From: Vishvananda Ishaya, 2011-01-13
-
Re: Lazy import of modules
From: Devin Carlen, 2011-01-13
-
Re: Lazy import of modules
From: Andy Smith, 2011-01-14
-
Re: Lazy import of modules
From: Vishvananda Ishaya, 2011-01-14
-
Re: Lazy import of modules
From: Jay Pipes, 2011-01-14
-
Re: Lazy import of modules
From: John Purrier, 2011-01-14