-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Open
Copy link
Labels
choreKeeping things up to date/addressing deprecationsKeeping things up to date/addressing deprecations
Description
During deployment, we get the following deprecation warning:
dev: commands[4]> pip install -e ./layers/hls_lambda_layer/python
Obtaining file:///home/runner/work/hls-orchestration/hls-orchestration/layers/hls_lambda_layer/python
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Installing collected packages: hls_lambda_layer
Attempting uninstall: hls_lambda_layer
Found existing installation: hls_lambda_layer 0.0.0
Uninstalling hls_lambda_layer-0.0.0:
Successfully uninstalled hls_lambda_layer-0.0.0
DEPRECATION: Legacy editable install of hls_lambda_layer==0.0.0 from file:///home/runner/work/hls-orchestration/hls-orchestration/layers/hls_lambda_layer/python (setup.py develop) is deprecated. pip 25.0 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457
We want to update hls_lambda_layer according to the instructions in the warning. The use of --use-pep517
with setuptools >= 64
is likely easier than switching to using pyproject.toml
.
Metadata
Metadata
Assignees
Labels
choreKeeping things up to date/addressing deprecationsKeeping things up to date/addressing deprecations