[14:23:52] <toad_polo> I guess this? https://github.com/pypa/pip/issues/7620
[14:24:43] <pradyunsg> Yea, pip 20.0 basically broke all CI systems. :)
[14:25:57] <toad_polo> Still using `setup.py bdist_wheel` I see!
[14:27:18] <toad_polo> Someone should really make a thin wrapper around `pep517`. `pep517.build` has basically the right UI, we just need a tool that falls back to using a default `pyproject.toml`
[15:08:48] <duckinator> toad_polo: i have a project that's basically a wrapper around pep517 + a very basic task runner, but i'm not sure it's quite ready in terms of tests + documentation. it's successfully built+released itself for all 7 releases, though. :3 https://github.com/duckinator/bork/
[15:10:01] <toad_polo> This seems like it does many other things.
[15:10:40] <toad_polo> duckinator: What does it do if there's no `pyproject.toml`?
[15:10:43] <duckinator> it's a build + release tool with a very basic task runner (only one-liner commands). builds on top of pep517 + twine to avoid reinventing wheels.
[15:13:22] <duckinator> toad_polo: atm, it won't work, but i'm not opposed to changing that once i improve the state of it wrt tests and documentation. but these lines should be all that's required, if you're using setuptools for it (in theory it can use anything the pep517 library does, but i don't have any testcases for that): https://github.com/duckinator/bork/blob/master/pyproject.toml#L1-L4
[15:14:05] <toad_polo> Looks like an interesting project, but it doesn't really meet my requirements.
[15:14:54] <duckinator> fair enough. ^^ nice thing about pep517 (both the PEP itself and the library) is the ability to reuse the core functionality so easily.
[15:15:04] <toad_polo> I'm looking for a super barebones thing that can replace `setup.py bdist_wheel sdist` in the same way some people are using `pip wheel . --no-deps -w dist/`.
[15:15:57] <toad_polo> Right now I always use `python -m pep517.build -b -s .`, but that only works if you have `pyproject.toml`, so you can't say, "Use this command", you have to say, "Create a pyproject.toml and then use this command".
[15:16:09] <toad_polo> Which doesn't work if you're building someone else's project.
[15:16:25] <toad_polo> I don't think it is terribly difficult to build what I'm suggesting.
[15:18:05] <duckinator> yeah, it shouldn't be too hard. i think the stdlib and the toml + pep517 libraries should be more than capable of handling it.
[15:19:20] <toad_polo> I doubt you'll need `toml`.
[15:20:14] <toad_polo> Though you're probably pulling it anyway via `pep517` and I suppose using a fallback mechanism of PEP 517 -> generate pyproject.toml -> invoke setup.py would work.
[15:21:39] <duckinator> ah, yeah, i think you're right wrt not needing toml. looks like the actual build process is the one place bork doesn't use it haha
[15:41:27] <duckinator> toad_polo: this may be a good starting point for you if you decide to make your own thing: https://gist.github.com/duckinator/94205a8465403b2354d4469a437bad9f :) stdlib + pep517, ~30 lines.