Ensurepip: for the present, I am willing to assume that is pip imports, it is ready to go.

try: import pip
except ImportError: <ask whether to install>

Testing: testing that runpip works will initially be done by running the app on our live systems.  For automated testing of the gui, runpip should be replaced with a mock that looks up a response string in a dictionary of argument-response pairs.  The response string should have the same format as pip responses, though they will usually be shorted.  For instance, the dummy 'machine' might have only two packages.  The description might be 'Description of package x' as that would be enough to test that a description is displayed when a line is double clicked.

In the last week, I have learned more about how to write functional tests for a GUI.  I will try to do one soon for IDLE.

Upendra: tem_pip_v3.py runs as I believe you intended from command line.  The details will need a scroll bar.

When run from Idle editor on my machine, it behaves strangely.  first, it restarts in a new shell window instead of the existing one.  This is wrong and I have not seen it before.  I have not yet figured out why.

Next, a blank console window appears before the tkinter gui window and disappears when the tkwindow appears.  Ditto. When an entry is double-click, a console window is opened and closed and no details are displayed.  Changing ["pip"] to ["pythonw", "-m", "pip"] fixes these issues.

The _get_data function is not needed for tests that I can think of.  Please remove debug prints and the 'are you sure you want to quit' box.

Eric: the vscroll is on a row above the Treeview.  Give explicit row and column for each grid call, and group together the grid calls for a given frame.