You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which will result in a broken package when installing from a tarball
File "/home/conda/feedstock_root/build_artifacts/pycromanager_1691005638576/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehol/lib/python3.11/site-packages/setuptools/build_meta.py", line 338, in run_setup
exec(code, locals())
File "<string>", line 14, in<module>
FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
error: subprocess-exited-with-error
I am going to add a dummy requirements.txt as the rest of the conda dependencies will be provided by the recipe meta.yaml.
Using this sort of install procedure (relying on an external requirements.txt) file is not recommended. Could you look into other ways of specifying dependencies? for instance using a setup.cfg file as described here.
Cheers!
The text was updated successfully, but these errors were encountered:
Hi team, in working on the conda forge package for the latest release
conda-forge/pycromanager-feedstock#29
We noticed that the tarball is not including the
requirements.txt
file:https://github.com/micro-manager/pycro-manager/blob/main/requirements.txt
Which will result in a broken package when installing from a tarball
I am going to add a dummy
requirements.txt
as the rest of the conda dependencies will be provided by the recipemeta.yaml
.Using this sort of install procedure (relying on an external
requirements.txt
) file is not recommended. Could you look into other ways of specifying dependencies? for instance using asetup.cfg
file as described here.Cheers!
The text was updated successfully, but these errors were encountered: