Fatal Internal error while trying to unset configuration

[TorstenRobitzki]

Environment

• pip version: 20.3.3
• Python version: 3.9.0
• OS: OS/X 10.15.7

I'm using pyenv. I'm not an active Python developer, so please bear with me if I'm missing important details.

Description
I try to remove the "global.extra-index-url" key from the pip configuration by:

`pip config unset global.extra-index-url`

Which then responses with:

`ERROR: Fatal Internal error [id=1]. Please report as a bug.`

Expected behavior

I would expect to either remove the key or to prompt an error message that I could use to investigate into the reason of the failing of the command.

How to Reproduce
Sorry, I don't have any clue, how this could be reproduced.

Output

% pip config unset global.extra-index-url 
ERROR: Fatal Internal error [id=1]. Please report as a bug.

Maybe the current value of the configuration gives a clue (some values slightly changed):

% pip config list
global.extra-index-url='\nhttps://torsten:keykeykeykey@customer.jfrog.io/customer/api/pypi/    https://customer.jfrog.io/customer/api/pypi/customer-pip3-stable/simple\nhttps://pypi.python.org/simple/'

There was a similar issue reported last year: #6940 Unfortunately, the issue was closed without giving and hint to how it was resolved.

[uranusjr]

cc @dinko-pehar (who opened #6940)

[pradyunsg]

This probably has something to do with the fact that this is a multi-value property.

[TorstenRobitzki]

My workaround was, to edit ~/.pip/pip.conf and to remove that line with an editor.

[amaank404]

is there a verbose option, you should have tried that

[NoahGorny]

I am unable to reproduce

[pradyunsg]

Ditto. I'm not able to reproduce this either?

[TorstenRobitzki]

I got into the situation by following the instructions of a colleague to edit ~/.pip/pip.conf and to insert something like this:

[global]
    extra-index-url =
        https://google.de
        https://pypi.python.org/simple/

If I set the config file to this content, I get reproducible the above error message.

[tnielens]

I do reproduce similar issues. I suspect it's related to the legacy configuration path ~/.pip/pip.conf. Moving the file to the new default path ~/.config/pip/pip/conf solves the issue.

[wimglenn]

I also got there. Not sure how.

$ pip --version
pip 22.0.4 from /private/tmp/v/.venv/lib/python3.10/site-packages/pip (python 3.10)
$ pip config debug
env_var:
env:
global:
  /Library/Application Support/pip/pip.conf, exists: False
site:
  /private/tmp/v/.venv/pip.conf, exists: True
    global.index-url: http://localhost:8080/
user:
  /Users/wim/.pip/pip.conf, exists: False
  /Users/wim/.config/pip/pip.conf, exists: False
$ cat .venv/pip.conf 
[global]
index_url = http://localhost:8080/

$  v pip config unset global.index-url    
ERROR: Fatal Internal error [id=1]. Please report as a bug.
$ pip config unset global.index-url -vvvv
Skipping file '/Library/Application Support/pip/pip.conf' (variant: global)
Skipping file '/Users/wim/.pip/pip.conf' (variant: user)
Skipping file '/Users/wim/.config/pip/pip.conf' (variant: user)
For variant 'site', will try loading '/private/tmp/v/.venv/pip.conf'
Will be working with site variant only
ERROR: Fatal Internal error [id=1]. Please report as a bug.