-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Django custom user compatible #5
Conversation
Needs to update migrations. Sorry... |
What do you think about just using The only reason I can think of to have the compatibility module is for Django 1.4 compatibility, but I think we can probably drop that for the next release? (Django 1.4 is very old, and out of its extended support lifetime upstream.) |
I think that is a good idea. I agree with everything you say |
This uses a generative envlist, and updates Python to 2.7 and 3.4. The tests don't pass on Python 3.5 and Django 1.9 yet.
(This drops MANIFEST, which should no longer be generated.)
Cool. :) Do you want to take a stab at updating this PR? |
Use find_packages() in setup.py. Drop Django 1.4 and 1.5 from automated tests.
This silences the Django 1.7 warning.
Remove the "coverage" configuration from Tox, for now: it does not really serve a compelling purpose, and it's not as easy to get it to generate good reports.
However, restrict Django 1.7 to exclude Python 3.5. (Django as of 1.7.11 does not work on Python 3.5.)
Update packaging, test suite, and Python / Django compatibility
Fix RemovedInDjango19Warnings
Sorry... but I have lots of projects to manage and no enough time to manage more... Thank you for your offer |
The proper way is to use Will this get merged in the near future? |
Project update: Move to Jazzband, or retire? #13 |
No description provided.