Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FIX] Make Python version explicit in pre-commit workflow #196

Closed
wants to merge 1 commit into from
Closed

[FIX] Make Python version explicit in pre-commit workflow #196

wants to merge 1 commit into from

Commits on May 10, 2023

  1. [FIX] Make Python version explicit in pre-commit workflow 

    Recently (or recently enough that I've just begun noticing it), the
nodeenv dependency had troubles installing. Sometimes. It wasn't very
reliably failing.

This is related to <ekalinin/nodeenv#328>.

By explicitly setting the Python version to something <=3.10, we can
safely pretend the problem doesn't exist.

Ideally the Python versions match up to the ones used in test.yml, but
they don't, and I fear it might be too intrusive to fix that in this
commit.

Signed-off-by: Carmen Bianca BAKKER <carmen@coopiteasy.be>
    @carmenbianca
    carmenbianca committed May 10, 2023
    Configuration menu
    Copy the full SHA
    24906ec View commit details
    Browse the repository at this point in the history