Log file Viewer

[00:06:09] <raydeo> is there a way to supply version pins for build dependencies of a package that's using pyproject.toml's build-system requires = [...]?

[00:06:38] <raydeo> normally the convention is for projects to not pin their deps and allow integrators to pin them in their app, but I don't see a way to do that with the build-system requires

[00:07:57] <ngoldbaum> raydeo: the pep says that the strings in requires are pep 508 specifications, so i think you can just include the version constraint in the specification string

[00:08:02] <ngoldbaum> at least if the pep is correct anyway

[00:08:14] <raydeo> that doesn't let me pin it externally... that requires me to edit the source package

[00:08:35] <ngoldbaum> oh i see, you're not the package author

[00:08:37] <ngoldbaum> nm

[00:08:40] <raydeo> correct

[00:08:59] <ngoldbaum> patch the project's setup.py?

[00:09:04] <raydeo> when not using isolated builds I can normally install the pinned versions of packages first, then the build will use those as long as they match the constraints

[00:09:15] <ngoldbaum> and file a bug upstream

[00:10:15] <raydeo> sure, I'm asking if there's a supported way to externally specify the constraints without having to edit the source package... because there is for non-build dependencies (just install the pinned version first and pip will see it and use it)

[00:12:14] <raydeo> it's possible for example that pip will respect the `--constraint` flags in that case or use the version installed into the main environment if it exists

[00:12:28] <raydeo> but I can't find anything definitive so asking :-)

[03:57:41] <dstufft> raydeo: uhh, I think our current answer is to manually build a wheel

[16:40:16] <raydeo> dstufft: hmm ok.. if the constraints and maybe requirements worked I think that'd be a good solution