[09:25:39] <pradyunsg> expect future forks of packaging to not spam this channel.
[09:30:17] <tos9> I think I've asked this question before (in a different way), but... is `virtualenv --no-setuptools venv; venv/bin/python -m pip install pep517; venv/bin/python -m pep517.build some/package/with/a/pyproject.toml` supposed to work?
[09:32:00] <tos9> I thought that was part of the point of pep517, that if the build requirements are specified, it knew how to at least get those
[10:13:00] <apollo13> tos9: just thinking out loud and not knowing what pep517.build does, I think that getting those would still be part of pip
[10:13:34] <apollo13> although according to pypi "Higher-level functions which install the build dependencies into a temporary environment and build a wheel/sdist using them."
[10:14:24] <apollo13> not sure if that covers the build module though
[12:55:14] <pradyunsg> tos9: yes, for the most part. The thing is, pep57 isn’t supposed to be user facing.
[12:55:28] <pradyunsg> This is literally https://discuss.python.org/t/2062, so that.
[12:56:39] <pradyunsg> The UX work that the discussion is blocked on recently got funded, so yay!
[13:37:52] <tos9> pradyunsg: Oh. Nice (that it got funded -- I think last I heard toad_polo disagreed but I'm sure not if those things get built)
[13:37:57] <tos9> pradyunsg: But was that "yes for the most part" that it should work?
[13:38:50] <tos9> Because I'm getting strange errors (though maybe ones suitable for #pypa) -- tracebacks that just end with BackendUnavailable
[13:40:51] <pradyunsg> Yea, well. It'd probably be useful to file an issue in pep517's repo listing them.