[work in progress] updating to django 3.1+#84
Conversation
|
thanks for working on this. Unglue.it is still at 1.11 and I spent a few days working on moving to 2.x but haven't had time to go finish up. |
|
This seems like a not-very-glamorous but needed task to future proof our websites. I'll take this as far as I can in local development, but I'll need to get my aws access set up again to ensure we can re-deploy the site. |
…e5's version of fa-code-fork > fa-code-branch
README.asciidoc
Outdated
| @@ -23,6 +24,10 @@ From the root of the project | |||
| For every new terminal, or when returning to work on the project, you will need to run | |||
|
|
|||
| source venv/bin/activate | |||
There was a problem hiding this comment.
seems the documentation is out of date
There was a problem hiding this comment.
the env setup instructions use requirements.txt, which you've deleted
Pipfile
Outdated
| [packages] | ||
| django = "==1.11.28" | ||
| django = ">=3.1.4" | ||
| gitberg = "==0.7.2" |
|
|
||
| [requires] | ||
| python_version = "3.6" | ||
| python_version = "3.9" |
There was a problem hiding this comment.
ebcli uses some config magic that's not clear to me, but the install platform default is py3.7 - look in .elasticbeanstalk/config.yml
There was a problem hiding this comment.
anything 3.6+ will let me use f-strings, so that should work

TODO: