Enable the additional flake8-bugbear warnings.
See https://github.com/PyCQA/flake8-bugbear for the list of warnings.

Tim Adye authored 1 year ago and Johannes Elmsheuser committed 1 year ago

change VS Code cppStandard to C++20

Tadej Novak authored 1 year ago and Edward Moyse committed 1 year ago

Add autopep8 support to Athena

Stefan Richter authored 1 year ago and Frank Winklmeier committed 1 year ago

Projects: update flake8 error codes

See merge request atlas/athena!62346

(cherry picked from commit a06da341)

eea12b32 Projects: update flake8 error codes

The latest flake8 version seems to treat enabling of extensions
differently. Need to go back to explicitly enable `ATL902` (Copyright
check) again. Also add `--isolated` to make sure no other configuration
files are read.

- Remove obsolete ATL238 (Py2to3 migration).
- Move ATL902 from `--enable-extensions` to `--select`, which has the
  same effect (flake8 always gives priority to the most specific error
  code from the select/ignore lists).

Factor common code used by std and LRT egamma config. Reduce LRT config log verbosity. Some flake8 related stylistic fixes

Factor common code used by std and LRT egamma config. Reduce LRT config log verbosity. Some flake8 related stylistic fixes

Unfortunately they don't seem to make a difference. :-( Apparently these
settings can only be done globally by the user, they can't be done
on a per-project level...

Still, for reference, it seems to be a good idea to keep these settings
in the repository as well.

This is just to help the CI system to categorise merge requests that touch
files in these directories.

Attila Krasznahorkay authored 5 years ago and Frank Winklmeier committed 5 years ago

The idea is that for VS Code based development we should rely on
the container capabilities of the editor. Letting it create a terminal
for us that we could compile code in, while relying on the files
and environment created inside the container, to interpret our code.

In order for VS Code to parse our code correctly, it has to be told
explicitly how each source file needs to be compiled. (Otherwise it would
not find the headers from LCG/TDAQ/Gaudi to interpret our code.) This
update makes sure that when the user sets up the build of the
WorkDir project in the "usual layout", in a directory called build/
just beside the athena/ directory, VS Code would automatically find
the correct compile_commands.json file that it needs, when the user
opens the athena/ directory for editing.