Help needed to test packages with Django 1.7
(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 large sample of packages, some maintainers will be MIA and I won't have any answer. So it would be highly appreciated if some people could help process the following bugs so that when Django 1.7 is out we have a good picture of what needs to be done and/or what will possibly have to be (temporarily) removed from testing: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-dja...@packages.debian.org;tag=django17 It would be nice if all packages had a test suite to ensure whether they still work but a large part doesn't even have a python-django build dependency so it's not really the case... What could be done however is mass-rebuild the packages against django 1.7 and mass-tag as confirmed the set of packages which are failing to build with Django 1.7. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140722090523.gb27...@x230-buxy.home.ouaza.com
Re: Help needed to test packages with Django 1.7
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. Only the common package should have this file, from debian/django-admin. If I get a chance, will look at this myself. Currently trying to do too many things at once, this never seems to work well. Thanks
Re: Help needed to test packages with Django 1.7
On 23 July 2014 10:27, Brian May br...@microcomaustralia.com.au 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 following to your sources: deb http://code.vpac.org/debian/ wheezy main This repository contains back ports of some other required packages. And then download and install python-django packages from http://code.vpac.org/debian/experimental/ I haven't yet extensively tested this, although it does install ok. I made one really minor change (and committed to subversion) compared with -2 in experimental, this requires Python 2.7+ (2.6 is not supported any more). -- Brian May br...@microcomaustralia.com.au
Re: Help needed to test packages with Django 1.7
Just testing some of my code against Django 1.7. The first problem was this: Unhandled exception in thread started by function wrapper at 0x2fccc80 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/dist-packages/django/core/management/commands/runserver.py, line 104, in inner_run self.validate(display_num_errors=True) File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line 361, in validate return self.check(app_configs=app_configs, display_num_errors=display_num_errors) File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line 370, in check all_issues = checks.run_checks(app_configs=app_configs, tags=tags) File /usr/lib/python2.7/dist-packages/django/core/checks/registry.py, line 59, in run_checks new_errors = check(app_configs=app_configs) File /usr/lib/python2.7/dist-packages/django/core/checks/model_checks.py, line 16, in check_all_models model.check(**kwargs) TypeError: unbound method check() must be called with ProjectApplication instance as first argument (got nothing instead) Turns out that is because I have a model function called check(), which must now be renamed. This is documented in the Django 1.7 release notes. https://docs.djangoproject.com/en/dev/releases/1.7/ The biggest and most scary change IMHO, is libraries that ship with django-south migrations. I have at least one library that does this (django-simple-captcha, currently stuck in NEW). I think django-south still works with Django 1.7 (), but is considered depreciated compared with the Django 1.7 built in migrations. The problem being that the newer migration mechanism is not compatible with the previous mechanism. How we deal with this probably will require more consideration here. This seems to be a really good blog post on the issue: http://treyhunner.com/2014/03/migrating-to-django-1-dot-7/ - where Trey recommends renaming the existing migrations directory to south_migrations, and setting SOUTH_MIGRATION_MODULES. Which is unfortunate, it means the decision has to be made in the library, but the SOUTH_MIGRATION_MODULES has to be set in the application. -- Brian May br...@microcomaustralia.com.au
