On Mon, Jul 17, 2017 at 6:25 AM, Donald Stufft <don...@stufft.io> wrote: > Fwiw I also agree return values are more robust, though the fact that an > exception has a message is also a nice property since it allows backends to > provide a reason they dont support sdist in this tree (which some tools may > want to surface to users, particularly if they *need* a sdist, like a > hypothetical 'twine sdist' command). That could be implemented by returning a > Tuple though or something.
What's your opinion on "show the backend's stderr output" as an error message reporting system? It's admittedly a bit duct-tape-and-baling-wire, but tools like 'twine sdist' need to capture and display stderr regardless, and either way it's just unstructured text we're dumping at the user, so I'm having trouble pointing to any specific value provided by having a second error channel. -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
