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

Updated for Django 3.0 and added ability for blank fields #15

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

Adrian-at-CrimsonAzure
Copy link

Fixes #14
It Will now only import if Django version is older than 3.

I also added the ability to leave the fields blank since I found it annoying that you couldn't do this.

I have not tested this with Django 2.x as I have moved all of my projects over to 3.x but I don't see any reason why this wouldn't work.

@Adrian-at-CrimsonAzure
Copy link
Author

No idea why the Django 3.0 test is failing. I don't want to invest more time into it and I am not familiar enough with the codebase. It's working fine in my Django 3.0 app running on Python 3.6

If someone else wants to take a look at it, be my guest.

@jmichalicek
Copy link
Owner

Not sure how I missed this PR. I just fixed a bunch of bugs after discovering another user was still using this on modern versions of Django. I'm going to look at the other stuff you did with the blank values. At this point I've just dropped support for Python 2, although I'm sure there's more cleanup to be done if I take a closer look. I just fixed quick, obvious stuff while I was in dealing with the main problem I set out to fix.

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.

Django 3.0
2 participants