Currently, everything is shipped in package pyracf.
Core irrdbu00 reader is in pyracf/__init__.py, which defines the RACF class. The RACF class has methods:
coded as functions in __init__.py
defined through property() as class properties, this includes most of the publisher names
inherited from ProfilePublisher, XlsWriter
RACF instances create dfs:
dataframes (starting with _) are defined as ProfileFrame() and then linked using setattr
It is easy to delete XlsWriter from the RACF class, and force users to import the module containing XlsWriter.
The same applies to RuleVerifier, i.e. create verifier instances explitly using v = RuleVerifier(r), but where should we store the rule_verifier.py module?
Also, RuleVerifier needs some of the same classes that RACF uses. That implies creating a separate directory with class definitions, that modules in both pyracf and verifier directories import from.
Same could be done with the ProfilePublisher class (optional), and the FrameFilter class (also shared between pyracf and verifier).
Currently, everything is shipped in package pyracf.
Core irrdbu00 reader is in
pyracf/__init__.py, which defines the RACF class. The RACF class has methods:__init__.pyRACF instances create dfs:
It is easy to delete XlsWriter from the RACF class, and force users to import the module containing XlsWriter.
The same applies to RuleVerifier, i.e. create verifier instances explitly using v = RuleVerifier(r), but where should we store the rule_verifier.py module?
Also, RuleVerifier needs some of the same classes that RACF uses. That implies creating a separate directory with class definitions, that modules in both pyracf and verifier directories import from.
Same could be done with the ProfilePublisher class (optional), and the FrameFilter class (also shared between pyracf and verifier).
Do we want multiple packages?