Hi,
We use one common package namespace for all our corporate python apps.
And I want to follow this practice for pylons apps too.
But by default pylons uses "flat" package model - one root package for
app.
Of cause I can create my own template (and I done it) but it would be
great to have it out of the box.
And it is interesting for me how to implement it - create separate
template for each
namespace hierarсhy depth level? I mean such variants:
mynamespace.myapp
mynamespace.mysubnamespace.myapp
Has anybody else been concerned with it?
--
Sorry for my language, greetings from Russia.
Andrey
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
