On Fri, Apr 1, 2011 at 12:35 AM, Patryk Zawadzki wrote:
> Hi group,
>
> Currently Django has its own concept of namespacing (apps) and mostly
> ignores Python modules. I'd like to propose using Python paths
> wherever we can instead of apps. This would solve a lot of problems
> with conflicting su
On Fri, Apr 1, 2011 at 12:01 AM, Luke Plant wrote:
> On 31/03/11 19:35, Patryk Zawadzki wrote:
>> * for 1.4 provide a number of fallback settings that can be used to
>> enable legacy behavior in each of the first three points
> but this is where it falls down, because the devil is in the details
On 31/03/11 19:35, Patryk Zawadzki wrote:
> I propose the following:
> * make the internal model handling operate on full paths to the
> classes, rather than just the app names and class names
> * make the DB table names use full python paths instead of just the
> app name and the class name
>
Hi group,
Currently Django has its own concept of namespacing (apps) and mostly
ignores Python modules. I'd like to propose using Python paths
wherever we can instead of apps. This would solve a lot of problems
with conflicting submodule names that plague maintainers of reusable
apps and framework
