Should setup.py have a dependency on Django?

[jazzband]

Should setup.py have a dependency on Django?

[jezdez]

Hm, in the past I've not done that simply because people may not have made the jump from one minior Django version to the next. So for example if we'd have a 1.6 project on 1.6.3 and specify something like "Django>=1.6" in the setup.py then pip would not know which version to use, the major version installed right now or update to 1.7?

Anecdotally all of the projects I've worked on in past years had a requirements.txt that specified the base packages to be used by the project including Django and an exact version. That limited surprises and made us upgrade when we had the time to do proper testing. Additionally I would assume the pseudo namespace of the _django-_formtools package implies that it's supposed to be used with a Django release. I would not leave the specification which minimal version of Django to use to the package manager.

[gchp]

If formtools is going to only be supported for certain versions of Django, then should the version specifier be Django>=MIN_SUPPORTED_DJANGO_VERISON? That way, when it is installed it will always get a compatible version of Django, but users can always use their own requirements file or whatever to pin the versions. At least like this if I already have a version of Django installed which meets the MIN_SUPPORTED_DJANGO_VERSION, it won't need to install anything and won't cause problems.