Isuru Fernando
Isuru Fernando
May be we should just use `parse_version` from `pkg_resources`
Projects like numpy use a development version of cython to build wheels because the cython release might be far away.
@linehill any ideas why there is a link error?
``` Error(s) while linking: Cannot find symbol _Z13get_global_idj in kernel library Cannot find symbol _Z22_cl_work_group_barrierj12memory_scope in kernel library Device cpu failed to build the program ```
Any thoughts on https://github.com/conda-forge/python-feedstock/pull/679/files#diff-a6a19a192f8fe15a32c4a1d019dfbba33a7128027489cc91a25f95a90b16d92e ?
No, it just adds the 3.13 (without the t) to sys.path. So, noarch packages installed into 3.13 will get found and non-noarch are still going to end up in 3.13t....
Thanks. Added a news entry and updated the PR description.
Yes, that's correct. The line you linked to doesn't matter. conda-build's relocation logic works after the link check logic.
We could make another repo or just download one self-contained python file that lives in regro/cf-scripts. It's a separation of concern issue. conda-smithy should not be the place where BotConfig...
That would require co-ordinating the release of conda-smithy and the new package. The whole point is to make the bot config be independently developed from conda-smithy.