-
Notifications
You must be signed in to change notification settings - Fork 12
Django upgrade #701
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
base: master
Are you sure you want to change the base?
Django upgrade #701
Conversation
|
I think I just found an issue. Updating a static interface doesn't seem to work. |
|
Anything specific I can do to help evaluate this? Or should I just poke On Mon, May 19, 2014 at 10:17 AM, Nathan Murrow notifications@github.comwrote:
|
|
Yeah, this pull request is still pretty rough so just see what errors you can find. We might not be merging this one for a while. |
|
There is a lot of deprecated/renamed django libraries. I tried this at home once. Good luck! |
|
Incidentally, this pull request requires |
|
Seems like this pull request is failing because of CSRF errors. |
|
Is this going to work or should we stay on 1.4 for now? |
|
It does not work and I don't have a plan for making it work. Someone more familiar with the CSRF stuff needs to take a look if we want to go through with it. |
Some modifications to get Cyder working on Django 1.6. Maybe we should shoot for 1.7 instead? But anything is better than 1.4.
Tests pass and I haven't been able to tell that anything is wrong from poking around the interface, but a more thorough investigation might be prudent.