New syntax proposal: Section Statement to adopt most features of config language

[Paddy3118]

@AlfredDU

What I expect is such a goal: the python file with this new syntax is valid code for program developers, and also it appears absolutely a valid, human-read-friendly configure file (like toml or ini) for configuration ops and maintenance staff.

Not sure that having a configuration file with such power is wise? TOML isn’t Javascript for example, neither is JSON. It would be too easy for others to do too much in what should be just configuration. I prefer the security of configs being restricted much much more.

[AlfredDU]

Dear Paddy,

Developer can choose either to write just plain config files like regular toml, or flexible, more powerful config with advanced values such like class or method. It is not rare for the latter case, for example:

1. use enum in config file (it is a very common feature request for toml);
2. use callback in config file, for example, set a ease-function for visual animation effect config items.