It might be possible that PEP518 style pyproject.toml provides us with hooks into the build (python -m build) and install (python -m install) steps to run our own code to adapting and installing files.
This could make socranop-installtool mostly to completely obsolete.
Some things to check:
compatibility with our minimum Python version
compatibility with pipenv install --dev type editable development installations (I would not want to lose the editable development installation)
what about installing to arbitrary locations outside of our $prefix, e.g. to /etc/udev/rules.d/ for installs to $HOME/.local?
It might be possible that PEP518 style
pyproject.toml
provides us with hooks into the build (python -m build
) and install (python -m install
) steps to run our own code to adapting and installing files.This could make
socranop-installtool
mostly to completely obsolete.Some things to check:
pipenv install --dev
type editable development installations (I would not want to lose the editable development installation)$prefix
, e.g. to/etc/udev/rules.d/
for installs to$HOME/.local
?This is probably a post 0.5 thing.