[pip3] build Phoenix not verbose enough

I am building wxPhoenix with that command on a unixoid system

sudo pip3 install -v -U --pre -f
http://wxpython.org/Phoenix/snapshot-builds/ wxPython_Phoenix

You see I set '-v' to make pip3 more verbose.
So I see more pip-related messages. Nice.
But I miss Phoenix-build-related messages. I want to see each file that
is currently compiled or liked, etc.

In the past there where this informations but now they are missing.
Could you modify the essential build-call inside the scripts to be more
verbose please?

I think pip is now redirecting most output to a log file, so the output from Phoenix's build is probably going there. I'm not sure where the log is located by default, but from the help text it looks like you can give it an explicit location with the --log parameter.

Or, you can always grab the source tarball and build it using standard setup.py commands, and then you'll see all the build output. You'll see that there is quite a lot of output that way

···

c.buhtz@posteo.jp wrote:

I am building wxPhoenix with that command on a unixoid system

sudo pip3 install -v -U --pre -f
Index of /Phoenix/snapshot-builds wxPython_Phoenix

You see I set '-v' to make pip3 more verbose.
So I see more pip-related messages. Nice.
But I miss Phoenix-build-related messages. I want to see each file that
is currently compiled or liked, etc.

In the past there where this informations but now they are missing.
Could you modify the essential build-call inside the scripts to be more
verbose please?

--
Robin Dunn
Software Craftsman

Ah I see. In the past older versions of pip3 doesn't behave like that.
So you mean pip changed and not your build-srript?

···

On 2015-04-08 14:00 Robin Dunn <robin@alldunn.com> wrote:

I think pip is now redirecting most output to a log file

Yes, or at least it seems to be that pip is eating that output in some way.

···

c.buhtz@posteo.jp wrote:

On 2015-04-08 14:00 Robin Dunn<robin@alldunn.com> wrote:

I think pip is now redirecting most output to a log file

Ah I see. In the past older versions of pip3 doesn't behave like that.
So you mean pip changed and not your build-srript?

--
Robin Dunn
Software Craftsman