Another export question - I noticed that the ./bin directory in the venv created by

pants export ::

does not have a "pip" file in it. Is that by design? My use case for it is using e.g.

pip list | more

as a quick test of what's in the venv for when I want to run something outside of running it via pants

Its not really by design. For all internal venvs Pants omits pip on purpose. We don;t want internal venvs ever mutated. For export, we should provide pip.

Thanks, I'll write up a ticket if it seems like a need for my team

Excellent. Thank you.

For the purposes of quickly creating a venv for tinkering in, this has come up when talking to my team as well.. not sure how frequently it would be used, but it helps ease new users into the Pants world, to be able to offer functionality that is familiar (a venv with pip in it).

I definitely see this as easing new users into the Pants world, where it might be used a lot early on and then rarely used later on once the team is confident with Pants

That makes sense to me! Given that you both think this would be helpful to newcomers, @lively-exabyte-12840 would you be willing to please open a feature request? https://github.com/pantsbuild/pants/issues/new/choose That helps us a lot with project planning

Correct - that venv is not immutable on purpose, I just did the easiest thing that works when implementing export...

Just closing the loop on this - https://github.com/pantsbuild/pants/issues/14622

Thanks!