I'd like to give you my 2 cents.
On Sat, 2012-03-31 at 08:25 -0700, Michael Boratko wrote:
> That makes sense, thank you for explaining. The only problem is that
> the website instructions to install Django CMS by just typing "pip
> install django-cms" do not work, then.
>
>
> It would be great if pip had a method for supplying multiple bounds on
> requirements, does anyone know if it does? Something like
> 1.2.7<=Django<1.4 would be great. Even better would be something like
> "Django>=1.2.7&&Django<1.4". Anyway, as it stands now, the
> instructions on the website won't work.
PIP (or, better, setuptools) already has this feature. The syntax is:
install_requires=[
...
'django >= 1.2.7, < 1.4',
...
]
However the point #3 that Jonas has pointed out (What if 1.4 just
worked?) remains. And being unable to perform an upgrade that will work
flawless is, in my experience, a very annoying thing.
In my opinion, the best thing django-cms can do to prevent errors
introduced by upgrades is telling people in the documentation to specify
the Django version in the project's setup.py.
Yes, they can with:
pip install django-cms --no-dependencies
(Assuming that all the dependencies were installed previously)
It should be noted that this is a "manual step": with just your
project's setup.py, you can't tell setuptools to ignore django-cms
install requirements.
--
Ubuntu member
http://www.ubuntu.com/