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.

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

Adding pip check to the CI #1103

Open
benoit-cty opened this issue Jan 10, 2022 · 0 comments
Open

Adding pip check to the CI #1103

benoit-cty opened this issue Jan 10, 2022 · 0 comments

Comments

@benoit-cty
Copy link
Contributor

Hi there!

I really enjoy OpenFisca, but I recently encountered an issue.

The deps of OpenFisca are strict. If we want to be sure that they are all aligned, it could be better to check it in CI.

I discover this issue when working on #1039 as it is a check done by the conda CI.

Here is what I did:

Run pip check

Here is what I expected to happen:

No broken requirements found.

Here is what actually happened:

flake8 3.9.2 has requirement pycodestyle<2.8.0,>=2.7.0, but you have pycodestyle 2.8.0.

According to pip show pycodestyle, pycodestyle was installed for : autopep8, flake8, flake8-print

Here is data (or links to it) that can help you reproduce this issue:

No data, just a fresh install done by:

python3 -m venv .venv
source .venv/bin/activate
pip install -U pip
pip install --editable .[dev] --use-deprecated=legacy-resolver

Context

I identify more as a:

  • Developer (I create tools that use the existing OpenFisca code).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant