(Please cc me as I'm not subscribed)
Hello,
I have filed 85 bugs against all reverse-deps of python-django
to ask their maintainers to ensure that their packages works well
with Django 1.7 (1). A good chunk of those are maintained or co-maintained
by the Python Modules team, and as usual in a lar
Hello,
Thanks for you work. I very much agree, would really like to see Django 1.7
in Jessie, even if it does break some things along the way.
Something seems to have gone wrong with your package.
Both python-django and python3-django include
/usr/bin/django-admin
...and as a result conflict.
On 23 July 2014 10:27, Brian May wrote:
> Something seems to have gone wrong with your package.
>
Looks like you already fixed it in -2.
I have back ported this to wheezy.
In case anybody wants to use it, and actually trusts me (why would anybody
trust me?), you can use at by adding the follow
Just testing some of my code against Django 1.7.
The first problem was this:
Unhandled exception in thread started by
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/django/utils/autoreload.py", line
221, in wrapper
fn(*args, **kwargs)
File
"/usr/lib/python2.7/d
On 23 July 2014 12:54, Brian May wrote:
> I think django-south still works with Django 1.7 (), but is considered
> depreciated compared with the Django 1.7 built in migrations.
>
I was wrong. django-south will not work with 1.7, and quite possibly never
will work with Django 1.7 - I haven't
Hi,
On Wed, 23 Jul 2014, Brian May wrote:
> Attempt to summarize the problem: You want to make sure Django 1.7 is never
> installed if there are any apps with Django south migrations that haven't
> been run, and if Django 1.7 is installed you want to make sure django-south
> is not in INSTALLED_AP
6 matches
Mail list logo
