On Sun, Oct 19, 2008 at 1:55 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
> However, it's important to note that this doesn't preclude the use of
> deeper namespaces - it just says that namespacing for an application
> shouldn't be tied to the project. One obvious way to satisfy this
> would
On Sun, Oct 19, 2008 at 5:53 AM, Dana <[EMAIL PROTECTED]> wrote:
>
> Hello everyone,
>
> I am working on a CMS that includes a bunch of applications (like
> Story, Event, etc...) with some being propriatary and some being third
> party. When it comes to our naming conventions, we've had a bit of
>
I think there are two issues at play here:
1. Separate your site or application into multiple Python projects to
promote re-usability, maintainability, extensibility.
2. Place your packages within a top-level package to prevent
namespace collisions to increase re-usability.
Note there is a di
Hello everyone,
I am working on a CMS that includes a bunch of applications (like
Story, Event, etc...) with some being propriatary and some being third
party. When it comes to our naming conventions, we've had a bit of
discussion over namespace issues. Now I have been referencing James
Bennett's
4 matches
Mail list logo
