Back
Similar todos
- write out notes on how to start and stop supporting python versions in python packages ✅ #greendeploy
Upgraded Python to 3.9 
#rhymecraft
- publish greendeploy-cli to pypi ✅ #greendeploy
- changed plan to publish `greendeploy-cli as opensource on pypi first so greendeploy-saas` can then reuse the same function that can clone the starters ✅ #greendeploy
⬆️ upgraded 
#djangopackages to Python 3.8 and used some automated cleanup tools
- greendeploy: test what happens when call the cli library to make the project ✅ #greendeploy
- upgrade dependencies of greendeploy ✅ #greendeploy
1. make django-last-active support python 3.8 as well ✅ #greendeploy
- upgraded dockerfile for ubuntu:focal image ✅ #greendeploy
updated my 
#dotfiles and upgraded my default Python to 3.10
upgraded #djangopackages to work with Python 3.8 and updated requirements
For #greendeploy
1. work on making django-last-seen 3.2 compatible ✅
⬆️ upgraded/deployed #djangopackages to Python 3.11 along with a bunch of security updates
- follow up on pygithub PR ✅ #greendeploy
- package greendeploy-cli to be deployable cli but got stuck github.com/kedro-org/kedro/di… ✅ #greendeploy
- install the greendeploy-cli library as dependency in greendeploy-saas ✅ #greendeploy
⬆️ upgraded jobs container from Python 3.7 to 3.10 and rewrote much of the guts and templates
- follow up with PyGithub PR ✅ #greendeploy
✏️ published "Upgrading Python from 3.11 to 3.12 notes" micro.webology.dev/2024/03/04…
updated my #dotfiles to support Python 3.11 and mostly fix some syntax errors caused by pyenv changing