Skip to content

Conversation

ziemenz
Copy link

@ziemenz ziemenz commented Jan 19, 2016

No description provided.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This breaks the installer if Django is not yet installed (so for a fresh install of all your requirements for instance).

Since setup.py is used to install, and it imports newsletter, it will crash on the django import.

I have fixed this for django-choices the following way: bigjason/django-choices@b95612e

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is easily unit testable with tox as well where you don't pin a certain Django version in your tox requirements, and let newsletter pull in Django itself.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the detected error

@dokterbob
Copy link
Collaborator

What exactly is the advantage of setting the version number in this fashion?

@dokterbob
Copy link
Collaborator

No reply to my enquiry, I'm closing this one. Should you be able to tell me why this is useful I might reconsider.

@dokterbob dokterbob closed this Jan 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants