github action may fail when use the [package.source] in poetry.lock

[youngquan]

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

Issue

I am from China. Because https://pypi.org/simple is too slow for me to download package, I often use a pypi mirror. I add cofigurations below to speed up:

[[tool.poetry.source]]
name = "tsinghua"
url = "https://pypi.tuna.tsinghua.edu.cn/simple/"
default = false

Recently, I have used Poetry to manage a python project named goldenmask on Github. However, because the poetry.lock file was pushed to the repository, poetry install would try to fetch packages from the pypi mirror located in China. These is unnecessary, and I have to delete the file poetry.lock and the cofigurations above, so github actions could work.

This maybe unreasonable I think, so is there a better solution for developers in China? Could someone give me some advice?

[trim21]

you can set mirror in pip config file like /etc/pip.conf in old way.

When poetry call pip to install packages, pip will try to install from mirror instead of pypi. There is no need to add source section in pyproject.toml

[youngquan]

Thanks for your reply. I have already set the global.index-url using pip config set：

$ pip config set global.index-url https://pypi.tuna.tsinghua.edu.cn/simple/
Writing to /root/.config/pip/pip.conf

$ pip config get global.index-url
https://pypi.tuna.tsinghua.edu.cn/simple/

However, when I tried to use poetry to add a package, pip was still using https://pypi.org/simple, because it was too slow to resolving dependencies.

I also tried to set mirror in pip config file like /etc/pip.conf in old way, however it still did not work:

$ cat /etc/pip.conf 
[global] 
index-url = https://pypi.tuna.tsinghua.edu.cn/simple/

Is there some way to know which pypi mirror that poetry was using? Besides, even I can set the pypi mirror, the poetry.lock would still contian information of the pypi mirror I set. I had to delete the file poetry.lock again when I was using github actions, I do not know whether this was reasonable?

Here are the version of poetry:

$ poetry --version
Poetry version 1.0.5

[trim21]

no, pip is not using pypi.

poetry is issuing http requests to pypi json api to resolve deps, that's why it's slow.

I'm not sure if poetry could use json api of mirrors, looks like it could.

I'm doing it this way but I can't find anything about my pypi mirror in my poetry.lock...

[youngquan]

So when I set pypi mirror in /etc/pip.conf, where did poetry try to resolve deps from? From https://pypi.org/simple or from https://pypi.tuna.tsinghua.edu.cn/simple/ ? If I set [[tool.poetry.source]] in pyproject.toml, it will be very fast to resolve deps !

Here is a picture show how slow the poetry is, when I did set pypi mirror in /etc/pip.conf:

I have never waited for the result, so I never saw the poetry.lock file when pypi mirror was only set in /etc/pip.conf. 😂

Meanwhile, If I set [[tool.poetry.source]] in pyproject.toml，there would be pypi mirror information in poetry.lock:

[trim21]

From pypi, because I often got requests failure exceptions showing host is pypi.
I never wait to resolve whole project, either...
I start from empty pyproject.toml and add deps one by one, to let poetry catch more and more requests.

[youngquan]

I see! So poetry use pypi json api to resolve deps, and download packages from pypi mirror in pip.conf, is that right?

Thanks for your time!

I did start from an empty pyproject.toml and add the click package 1 hours ago, poetry has not finished yet:

It is so frustrating, so I still have to set [[tool.poetry.source]] in pyproject.toml ???!!!

[NateScarlet]

Related to #1632

[sinoroc]

@youngquan There is a PR that could help solve this issue. Would you be able to test it, give feedback? #3624

[neersighted]

Closing as a specialized duplicate of #1632

[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.