Hard dependencies

[rfleschenberg]

I am creating this issue as a place to discuss how django-shop should specify its hard (non-optional) dependencies.

My suggestion:

1. Follow established Python practice and specify them in setup.py with their minimum versions.
2. Possibly document that we recommend to freeze them with exact versions in a project-wide requirements file.

Hard dependencies that I found so far:

• beautifulsoup4
• django-post-office
• django-filer (requires manual setup, we should point the user at its documentation)
• django-ipware
• django-fsm
• djangorestframework

[vivazzi]

+

[rfleschenberg]

Also:

• django-angular
• django-select2

[jrief]

I agree with django-select2, but django-angular should not be considered a hard dependency.

Well, I have to admit that all Javascript code, some template code and some Cascade plugins require AngularJS, thus django-angular makes perfectly sense as a dependency, but my intention is, to have that part pluggable in case someone want to use Ember, React or any other JS framework.

[rfleschenberg]

I agree that django-angular should not be a hard dependency (in general, the fewer dependencies, the better). But at the moment it is imported in shop/forms/checkout.py, shop/forms/auth.py and shop/forms/base.py. I did not really look at this code yet. Jacob, do you think it would be easily possible to eliminate the dependency or make it optional?

[rfleschenberg]

Closing here. Copied to https://github.com/awesto/django-shop/issues/313.

[rfleschenberg]

This issue was moved to awesto/django-shop#315