Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Python scripts to modules and install via entry points #201

Open
tkittel opened this issue Sep 24, 2024 · 0 comments
Open

Migrate Python scripts to modules and install via entry points #201

tkittel opened this issue Sep 24, 2024 · 0 comments

Comments

@tkittel
Copy link
Member

tkittel commented Sep 24, 2024

For two reasons we should migrate Python scripts to modules and install via entry points.

  1. To allow systematic access to all cmdline scripts from the python API, without messing with subprocesses.
  2. To make it easier to install cmdline scripts on Windows, where pip can take care of all the .bat/.exe wrapping for us.

Once done properly, the python modules could be called like _cli_ncmat2cpp.py for ncrystal_ncmat2cpp, however they could in general come with a Python API frontend e.g. ncmat2cpp.py, where most of the features would be implemented. Or we remove the _ in _cli_ncmat2cpp in case someone feels like providing a custom arg list and call it exactly like the cli script.

Special cases: nctool (just the naming is special) and ncrystal-config (we might want this also as part of a future C++/C API package).

Relates to #154 and #152.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant