Skip to content

Add in a constraints file for flake8.#677

Merged
clalancette merged 1 commit intomasterfrom
clalancette/constraints
Aug 3, 2022
Merged

Add in a constraints file for flake8.#677
clalancette merged 1 commit intomasterfrom
clalancette/constraints

Conversation

@clalancette
Copy link
Copy Markdown
Contributor

Signed-off-by: Chris Lalancette clalancette@openrobotics.org

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette
Copy link
Copy Markdown
Contributor Author

clalancette commented Aug 2, 2022

Rolling CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status
  • Windows Debug Build Status
  • RHEL Build Status

Foxy CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status
  • Windows Debug Build Status

@clalancette
Copy link
Copy Markdown
Contributor Author

This is an alternative to #675 , that just adds in a constraint to flake8, rather than trying to pin it. This should be the minimum we need to keep flake8 to an earlier version for now.

Copy link
Copy Markdown
Contributor

@Blast545 Blast545 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with green CI.
Context for extra reviewers: https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-c.

@clalancette clalancette marked this pull request as ready for review August 3, 2022 01:16
@clalancette
Copy link
Copy Markdown
Contributor Author

There are still a few regressions (particularly in the Windows jobs), but there are none in flake8. So I think this is doing what we want to do; I'm going to go ahead and merge it ahead of the nightlies.

@clalancette clalancette merged commit a10c486 into master Aug 3, 2022
@delete-merged-branch delete-merged-branch bot deleted the clalancette/constraints branch August 3, 2022 01:17
@wjwwood
Copy link
Copy Markdown
Member

wjwwood commented Nov 2, 2023

In the future, please print out files like the constraint.txt, it makes it kind of impossible to know what was used in a build. This file isn't reflected in the output of pip either, so without looking at this code it's hard to know what was in that file (especially if it changes over time).

Also, it's out of sync with our Windows source instructions:

http://docs.ros.org/en/rolling/Installation/Alternatives/Windows-Development-Setup.html#install-python-prerequisites

Install Python prerequisites

Install additional Python dependencies:

pip install -U colcon-common-extensions coverage flake8 flake8-blind-except flake8-builtins flake8-class-newline flake8-comprehensions flake8-deprecated flake8-docstrings flake8-import-order flake8-quotes mock mypy==0.931 pep8 pydocstyle pytest pytest-mock vcstool

@wjwwood
Copy link
Copy Markdown
Member

wjwwood commented Nov 2, 2023

I was going to open a pr to print out the file, but @clalancette do you remember if there was a reason for the file versus the inline constraints? Maybe it's not possible to do the <5.0.0 outside of the file?

@clalancette
Copy link
Copy Markdown
Contributor Author

I was going to open a pr to print out the file, but @clalancette do you remember if there was a reason for the file versus the inline constraints? Maybe it's not possible to do the <5.0.0 outside of the file?

I don't remember. I didn't actually know that you could do constraints on the command-line. I think a PR to print out the contents of constraints.txt would be fine.

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

Successfully merging this pull request may close these issues.

4 participants