Skip to content
This repository has been archived by the owner on Sep 19, 2018. It is now read-only.

Migrate to Python 3.x && Django 1.8.x #415

Open
RadoRado opened this issue Sep 27, 2015 · 2 comments
Open

Migrate to Python 3.x && Django 1.8.x #415

RadoRado opened this issue Sep 27, 2015 · 2 comments

Comments

@RadoRado
Copy link

Any thoughts on moving to a newer Python and Django?

A simple check on requirements.txt - https://caniusepython3.com/check/979ec793-101d-4b35-9919-f4a7bb2d9f95 - shows 3 packages.

@mitio
Copy link
Member

mitio commented Sep 28, 2015

Sounds good.

We haven't planned on upgrading the tech stack as we have a lot more pressing issues to solve first. I'm okay with the upgrade once we get the most urgent stuff out the door as there are now less than two weeks to the start of Code Week.

I'll leave this issue open for later.

As for the openid, we're using it for the login part of the site, I think (or that's socialauth? I'm not sure).

@RadoRado
Copy link
Author

Thanks for commenting @mitio

I checked for any references for openid and open_id - found only in requirements.txt

socialauth is used in this project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants