Hi Brian,
On Fri, 25 Jul 2014, Brian May wrote:
I can't help but think this might be unrealistic (?). Changes required for
new versions of Django often break compatibility with old versions, and
1.4.5 is really old now. Just because many packages don't have versioned
dependencies on Django
Hi Andrew,
thanks for your quick answer.
On Thu, 24 Jul 2014, Andrew Godwin wrote:
There is no way around this; it's unfortunate that the packaging situation
means that Django will get auto-upgraded as part of a distribution upgrade;
I'm surprised that Debian hasn't had this with packages
Not CCing Django-Developers, my emails bounce, possibly because I am not
subscribed. Feel free to repost if you feel it might help.
On 25 July 2014 18:04, Raphael Hertzog hert...@debian.org wrote:
Applications that depend on South and have different upstream versions
in Debian 7 and Debian 8
[ Please keep me in CC ]
Hello,
I'm one of the python-django Debian package maintainers and I have been
working on preparing the field for Django 1.7... and we have one problem
that we don't know how to handle.
Consider that Debian contains Django but also Django applications using
South. When
Normally, in development with south. If the migrations get to the point
were they're out of sync. The lead Dev removed the conflicting migrations
and runs the schema migration command.
As for the django 1.7 flow of migrations, I cannot comment on it, but I
would go into this problem with the
On Thu, Jul 24, 2014 at 4:44 PM, Joseph Curtin 4...@jbcurtin.io wrote:
My question now would be, can django migrations and south migrations
co-exist and can I turn off django migrations?
No, migrations is a required feature of Django and cannot be turned off.
The best you could do is generate
So, South migrations will not work with Django 1.7. Period.
There is no way around this; it's unfortunate that the packaging situation
means that Django will get auto-upgraded as part of a distribution upgrade;
I'm surprised that Debian hasn't had this with packages before? (Version
upgrades that
On 25 July 2014 06:27, Raphael Hertzog raph...@ouaza.com wrote:
How can we solve this problem?
This isn't really a good solution, but the best I can think of right now.
The system administrator for every site does the following:
1. Manually pins python-django to less then 1.7 - can somebody
On 25 July 2014 08:00, Andrew Godwin and...@aeracode.org wrote:
So, South migrations will not work with Django 1.7. Period.
I haven't been able to find an official statement of this, but have had
some trial runs, where this looked very much like it was the case.
Might be possible to hack it
9 matches
Mail list logo
