The web framework that scales with you. TurboGears 2.4.3 released https://github.com/TurboGears/tg2/releases/tag/tg2.4.3
amol- on master
Test on Python3.9 (compare)
amol- on development
Check on py39 (compare)
amol- on py39
amol- on py39
Check on py39 (compare)
amol- on py39
amol- on development
Check on Python 3.9 Handle deprecated python method (compare)
amol- on py39
Check on Python 3.9 Handle deprecated python method (compare)
amol- on py39
Handle deprecated python method (compare)
amol- on py39
Check on Python 3.9 (compare)
amol- on py39
Check on Python 3.9 (compare)
amol- on py39
Check on Python 3.9 (compare)
Convert
is enough: https://turbogears.readthedocs.io/en/latest/reference/classes.html#tg.validation.Convert
_lookup
is probably what you are looking for.key
in practice defines "in which parameter you find the value for that widget"
@michael-goebel From 2.1.5 it should be doable to upgrade up to 2.4
There are some big changes, but nothing that should require you to rewrite things from scratch apart maybe the usage of TW2 instead of TW1.
My suggestion is to read the upgrade guidelines version by version -> https://turbogears.readthedocs.io/en/development/reference/upgrading.html
You can try to excecute them all at once, which is more complex but faster or just upgrade one version at the time. From 2.1 to 2.2 and then to 2.3 and so on... Once you are on TG2.2 and TW2 the jump to newer versions should be more straightforward.
@CastixGitHub note that PR includes some changes to quickstart that were already discussed in a previous PR: https://github.com/TurboGears/tg2devtools/pull/19/files
The setting up your version control system is definitely out of the scope of gearbox quickstart
. It might go in a dedicated gearbox
command like gearbox gitignore
or things like that providing a good ignore file for TG projects. But doing git init
is definitely out of the scope of both gearbox and tg.