Skip to content

Incorrect error message when a specific Python version requires a downlevel pip #643

Description

@dirkf

Description:

actions/setup-python logs an error, as shown below, on installing a specific Python version that is not supported by the latest pip. For example, Python 3.5.x requires pip < 21. Since the version of Python was specified and the correct pip was ensured, the older pip version is expected and not an error.

Even if a newer pip were available, this should be an informational or warning message.

See also #233.

Action version:

v4 and earlier

Platform: (probably irrelevant)

  • Ubuntu
  • macOS
  • Windows

Runner type: (probably irrelevant)

  • Hosted
  • Self-hosted

Tools version:

A version that doesn't support the latest pip, eg 3.5.x.

Repro steps:

Use actions/setup-py to install a specific Python version that doesn't support the latest pip, eg 3.5.x. Eg, https://github.com/ytdl-org/youtube-dl/actions/runs/4624273941/jobs/8178946389.

Expected behavior:

The specified Python version should be installed with the latest version of pip for that version.

Actual behavior:

This output is generated:

[error]You are using pip version 20.3.4, however version 23.0.1 is available.

Python 3.5.x is not supported by pip > 20.3.4, so this is correct behaviour and not an [error].

Activity

  1. dirkf commented on Apr 6, 2023

    @dirkf
    Author

    Apparently there is a dependency on python-versions where older versions of Python need to be rebuilt. Meanwhile, or in any case, there are environment variables that should be used in the setup script.

  2. dmitry-shibanov commented on Apr 7, 2023

    @dmitry-shibanov
    Contributor

    Hello @dirkf. Thank you for your report. We'll investigate the issue.

  3. dmitry-shibanov commented on May 8, 2023

    @dmitry-shibanov
    Contributor

    Hello @dirkf. Sorry for the late response. I've checked build and previous reply. I think it will be better to set up environment variables on the job level because it comes from the pip directly. Besides, possibly some users will need this messages.

    For now I'm going to close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions