Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not import django at top level in __init__.py #30

Merged
merged 1 commit into from
Jan 27, 2016

Conversation

ar45
Copy link
Contributor

@ar45 ar45 commented Jan 7, 2016

Fixed installing via pip had import django when it might not exist.

This is a quick ugly fix by moving the import into the function which needs it.

@Brobin
Copy link
Owner

Brobin commented Jan 27, 2016

Why is this an issue? Django should install via the requirements file.

@ar45
Copy link
Contributor Author

ar45 commented Jan 27, 2016

Requirements file does not guarantee any order (recently fixed, see pypa/pip#2478).
So in my requirements having both Django and django-seed it fails with an error no module named django.

In any case if you should not import something you rely on in your pre-install.

Brobin added a commit that referenced this pull request Jan 27, 2016
Do not import django at top level in __init__.py
@Brobin Brobin merged commit 95339f7 into Brobin:master Jan 27, 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.

None yet

2 participants