Closed hoelzerC closed 7 months ago
Requiring an explicit installation avoids wrong paths and enforces a working installation for development. Otherwise, when running tests from the root of the repo, you just import from the ./dxtb
directory.
Okay, we can design the user story to require explicit installation. Let's make a note of that in the docs.
The user does not need to do anything different here. The setup.cfg
is configured to respect the src layout, so pip install .
still works for installation from source. I will configure pip and conda for better installation anyway. The src layout really only avoids some undesired behavior for us developers.
So far it was not designed that user == pip install dxtb
and developer == git clone
. That was the whole point. For developers, it is slightly unhandy to import modules manually.
Was there a specific reason to have
./src/dxtb
instead of./dxtb
in the root directory of the package?