Editable install does not work as intended

[p-slash]

pip hard copies the files in the bin directory, so changes to the source do not propagate until another pip install -e is executed. One solution is to modernize the installation by moving to setup.cfg with [options.entry_points] and console_scripts. This requires moving the bin directory inside the py/picca folder and listing every executable setup.cfg.

[Waelthus]

Agreed that this is suboptimally done atm esp regarding the bin files (which also is causing differences between editable and normal installations and iirc was the reason to test on editable ones). But I'd opt for moving the setup info directly to pyproject.toml which is the current way recommended for python. Afaik, the main reason we still have a setup.py is that it allows getting some info, e.g. the list of all binaries, some additional data files and the git hashes programatically at install time.
If this is a non-issue now, or if people know better ways, I'd be all in favor for changing this.