pypowsybl
pypowsybl copied to clipboard
[WIP] Draft of new layout for python modules
Signed-off-by: Sylvain Leclerc [email protected]
Please check if the PR fulfills these requirements (please use '[x]'
to check the checkboxes, or submit the PR and then click the checkboxes)
- [X] The commit message follows our guidelines
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)
Does this PR already have an issue describing the problem ? If so, link to this issue using '#XXX'
and skip the rest
#300
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Refactoring
@geofjamg @EtienneLt @CBiasuzzi @massimo-ferraro @obrix :
please do not hesitate to formulate a critical opinion on this proposed layout (implemented on loadflow module only as an illustration):
all actual code goes into impl
subpackage, while the public API is simply defined by importing the classes and methods we want to expose.
This should allow to scale better (more python files, basically ...), and to not care too much about namespace pollution in implementation files.
done with https://github.com/powsybl/pypowsybl/pull/641