pip and PEP 517 Backends
I have a PEP 517 compatible backend which works with pip to install from an sdist (via an internal wheel). However there are a couple of issues...
pip swallows all output from the backend. Is there anyway for the user to see the output (builds can take several minutes)?
I would like to pass options from the pip command line to the backend but neither --global-option or --install-option have any effect (the config_settings argument is always None). How do I achieve this?
Thanks, Phil
On Sat, 24 Aug 2019 at 06:46, Phil Thompson phil@riverbankcomputing.com wrote:
I have a PEP 517 compatible backend which works with pip to install from an sdist (via an internal wheel). However there are a couple of issues...
pip swallows all output from the backend. Is there anyway for the user to see the output (builds can take several minutes)?
pip -v (or maybe -vv) should show this (plus a chunk of other stuff, unfortunately, but we don't have any finer control over what gets logged (and I'm not even sure what a good UI for something like that would look like).
I would like to pass options from the pip command line to the backend but neither --global-option or --install-option have any effect (the config_settings argument is always None). How do I achieve this?
That's basically "not implemented yet" (mostly because there's limited need for it with existing backends). So the answer to that would be to propose a PR for pip that adds support for config_settings. Sorry...
Paul
On 24/08/2019 10:27, Paul Moore wrote:
On Sat, 24 Aug 2019 at 06:46, Phil Thompson phil@riverbankcomputing.com wrote:
I have a PEP 517 compatible backend which works with pip to install from an sdist (via an internal wheel). However there are a couple of issues...
pip swallows all output from the backend. Is there anyway for the user to see the output (builds can take several minutes)?
pip -v (or maybe -vv) should show this (plus a chunk of other stuff, unfortunately, but we don't have any finer control over what gets logged (and I'm not even sure what a good UI for something like that would look like).
It looks like the output is buffered and appears right at the end, so not good for progress messages during a lengthy build.
Phil
On Sun, Aug 25, 2019 at 8:15 AM Phil Thompson phil@riverbankcomputing.com wrote:
On 24/08/2019 10:27, Paul Moore wrote:
pip -v (or maybe -vv) should show this (plus a chunk of other stuff, unfortunately, but we don't have any finer control over what gets logged (and I'm not even sure what a good UI for something like that would look like).
It looks like the output is buffered and appears right at the end, so not good for progress messages during a lengthy build.
The lines should be getting shown immediately in verbose mode: https://github.com/pypa/pip/blob/d2b7082932a59585ea6198cbf375758fae949c67/sr... If not, it's a bug..
--Chris
Phil
Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/5QMXH...
On 25/08/2019 19:46, Chris Jerdonek wrote:
On Sun, Aug 25, 2019 at 8:15 AM Phil Thompson phil@riverbankcomputing.com wrote:
On 24/08/2019 10:27, Paul Moore wrote:
pip -v (or maybe -vv) should show this (plus a chunk of other stuff, unfortunately, but we don't have any finer control over what gets logged (and I'm not even sure what a good UI for something like that would look like).
It looks like the output is buffered and appears right at the end, so not good for progress messages during a lengthy build.
The lines should be getting shown immediately in verbose mode: https://github.com/pypa/pip/blob/d2b7082932a59585ea6198cbf375758fae949c67/sr... If not, it's a bug..
Ah, my fault. I need to flush the progress messages.
Thanks, Phil
participants (3)
-
Chris Jerdonek -
Paul Moore -
Phil Thompson