Skip to content
This repository has been archived by the owner on Jan 9, 2019. It is now read-only.

Upgrade to Django 1.10.1 #129

Merged
merged 4 commits into from
Oct 5, 2016
Merged

Conversation

glogiotatidis
Copy link
Contributor

No description provided.

@glogiotatidis glogiotatidis changed the title Upgrade to Django 1.10.1 WIP - Upgrade to Django 1.10.1 Sep 27, 2016
@glogiotatidis
Copy link
Contributor Author

This is currently blocked by django-session-csrf being incompatible with Django 1.10. There's an open pull request to fix that: mozilla/django-session-csrf#30

@peterbe maybe you can push things forward?

@peterbe
Copy link
Contributor

peterbe commented Sep 29, 2016

I left some comments mozilla/django-session-csrf#30 but once that lands I can take care up updating pypi. Then we can proceed on this PR.

@glogiotatidis glogiotatidis changed the title WIP - Upgrade to Django 1.10.1 Upgrade to Django 1.10.1 Oct 3, 2016
@glogiotatidis
Copy link
Contributor Author

@peterbe updated!

Copy link
Contributor

@peterbe peterbe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to check out this branch and build a project with it for testing.
Just gotto remind myself how to use cookiecutter because it's been a couple of years since last.

@@ -1,14 +1,16 @@
from django.conf import settings
from django.conf.urls import include, url
from django.contrib import admin
from django.views.static import serve as static_serve
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did it need to be aliased? What's wrong with just serve?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just find static_serve more descriptive

@peterbe
Copy link
Contributor

peterbe commented Oct 3, 2016

We might need to go back to django-session-csrf and work on this. But I just created a fresh new install based on this branch and it won't even start.
screen shot 2016-10-03 at 8 49 47 am

The fault lies with django-session-csrf but we have to take responsibility of that.

@peterbe
Copy link
Contributor

peterbe commented Oct 3, 2016

Let's hope @moggers87 finds the time to complete the python 3 support.
mozilla/django-session-csrf#20 (comment)

I just can't accept that we say that sugardough is compatible with django 1.10 but doesn't work in Python 3.

@glogiotatidis
Copy link
Contributor Author

Fair enough, let's wait that for a week. @moggers87 is already working on py3

@peterbe
Copy link
Contributor

peterbe commented Oct 4, 2016

I tested your PR together with the python3 branch that @moggers87 is working on and now my recently created sugardough python 3.5 project worked.
See mozilla/django-session-csrf#36 (review)

The only testing I did was to load the home page. But that didn't work before.

So let's pause on this PR until we can also include a new django-session-csrf version hashed in.

--hash=sha256:44e4639ec057a6b6a9dddb869d4e3a4818fc9278ec490cce39aef08440592a93
django-jinja==2.1.3 \
--hash=sha256:64446ae1de3593136042147cb16ba9a3aa4449370d9c26c1ec9b7553b2d1c809
django-session-csrf==0.7.0 \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This now needs to be 0.7.1 and sugardough should be py3 ready. Yay!

@glogiotatidis
Copy link
Contributor Author

woohoo! @peterbe updated, feel free to squash merge

@peterbe peterbe merged commit eb2566d into mozilla:master Oct 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants