should readthedocs.yml have a pip version setting?

[caganze]

Hi,

This is the message that I get while trying to build
"You should consider upgrading via the 'pip install --upgrade pip' command", do I have control over this?

Thank you,

[RichardLitt]

I believe you should have control over this. Could you try running this command locally, and then seeing if the message comes up when you build again?

[stsewd]

The pip version comes from the docker image used to build the docs. See #4127 (comment) (closing in favor of the other issue).

[ltalirz]

@stsewd I'm not sure (closed) issue #4127 really covers this issue.

For example, my problem is that I need pip >= 10 in order to build my package.
However, including pip>=10 in the requirements.txt does not solve this issue, since the newer pip version is required already at install time (see failed build here ).

In essence, being able to specify the pip version would allow to use a pyproject.toml with pip >= 10.

Is there currently a way to upgrade pip before it tries installing the requirements.txt?

P.S. I tried wiping the environment as suggested in #4127 but this does not upgrade pip to >= 10.

[stsewd]

@ltalirz Currently there is no way to do that, we need to wait for the next release of the rtd docker image which should include a more recent version of pip.