transition to pyproject.toml
Feature Summary
transition from setup.py to pyproject.toml
Problem Description
We are facing more and more restrictions due to the usage of setup.py instead of pyproject.toml. Even though it seems that not all features of setup.py have been ported to pyproject.toml, it seems to be necessary to make the switch. The recent bug with missing dependencies in pip demonstrated it again.
Proposed Solution
Transition to pyproject.toml. To the best of my knowledge, pyproject.toml does not support relative paths for editable installs. Therefore, it might be necessary to create a dedicated Makefile / bash script for setting up the developer environment.
Benefits
The usage of setup.py was deprecated years ago. This change will bring us back on track with the community.
Alternatives Considered
We could alleviate some restrictions by using projects like poetry. However, I fear there are quite a few disadvantages for the deployment at the beamline.
Impact on Existing Functionality
pip install -e ./bec_server
won't work anymore.
Priority
Medium