Re: Switch b4/README.txt to "pipx install" instead of "pip install"?

[Marc Herbert <marc.herbert@linux.intel.com>]

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> On Fri, Nov 21, 2025 at 01:03:46PM -0800, Marc Herbert wrote:
>> > If you'd like to submit a patch, I'll be happy to apply it.
>> 
>> Sent. If you'd like to fix my English or make some other minor changes,
>> please just go ahead and do not ask for my permission.
>
> I followed up already, but if you'd like me to wordsmith the rest myself, I'm
> happy to do that -- writing docs is nobody's favourite job. :)

Please go ahead, otherwise there's a good chance you would spend more
time holding my hand than doing it yourself. Also, don't give me credit
if you make all the changes you requested, that would not reflect
reality.

Making a one-line doc fix is easy, but anything slightly wider requires
a good overview of the whole docs to maintain consistency. You have that
and I don't.

On the other hand, I hope you can eventually work through the backlog
and look at my other, unrelated patch and questions on this list :-)

>> The only drawback is the same as the advantage: too much virtual env
>> isolation! It hits you when you try to install and use "on the fly" some
>> fancy debugger, test plugin, tracing library, Python IDE,... They are
>> generally "not found". Then you either need to explicity add them to the
>> manifest, or use some obscure pipx option, or revert to "pip instal
>> --break-system-packages -e .", or to "b4.sh",...
>
> The biggest drawback of anything pip (or pipx) installed is that everything
> breaks when I upgrade my distro to the next version and suddenly my Python is
> 3.14 and not 3.13. :)

Ah yes, that too! Forgot that other bit of Python fun. I have a special
Trash/ folder for those occasions, too afraid to break something
prematurely...