django-positions - Project Hosting on Google Code

Project Home		Issues

Earlier this year Aug 07, 2009 issue 6 (please use transaction.commit_unless_managed()) changed by jpwatts - I added this in the latest changeset: http://github.com/jpwatts/django-positions/commit/c44877c9f26b4b285021ed29ef594fcdcf372cad Thanks for pointing this out; the docs make it pretty clear that I was doing it wrong. Status: Fixed Owner: jpwatts I added this in the latest changeset: http://github.com/jpwatts/django-positions/commit/c44877c9f26b4b285021ed29ef594fcdcf372cad Thanks for pointing this out; the docs make it pretty clear that I was doing it wrong. Status: Fixed Owner: jpwatts Aug 06, 2009 issue 6 (please use transaction.commit_unless_managed()) reported by igor.bernstein - As per http://docs.djangoproject.com/en/dev/topics/db/sql/ This plugin's updates are never committed to the database if user isn't using transaction decorators. As per http://docs.djangoproject.com/en/dev/topics/db/sql/ This plugin's updates are never committed to the database if user isn't using transaction decorators. Older Dec 16, 2008 issue 5 (TypeError: __init__() got an unexpected keyword argument 'un...) Status changed by jpwatts - Status: Invalid Status: Invalid Dec 16, 2008 issue 5 (TypeError: __init__() got an unexpected keyword argument 'un...) commented on by davidgrant - Sorry, please close this. On one of my models I still has PositiveIntegerField instead of PositionField and that's what caused this. Sorry, please close this. On one of my models I still has PositiveIntegerField instead of PositionField and that's what caused this. Dec 16, 2008 issue 5 (TypeError: __init__() got an unexpected keyword argument 'un...) reported by davidgrant - What steps will reproduce the problem? 1. python manage.py sqlall <app name> (where app is an app that uses PositionField and unique_for_field) 2. TypeError: __init__() got an unexpected keyword argument 'unique_for_field' What is the expected output? What do you see instead? -Expected it to not break. What version of the product are you using? On what operating system? -svn HEAD in Django 1.0.x branch What steps will reproduce the problem? 1. python manage.py sqlall <app name> (where app is an app that uses PositionField and unique_for_field) 2. TypeError: __init__() got an unexpected keyword argument 'unique_for_field' What is the expected output? What do you see instead? -Expected it to not break. What version of the product are you using? On what operating system? -svn HEAD in Django 1.0.x branch Aug 13, 2008 issue 4 (Django-positions fails with the development version of Djang...) commented on by djtequila - That was commendably fast work. Many thanks! That was commendably fast work. Many thanks! Aug 12, 2008 issue 4 (Django-positions fails with the development version of Djang...) Status changed by jpwatts - The fix is in r13. Thanks for the report. Status: Fixed The fix is in r13. Thanks for the report. Status: Fixed Aug 12, 2008 r13 (Fixed incompatibility with Django's signal refactor. http:/...) committed by jpwatts - Fixed incompatibility with Django's signal refactor. http://code.djangoproject.com/changeset/8223 Fixed incompatibility with Django's signal refactor. http://code.djangoproject.com/changeset/8223 Aug 12, 2008 issue 4 (Django-positions fails with the development version of Djang...) Owner changed by jpwatts - Owner: jpwatts Owner: jpwatts Aug 12, 2008 issue 4 (Django-positions fails with the development version of Djang...) changed by jpwatts - Status: Accepted Labels: Priority-Critical −Priority-Medium Status: Accepted Labels: Priority-Critical −Priority-Medium Aug 12, 2008 issue 4 (Django-positions fails with the development version of Djang...) reported by djtequila - What steps will reproduce the problem? 1. Download the latest development version of Django 2. Create a simple project, including a model using django-positions. 3. Try to do a 'syncdb' from manage.py What is the expected output? What do you see instead? Expected: The database should be created. Experienced: 'module' has no method 'connect' What version of the product are you using? On what operating system? Latest development version of Django, experienced on Windows XP and Mac OSX. Please provide any additional information below. The problem seems to be the following lines: dispatcher.connect(self._on_delete, sender=cls, signal=post_delete) dispatcher.connect(self._on_save, sender=cls, signal=post_save) dispatcher.connect is deprecated. using Signal.connect (post_delete.connect I guess) is apparently the new way, but the sender must be able to receive kwargs. Which it doesn't. What steps will reproduce the problem? 1. Download the latest development version of Django 2. Create a simple project, including a model using django-positions. 3. Try to do a 'syncdb' from manage.py What is the expected output? What do you see instead? Expected: The database should be created. Experienced: 'module' has no method 'connect' What version of the product are you using? On what operating system? Latest development version of Django, experienced on Windows XP and Mac OSX. Please provide any additional information below. The problem seems to be the following lines: dispatcher.connect(self._on_delete, sender=cls, signal=post_delete) dispatcher.connect(self._on_save, sender=cls, signal=post_save) dispatcher.connect is deprecated. using Signal.connect (post_delete.connect I guess) is apparently the new way, but the sender must be able to receive kwargs. Which it doesn't.

issue 4 (Django-positions fails with the development version of Djang...) reported by djtequila - What steps will reproduce the problem? 1. Download the latest development version of Django 2. Create a simple project, including a model using django-positions. 3. Try to do a 'syncdb' from manage.py What is the expected output? What do you see instead? Expected: The database should be created. Experienced: 'module' has no method 'connect' What version of the product are you using? On what operating system? Latest development version of Django, experienced on Windows XP and Mac OSX. Please provide any additional information below. The problem seems to be the following lines: dispatcher.connect(self._on_delete, sender=cls, signal=post_delete) dispatcher.connect(self._on_save, sender=cls, signal=post_save) dispatcher.connect is deprecated. using Signal.connect (post_delete.connect I guess) is apparently the new way, but the sender must be able to receive **kwargs. Which it doesn't.

What steps will reproduce the problem? 1. Download the latest development version of Django 2. Create a simple project, including a model using django-positions. 3. Try to do a 'syncdb' from manage.py What is the expected output? What do you see instead? Expected: The database should be created. Experienced: 'module' has no method 'connect' What version of the product are you using? On what operating system? Latest development version of Django, experienced on Windows XP and Mac OSX. Please provide any additional information below. The problem seems to be the following lines: dispatcher.connect(self._on_delete, sender=cls, signal=post_delete) dispatcher.connect(self._on_save, sender=cls, signal=post_save) dispatcher.connect is deprecated. using Signal.connect (post_delete.connect I guess) is apparently the new way, but the sender must be able to receive **kwargs. Which it doesn't.

Earlier this year

Older