If the layout change was 1.4 that means it was 3 versions ago (1.4, 1.5 and
1.6) and given that 1.4 is the LTS, there is no supported version which had
that as the default layout.
On 4 January 2014 23:14, Curtis Maloney wrote:
> I submitted a patch some time ago to
I submitted a patch some time ago to do a small part of this, on models,
but it was rejected...
As a long time loather of overlapping import paths, I'm with Florian on
this one :)
[Oh, and the layout change was 1.4, not 1.3 :) ]
On 5 January 2014 09:24, Florian Apolloner
Kill double imports with fire :þ (and now)
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this
Personally, I'd do it straight away. The updated project layout has been
around 2 (3?) versions already, and I believe that at least a number of
large older codebases have already been reworked on this basis.
On 4 January 2014 20:31, Aymeric Augustin <
Until Django 1.3 introduced the current project layout, every Django project
was vulnerable to double import problems: since PYTHONPATH contained both a
directory and its parent, the same module could get imported twice through
For more information on why this is a
I've been working on making django-mssql support the schema migration
changes that will be part of Django 1.7 and have a pull request  that is
mostly complete. Before I continue down my current path, I'd like to
solicit some feedback to help ensure my changes will get merged.
I am currently