Package resolution fails with private repository on 1.0.0b8

[Imaclean74]

• I am on the latest Poetry version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• [ x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: Windows 10

• Poetry version: 1.0.0b8

• happens with newly created pyproject.toml. Only change is adding the "tool.poetry.source" section with private repo.

Issue

As of release 1.0.0b8, resolution against my private repository fails with the following error. If I roll back to 0.12.17 it works again.

Error string :

HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /pypi/black/json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x000001E8EF4DED08>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))```

[Imaclean74]

so looks like its failing entirely to connect to the internal repo and falling back to the external pypi.org. I'll see if I can get more log detail. repo details in pyproject.toml look something like :

[[tool.poetry.source]]
name = "foopypi"
url = "http://pypi.site.foo.com/simple"

[Imaclean74]

update - looks like this is a duplicate of #1677

Thanks to the comment there - I'm now able to get things working by making our private repository the default. However, this is a) different to the previous behavior and b) logging doesn't indicate what's actually happene=ing. ie - global pypi is used as the default - and poetry doesn't fall back to the listed private repo.

[[tool.poetry.source]]
name = "foopypi"
url = "http://pypi.site.foo.com/simple"
default=true

[abn]

Documentation at https://python-poetry.org/docs/master/repositories/ is now updated to reflect various configuraiton options. If pypi is not expected to be queried, then default=true (disabling PyPI) is the right approach.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.