This repository has been archived by the owner on Oct 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Django 1.8+ compatibility issues #236
Comments
For Django 1.9.1 and django-calaccess-raw-data 0.2.2,
|
Django 1.9.1 and django-calaccess-raw-data 0.1.2,
|
Django 1.8 and django-calaccess-raw-data 0.2.2 or 0.1.2,
|
gordonje
added a commit
that referenced
this issue
Jan 26, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(Arose out of ticket 1186 in the raw-data repo...)
Our code is currently only compatible with Django 1.7, which is especially problematic given that, as of v0.2.0, the raw-data app is >=Django 1.8 compliant and not backward compliant.
For the time being, I propose we lock this app into Django v1.7 and django-calaccess-raw-data v0.1.2 so that users don't encounter any of the errors that arise in scenarios listed below.
Going forward, if the campaign-browser is going to evolve with our other projects, we'll need to address the compatible issues listed below as well as any others. Then, as part of closing this ticket, we can switch the setup.py and requirements_dev.txt files back to allowing more current versions of Django and the raw-data app.
The text was updated successfully, but these errors were encountered: