Skip to content

gaudi: remove the py-qmtest dependency#38274

Merged
alalazo merged 2 commits intospack:developfrom
jmcarcell:gaudi-qmtest
Jun 12, 2023
Merged

gaudi: remove the py-qmtest dependency#38274
alalazo merged 2 commits intospack:developfrom
jmcarcell:gaudi-qmtest

Conversation

@jmcarcell
Copy link
Copy Markdown
Contributor

It hasn't been a dependency for many years (~6), since around version 27 which we don't even build. Also py-qmtest is unmaintained (last change happened in 2011) and it doesn't build with recent versions of python (see #38253) so it would definitely be better not to keep it around

@jmcarcell
Copy link
Copy Markdown
Contributor Author

@spackbot fix style

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Jun 8, 2023

Let me see if I can fix that for you!

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Jun 8, 2023

I was able to run spack style --fix for you!

spack style --fix
==> Running style checks on spack
  selected: isort, black, flake8, mypy
==> Modified files
  var/spack/repos/builtin/packages/gaudi/package.py
==> Running isort checks
  isort checks were clean
==> Running black checks
reformatted var/spack/repos/builtin/packages/gaudi/package.py
All done! ✨ 🍰 ✨
1 file reformatted.
  black checks were clean
==> Running flake8 checks
  flake8 checks were clean
==> Running mypy checks
Success: no issues found in 577 source files
  mypy checks were clean
==> spack style checks were clean
Keep in mind that I cannot fix your flake8 or mypy errors, so if you have any you'll need to fix them and update the pull request. If I was able to push to your branch, if you make further changes you will need to pull from your updated branch before pushing again.

I've updated the branch with style fixes.

@alalazo alalazo self-assigned this Jun 12, 2023
@alalazo alalazo merged commit ef4b35e into spack:develop Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants