Revision history [back]
This applies to askbot version 0.7.43. I've looked at the list of backwards incompatible changes in the Django release notes and so far found this:
- Stop using messaging system from
contrib.auth. I suggest to implement an internal system similar to the old style messaging as a temporary solution to speed up the migration. - Eliminate use of
request.raw_post_datain the python code. - Change to using new style Feed in
askbot/feeds.py.
We need to make sure that migrated code still works with Django 1.2.
Please feel free to make pull requests on github, thank you for your help.
This applies to askbot version 0.7.43. I've looked at the list of backwards incompatible changes in the Django release notes and so far found this:
contrib.auth. I suggest to implement an internal system similar to the old style messaging as a temporary solution to speed up the migration.request.raw_post_data in the python code.askbot/feeds.py.We need to make sure that migrated code still works with Django 1.2.
Please feel free to make pull requests on github, thank you for your help.
This applies to askbot version 0.7.43. I've looked at the list of backwards incompatible changes in the Django release notes and so far found this:
Stop using messaging system from contrib.auth. I suggest to implement an internal system similar to the old style messaging as a temporary solution to speed up the migration.
Eliminate use of request.raw_post_data in the python code.
Change to using new style Feed in askbot/feeds.py.
We need to make sure that migrated code still works with Django 1.2.
Please feel free to make pull requests on github, requests, thank you for your help.