At the moment PyAL is used across all the Python based actors (generated via FC2K). PyAL provides another layer between Access Layer and actors.
Event though current solution works it has some flaws:
1.1.1.1. Template
- Python template (FC2K) is composed of one, large file that is hard to maintain
- Lots of information between components is passed via dictionaries instead of strictly defined interfaces
- Logic of the actor is driven by if-else based approach - it's hard to add new features that are not supported at the moment
- Lots of hidden assumptions are made in the code (e.g. temporary files creation, arguments that are responsible for script execution, etc.)
- Error handling is not quite ideal
1.1.1.2. PyAL module
PyAL module (as a middle layer) seems to be obsolete now. As we plan to push everything towards IMAS based approach it seems reasonable to put PyAL features directly into Python interface, or as an external module that is quite close to Python HLI. At the moment, PyAL is hard to maintain due to:
- parts of code being hardcoded (magic values)