Your message dated Tue, 29 Jul 2014 09:58:03 +1000
with message-id
<CAA0ZO6C2S_vvQr6OHN8UrAE2rE7nO6PU1=k9Ez_1Fq=ma2d...@mail.gmail.com>
and subject line Re: [Python-modules-team] Bug#755644: python-django-jsonfield:
Please ensure it works with Django 1.7
has caused the Debian Bug report #755644,
regarding python-django-jsonfield: Please ensure it works with Django 1.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
755644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755644
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-django-jsonfield
Version: 0.9.13-1
Severity: important
User: [email protected]
Usertags: django17
Hello,
your package python-django-jsonfield depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7
We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.
Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.
If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.
If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django
[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.
Thank you for your help!
PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
On 29 July 2014 01:58, Raphael Hertzog <[email protected]> wrote:
> You probably just need a single call to django.setup() at the start of the
> test file, just like the wsgi change that was needed in #755638.
>
Unless I am rather confused, it appears to do that already:
if getattr(django, 'setup', None):
django.setup()
Oh, crap, just noticed I somehow managed to test version 0.9.12; 0.9.13 is
in unstable, and that I believe is fine. 0.9.12 only exists in Debian
backports.
Closing this bug, 0.9.13 seems to be fine.
--
Brian May <[email protected]>
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
