Conda config does not respect constraints in install_requires

[tobiasdiez]

Is there an existing issue for this?

• I have searched the existing issues for a bug report that matches the one I want to file, without success.

Did you read the documentation and troubleshoot guide?

• I have read the documentation and troubleshoot guide

Environment

- **OS**: Win 11
- **Sage Version**: latest

Steps To Reproduce

Run ./bootstrap-conda.

Expected Behavior

The generated conda config file should contain the same version constraints as specified in the install-requires files.

Actual Behavior

The generated config does not contain the version constraints, or incompatible ones. E.g. at https://github.com/tobiasdiez/sage/actions/runs/4150784209/jobs/7180663661, you can see that networkx, lrcalc and ptyprocess are not specified correctly.

Additional Information

@mkoeppe can you have a look at this? I tried to do this, but since your latest optimizations in the bootstrap-conda script my bash skills are no longer sufficient to understand what's going on there in detail (e.g. somewhere spaces are treated as array separators, so one cannot simply pull in the install-requires files).

[mkoeppe]

It is not clear to me how to transform version specifiers according to PEP 440 to corresponding conda version specifiers. @isuruf, can you help?

[isuruf]

I'm not sure I understand. Can you give some examples?

[tobiasdiez]

I think conda understands PEP 440 version specifiers: https://github.com/conda/conda-build/blob/925c2274ed517926b69aa1e5287d8629e4905be5/conda_build/skeletons/pypi.py#L826