[[tool.poetry.source]] setting is ignored

• [x ] I am on the latest Poetry version.
• [ x] I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name:
• Poetry version: 1.1.4
• Link of a Gist with the contents of your pyproject.toml file:

Issue

I’m in china mainland and speed to access pypi is very slow, so I have added tool.poetry.source to a local source:

[[tool.poetry.source]]
name = "ali"
url = "https://mirrors.aliyun.com/pypi/simple/"

However, this one works for my one project yesterday, it doesn’t work for my another project, checked today.

When it works, I found poetry will check both pypi and this local source for index, but only download package from local source, this can enhance speed a lot. However, it seems not work today, it always check index and download package from pypi, the local source is totally ignored.

if poetry is downloading from local source(which is ali in the case), it’ll show source’s name before ‘:’. it’s pypi here since it downloads from pypi.

I have recreated my virtual env and delete pypoetry’s cache.

[GooseYArd]

after some debugging, I found that if “[[tool.poetry.source]]” precedes “[tool.poetry.scripts]” in pyproject.toml, then as early as PyProjectTOML.data(), self._data[“tool”][“poetry”] will be absent a “source” key. However, if I move tool.poetry.source below tool.poetry.scripts in the file, this problem doesn’t occur.

I’m not sure if the issue is my ignorance of toml or an issue with tomlkit, but will do a little more debugging to see if I can spot the root cause.

[zillionare]

As I’m using poetry more and more, I might found clue leading to my issues (I haven’t been through this for months).

At time when the issue reported, I think we’re going though pip’s upgrade; and there’s sync issue between central repo (pypi) and its mirrors (for example, aliyun in my case). According to my observation, the sync may take several days.

As more and more python libraries manage dependancy with poetry, I found now dep resolution time is decreased, so a second source is not required (it’s worth some time to resolve deps use central repo, other than mirrors).

If you still experiece slow resolution, maybe you could try resolve your project.toml on a machine located at us cloud service. I did that several times months ago.

close this one since I didn’t expierence issues anymore, and I think it’s probably resolved