select environment detail info

[eleanorjboyd]

in "select a python environment" dropdown, we should include the path to the executable of that python as a description:

img copied from #490

[karthiknadig]

We removed path because it was noisy. We can add it back if it is useful.

[cwebster-99]

@eleanorjboyd did we receive feedback on wanting this back?

As an aside, we show the path in the select interpreter drop down although I do find this view quite noisy and given some of the paths get cut off the usefulness decreases. I am curious if we think this is more useful in Select Interpreter or Create Environment flows. Should we unify whether or not we show this information across these UIs or is it not very necessary. We also show the path on hover in the Python Environments panel.

[eleanorjboyd]

yes I did receive feedback at pycon but there was also a bug where multiple like 3.12s showed up for a single executable so maybe if thats fixed we don't need to surface it?

[cwebster-99]

I would recommend addressing that bug first and then see if we still receive the feedback to add the path back here. I like how we surface the path on hover in the environments panel and do find it a bit noisy in the Select Interpreter drop down so if it isn't providing much value on top of what is already displayed in the name/description I would opt to not add more visual clutter.

[eleanorjboyd]

ok we can revisit later on post release or user conversations

[eleanorjboyd]

Connor's suggestion: Maybe there should be a rename action and/or the extension should automatically suffix conflicting names with a number.

[cwebster-99]

feedback from users said that in the environments panel showing the path on hover and being able to copy the path was desired. Having the path printed in grey text was noisy