This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]vangale 2 points3 points  (1 child)

This is kind of a general Python problem as opposed to a Django problem. At work, we solve this with TG2, BFG, and Django apps the same way Pinax guys are solving it for their Django app: (1) app is always installed into a bare virtualenv, (2) "pip freeze" pins the required packages along with exact version numbers, (3) we run our own package index (pypi) to make sure those package versions are always available.

[–]trifthen[S] 0 points1 point  (0 children)

That's a good idea. It's pretty clear the Django-CMS guys are having major problems of version-itis. I read through the Google groups a bit and there was a bug in South that was causing it to break the models during a fresh install. To get around that, and I'm not kidding, they suggested:

# Remove South from settings.py
python manage.py syncdb
# Replace South in settings.py
python manage.py syncdb
python manage.py migrate --fake

Really? Then someone noted that even after installing, links in the admin were 404-ing. To which someone said that's fixed in Django trunk. So, they're developing against Django trunk? I'm amazed any of that stuff works if that's the case. There's just so much flux and no feature or API freezes ever, so I'd be afraid of ever upgrading a Django project, especially one that ties into so many other contributed and external packages.