Panos Laganakos wrote:
This post[1] seems to have the same issue. Ticket 6063, which was fixed at rev.6895.Problem is that the whole project is written for 0.96.1. Any way this can be fixed in 0.96.1?
My guess is that you'd have to backport the patch yourself.This is one of the reasons that using the latest trunk is the fact that you get the bugfixes and features. 0.96 will only get security updates, hence the 0.96.1 release.
I'd recommend that you go ahead and forwardport your whole project to the latest svn revision. The latest development version is much closer to 1.0 than 0.96 is. Forward porting django apps developed for 0.96 to the latest svn version is actually much easier than I thought it would be. This is because the devs have done a magnificent job of documenting the backwards incompatible changes.
Either way, you're going to end up refactoring either your project or the patch. If you backport the patch, you'd be stuck running a custom patched version of django.
Good luck! Jeff Anderson
signature.asc
Description: OpenPGP digital signature
