fix: Fix listing globals. Update plugins.

[milesj]

@rotu Fixes things.

One caveat though is that Python bins and globals are the same dir, so listing globals lists a bunch of other stuff. Not sure we can work around that easily.

[rotu]

One caveat though is that Python bins and globals are the same dir, so listing globals lists a bunch of other stuff.

A “global” could mean the name of a package, a module, or a binary. What do you intend proto to mean by that word for Python?

[milesj]

list-global is meant to display global packages that the user has ideally installed with install-global. Showing more than what they installed may confuse users.

[rotu]

list-global is meant to display global packages that the user has ideally installed with install-global. Showing more than what they installed may confuse users.

Hmmm that’s a hard problem! pip doesn’t track which dependencies are directly requested. And listing out some bin folder won’t do since a package may have zero, one, or several executables.

I’ve enjoyed using poetry in the past to specify projects or environments. I’ve found pipenv to be a terrible experience (but I don’t remember why). And a requirements.txt file is probably the lightest-weight way to do it (with something like pip-sync)

Also I haven’t tried pdm meaningfully yet. I got distracted by bugs in proto :-p