Improve display names of interpreters in the list and status bar

[DonJayamanne]

The prefix 'packaged by conda-forge` should not be added to some of the interpreters.
As this belongs to the root interpreters

@brettcannon @qubitron
We'll need to go come up with a set of rules for the display names of:

• Conda, virtual, venv, and other environments.

• Create new api to retrieve interpreter details with the ability to cache it Create new API to retrieve interpreter details with the ability to cache it #1569

[DonJayamanne]

The following is a WIP:

Requirements:

• Able to identify the type of environment (whether its conda, pipenv, etc)
• Able to identify version of Python
• Able to identify name of the environment (if its a virtual environment or similar)
• Able to identify the name of the company/distro
• Consistent across all platforms
• Consider requirements of PEP 514

TBD:

• Do we care for the display of bitness information (should be easy to determine, using sys.maxsize)
• Do we need to display the type of release (e.g. if its a RC, beta etc, something other than the final release).

Propose Format

CompanyName DisplayName (EnvironmentName EnvironmentType)

Propose Sort order

• Environment + display name
  E.g.:

1. Anaconda Python 2.7.14 32Bit (base)
2. Anaconda Python 2.7.14 32Bit (env-01)
3. Anaconda Python 3.5.1 64Bit (env-02)
4. Python 2.7.14 32Bit (v01 pipenv)
5. Python 3.5.1 32Bit (v02 pipenv)
6. Python 3.5.1 32Bit (v03 pipenv)
7. Python 3.5.1 32Bit (v03 pyenv)
8. Python 3.6.1 32Bit (v03 venv)
9. Python 3.5.1 32Bit (myenv2 virtualenv)

Where:

• CompanyName is
  • The name of the company (on Windows this is retrieved from the registry PEP 514)
• DisplayName is
  • On Windows, this should be retrieved from the registry PEP 514
  • Python Major.Minor.Micro 32/64bit (for all but conda environments and non Windows OS)
    E.g. Python 2.7.14 32bit Python 3.5.1 64bit
• EnvironmentType: is one of the following
  • pipenv
  • pyenv
  • venv
  • virtualenv
    Note: conda is not included in the above list, as the company name (prefix) would be an implicit indicator of the fact that its a conda environment.

[DonJayamanne]

Added needs decision, as @qubitron is working on the display format.
I'm currently working on laying the foundation work to make the above possible (i.e. ensure we have all necessary bits of information to build the display value).

[DonJayamanne]

Agreed display is as follows:
Sort order = Version number

Anaconda Python 2.7.14 32-bit (base)
Anaconda Python 2.7.14 32-bit (env-01)
Anaconda Python 3.5.1 64-bit (env-02)
Python 2.7.14 32-bit (v01 pipenv)
Python 3.5.1 32-bit (v02 pipenv)
Python 3.5.1 32-bit (v03 pipenv)
Python 3.5.1 32-bit (v03 pyenv)
Python 3.6.1 32-bit (v03 venv)
Python 3.5.1 32-bit (myenv2 virtualenv)

[brettcannon]

What are the parts of (v03 venv)? Is that directory name and type? Should we separate those out more clearly as that will get confusing when the directory has a space, e.g. (some bunk venv)?

And do we want x86/x64 instead of 32-bit/64-bit for any reason other than it's shorter? 😉

[DonJayamanne]

(v03 venv)

v03 - environment name
venv - tool used to create environment (or environment type).

confusing when the directory has a space, e.g. (some bunk venv)?

Agreed. How about using double quotes when necessary?

And do we want x86/x64

Good idea. I went with the later as that's what is returned by python (when using --version).

[brettcannon]

Maybe ("some bunk" / venv)? ("some bunk": venv)?

[DonJayamanne]

@qubitron thoughts.

[qubitron]

What about (some bunk: venv)? Double quotes look noisy, and the colon to me says "some bunk is a venv".

[brettcannon]

Could also be single quotes: ('some bunk': venv). But since macOS 9 is no longer a thing we can probably get away with it not confusing people as to where the directory name ends. 😉

[DonJayamanne]

Note:
Registry information is not to be used for display names. See issue #2219

[DonJayamanne]

Updated label to Bug as this resolves issue #2219

[ericsnowcurrently]

I've verified that the interpreter/env list is formatted in the new way. However, there might be something wrong. Some of the entries don't have the right info:

Python 2.7.15 64-bit (usr: virtualEnv)
  /usr/bin/python
Python 3.5.2 64-bit
  /usr/bin/python3.5
Python 3.6.5 64-bit (.miniconda3: conda)
  ~/.miniconda3/bin/python
Python 3.6.5 64-bit (usr: virtualEnv)
  /usr/bin/python3
Python 3.7.0 64-bit (test env: conda)
  ~/.miniconda3/envs/test env/bin/python
Python 3.7.0 64-bit
  /usr/bin/python3.7
Python 3.7.0 64-bit (test_env: venv)
  ~/.envs/test_env/bin/python

Note the (usr: virtualEnv) entries. IIRC, those were previously standalone entries (like 3.5 and 3.7 are). Furthermore, I don't have any virtualenv environments.

Perhaps this is related to a different issue, but I noticed it here at least. :)

[ericsnowcurrently]

Things look good now. "System" interpreters are shown correctly and pyenv showed up right.

[d3r3kk]

(Tested as well, looks great)

[qubitron]

Looks good with the following changes:

• virtualEnv -> virtualenv
• venv space -> 'venv space'