-
Notifications
You must be signed in to change notification settings - Fork 21
WIP: Port to Django 1.9 and use latest version of packages #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Seems there was some renaming in django GenericForeignKey -> GenericRelation managers.py:21 from django.contrib.contenttypes.fields import GenericRelation class ObjectTaskMixin(models.Model): seems to fix that error. But is it correct? Do you also get an error with runserver in settings.py I also get the following when testing: Traceback (most recent call last): Any idea what that is about? |
|
@sueastside Sorry about that. I had changes that fixed those errors locally but didn't push. Just pushed now. |
There is also a
class ObjectTask(models.Model):
"""
"""
task = models.ForeignKey(Task, verbose_name=_('task'), related_name="%(class)s_tasks")
content_type = models.ForeignKey(ContentType,
verbose_name=_('content type'),
related_name="content_type_set_for_%(class)s")
object_pk = models.TextField(_('object ID'))
content_object = GenericForeignKey(ct_field="content_type", fk_field="object_pk")EDIT: It was the functions defined in the |
|
The latest commit fixes the failing test and from the printed output, the tasks seems to be added and removed correctly! |
5e2c4bf to
239b209
Compare
WIP: Port to Django 1.9 and use latest version of packages
Django 1.6 is not supported anymore to the extent that even documentation for that version is not available on the official website. There have been some discussions here about porting to Django 1.9 (Ref: #4 and #8) and this PR takes a stab at it. This PR makes the following major changes:
From the test suite provided there is 1 failing test which I haven't been able to fix. I also suspect that the REST API's might be affected with the change to DRF 3.x, notably due to the removal of nested writable serializers. I will look into the REST API's but I'd appreciate any help with the failing test. This is the traceback obtained.
Regards,
Rohit