If pip does uses build_wheel directly, as Paul now prefers, I think we can leave the NotImplemented/Error/None question for a later date. We only want some way to signal "I can't do that" because a frontend might try sdist->wheel with a fallback to making a wheel directly. If no frontend is actually planning to do that, we can leave specifying it until a frontend wants it.
Donald, what do you think? IIRC, you were most keen on going sdist->wheel where possible, and I don't think you've commented on Paul's suggestion yet (apologies if I've overlooked a response). Thomas On Mon, Aug 28, 2017, at 12:47 AM, Nathaniel Smith wrote: > On Sun, Aug 27, 2017 at 4:27 PM, Greg Ewing <greg.ew...@canterbury.ac.nz> > wrote: > > Nathaniel Smith wrote: > >> > >> - creating an sdist failed for unexpected reasons, that need a human > >> to sort out (due to a broken system, or bugs – hey, they happen – or > >> ...) > > > > > > I think that should still be reported via an exception. Returning > > None should only be for the specific case that the backend doesn't > > support the requested operation. > > Well, you can't exactly say "if your code is buggy, then you should > signal that by doing this well defined thing" :-). One of my > objections to None is that it's very easy to return accidentally, > i.e., buggy code *will* sometimes return None no matter what the spec > says. > > -n > > -- > Nathaniel J. Smith -- https://vorpus.org > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig