-
Notifications
You must be signed in to change notification settings - Fork 20
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
Upgrade to Django 1.9 #283
Conversation
@@ -19,6 +19,47 @@ Done! | |||
The following instructions describe modifications to the standard upgrade process required due to | |||
specific changes. Items are listed in reverse chronological order. | |||
|
|||
## 4/28/16 - Upgrade Django from 1.7 to 1.9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use three ###
to keep the formatting consistent with the other upgrade headers.
Anyone know what the Travis error is all about?
|
The AttributeError looks to be incompatible versions of
http://stackoverflow.com/questions/28967785/attribute-error-installing-with-pip |
thx @eosrei - I'm a bit confused as to how this can be fixed since I assume it isn't happening anywhere other than in Travis, correct @IllyaMoskvin? I am thinking perhaps it is due to Travis using an old version of Ubuntu (12.04) by default. @jslootbeek since you did great work fixing Travis for #273, perhaps you can weigh in on this issue? |
@hburgund Definitely could be 12.04. Add
to switch to the beta for 14.04: https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments |
@eosrei thanks for the link, Brad! I'm going to attempt some squashing + force pushing to get this all sorted out. Just give me a few hours, venturing into some unfamiliar territory here with Travis. |
Switching to the 14.04 beta branch is not a bad idea moving forward, but I would be surprised if it worked cleanly out of the box. We'll likely need to fix some other things as well. |
@jslootbeek I'm using |
You can either specify it in requirements/dev.txt by adding |
Well, no luck so far. If someone has other ideas, please let me know. Still erroring out on setuptools. You can check the commit history for things I've tried.
|
@hburgund is (1) awesome, and (2) managed to fix the Travis error! I'm getting the same failed tests on my vagrant instance. Hopefully this is just a case of deprecated methods. I'll look into this either tomorrow or on Monday. |
@IllyaMoskvin what is the status on the error in the unit tests? Now that you are getting it locally as well as in Travis, it should be fairly easy to track down, I am hoping. I want to get this PR fully tested and integrated ASAP. |
I've discussed this on our Slack, but I'd like to post it here for reference, too. There are still three failed tests. All three test cases are related and trace back to the |
ee2092b
to
4cb5843
Compare
Good news! Gray and I worked through the problem together. Apparently, |
ca83ff3
to
cd3a4e7
Compare
dd12ade
to
a94390e
Compare
Added explicit permission-based queryset filtering to ProjectAdmin. Going forward, we should keep in mind that using See #291 for a subtle little problem caused by our
Therefore, I am removing these fixtures and incorporating a table flush command into the upgrade instructions. |
a94390e
to
ffc6824
Compare
I have done an upgrade test on a fresh
After we deal with these small issues, it's ready to merge as best I can tell. |
819144c
to
ca79c05
Compare
I'll wait on rebasing the APIv2 and devapi branches until this one is merged. |
Agreed that #293 isn't an upgrade issue, so doesn't need to hold up this merge. Regarding
This will be a better and more central spot to use than the IMAMuseum fork. |
ca79c05
to
58e4c11
Compare
Excellent. I updated (and renamed) |
Do we still need the
|
😄 That's why I linked the issue: https://code.djangoproject.com/ticket/17946 The issue is " closed Bug (fixed)", therefore the solution is in Django. The code and file should be removed. |
This is a fairly extensive commit, since most of the requirements had to be upgraded as well. Dependencies have been locked down to specific versions for consistency and troubleshooting. Notable changes: - Moved wsgi.py to a more standard location, updated apache config. Now referenced in roundware.settings.WSGI_APPLICATION - For roundware.api2, implemented the new Application Configuration structure. See http://stackoverflow.com/q/32795227/1943591 - django-guardian now creates its own AnonymousUser in the database. Removed AnonymousUser references from fixtures to avoid conflicts. http://django-guardian.readthedocs.io/en/stable/configuration.html - django-guardian assign is being depricated for assign_perm See django-guardian/django-guardian@1419048 - ManyToManyField no longer accepts null=True - django.contrib.auth.models.User should not be accessed directly. Use django.conf.settings.AUTH_USER_MODEL instead - Django changed the way it loads models, which broke streaming. Moving django.setup() in roundwared.rwstreamd fixed the issue. - django_chartit is no longer maintained. Moved to django_chartit2 This may require us to install jQuery and Highcharts manually - django.forms.models.save_instance has been removed. We are now calling save() instead, but it might need more testing. django/django@8656cf django/django@b11564 - Fixed errors in Travis install script (thanks @hburgund) - Fixed jsocol/django-adminplus/issues/42 - Fixed django-admin-bootstrapped dependency See IMAmuseum/django-admin-bootstrapped - Fixed queryset filtering in ProjectProtectedThrough classes in admin.py Added explicit permission-based queryset filtering to ProjectAdmin - Fixed duplicate rows in auth_permission, removed default_auth fixtures. - Removed fix-m2m-deserial.patch This closes roundware#229, fixes roundware#291, and supersedes roundware#282.
58e4c11
to
4b43011
Compare
yes, indeed, I believe we are merge-ready. Is it possible?!?!? |
This is a fairly extensive commit, since most of the requirements had
to be upgraded as well. Dependencies have been locked down to specific
versions for consistency and troubleshooting. Notable changes:
Now referenced in roundware.settings.WSGI_APPLICATION
structure. See http://stackoverflow.com/q/32795227/1943591
Removed AnonymousUser references from fixtures to avoid conflicts.
http://django-guardian.readthedocs.io/en/stable/configuration.html
See django-guardian/django-guardian@1419048
Use django.conf.settings.AUTH_USER_MODEL instead
Moving django.setup() in roundwared.rwstreamd fixed the issue.
This may require us to install jQuery and Highcharts manually
We are now calling save() instead, but it might need more testing.
django/django@8656cf
django/django@b11564
See roundware/django-admin-bootstrapped
Added explicit permission-based queryset filtering to ProjectAdmin
This closes #229, fixes #291, and supersedes #282.