how much work to get to python 3.6 and django 3.2?
Bug #1964366 reported by
Sheila Miguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| django-openid-auth |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm guessing from the tox.ini file that tests get run for Django 3.0.8, and it looks like python 3.6 is not supported.
How much work would it take to support those, not to mention Django 4.x?
I'm looking to upgrade my Django 1.11 environment and also upgrade to python 3.6 for my bionic environment.
Revision history for this message
| Sheila Miguez (codersquid) wrote | #1 |
To post a comment you must log in.
Good news. I made a sample Django 3.2 project on my bionic system and things mostly worked. I had to use the pickle session serializer still because python3-openid still has that problem.
The part that was odd was that when I logged in, lp didn't prompt me to share the canonical team, so my account didn't get added to that. I created two Django groups to correspond to two lp teams that I belong two, and I got added to the other one but not canonical. This actually happens to me when I run my actual Django site locally (but not in the deployed one) so it is a known issue for me, that still happens on this current version. Any clues as to why it happens?