unification of coding style
General rules we adhere:
- names: snake_case, class names: CamelCase
- all names: it should make sense,
- length of names: what is detail that can be left away, make it as succinct as possible (for instance,
envs.generators.rail_from_manual_specifications_generator
is too long) - comment: if the idead cannot be read from the structure of the code, then write a comment.
See https://realpython.com/python-pep8/
Procedure
- Everyone goes through their code, re-read it and try to understand (good luck)... improve rea
- Read other people's code and give feedback, you may add items to the following list.
Issues List
-
@mohanty shorten envs.generators.rail_from_manual_specifications_generator
Edited by Christian Eichenberger