SET_NULL in fiber/models.py makes fiber incompatible with Django 1.2.x

[django-fiber]

SET_NULL in fiber/models.py makes fiber incompatible with Django 1.2.x

[dbunskoek]

Can you send me the exact error you get? I investigated it for a little bit, and I found that ForeignKey.on_delete was introduced in 1.3, but you seem to be getting an error with regards to models.SET_NULL? Maybe we should do something like this: http://djangosnippets.org/snippets/1231/ ?

[tremmert]

I think that snippet you provided sounds like a possible idea...

Here is my error:

/Users/tremmert/Development/Envs/epsilon-current/bin/python manage.py runserver 8000
Traceback (most recent call last):
File "manage.py", line 11, in
execute_manager(settings)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/core/management/init.py", line 438, in execute_manager
utility.execute()
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/core/management/init.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(_args, *_options.dict)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/core/management/base.py", line 219, in execute
self.validate()
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/core/management/base.py", line 249, in validate
num_errors = get_validation_errors(s, app)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/core/management/validation.py", line 35, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/db/models/loading.py", line 146, in get_app_errors
self._populate()
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/db/models/loading.py", line 61, in populate
self.load_app(app_name, True)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/db/models/loading.py", line 78, in load_app
models = import_module('.models', app_name)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
import(name)
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/fiber/models.py", line 65, in
class Page(MPTTModel):
File "/Users/tremmert/Development/Envs/epsilon-current/lib/python2.7/site-packages/fiber/models.py", line 72, in Page
redirect_page = models.ForeignKey('self', null=True, blank=True, related_name='redirected_pages', verbose_name=('redirect page'), on_delete=models.SET_NULL)
AttributeError: 'module' object has no attribute 'SET_NULL'

Process finished with exit code 1

[dbunskoek]

Have you already upgraded to Django 1.3 (or 1.4 even)? We're currently debating how we should handle backwards compatibility. My current feeling is that people who don't upgrade from Django 1.2 probably won't mind running an older version of Django Fiber, or am I wrong? Can you, or anyone else, convince me otherwise? Are there any statistics of Django versions that are currently in use around the globe? I mean something like this for Google Chrome:

[mvdwaeter]

Django-fiber doesn't support Django==1.2 anymore. You can still use an older version of Fiber, although this is not recommended. Also use of Django==1.2 is not recommended.

To transition your project from Django==1.2 to Django==1.3.1 see the release notes:
https://docs.djangoproject.com/en/1.3/releases/1.3/

However, an update to Django==1.4 is recommended best!

To transition your project from Django==1.3.x to Django==1.4 see the release notes:
https://docs.djangoproject.com/en/1.4/releases/1.4/