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

Update ci configuration to use supported python version #51

Merged
merged 6 commits into from
Feb 26, 2025
Merged

Conversation

mtreinish
Copy link
Member

The repo hasn't been updated in some time as the tests were working as-is. But in the meantime the CI configuration has bitrotted slightly. The tests are all built around using python 3.8 which is now unsupported both by qiskit and cPython. This commit updates the configuration to fix this and unblock CI.

The repo hasn't been updated in some time as the tests were working
as-is. But in the meantime the CI configuration has bitrotted slightly.
The tests are all built around using python 3.8 which is now unsupported
both by qiskit and cPython. This commit updates the configuration to fix
this and unblock CI.
from qiskit_neko.version import __version__
from qiskit_neko.version import __version__ as __version__
Copy link
Member

Choose a reason for hiding this comment

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

?

Copy link
Member Author

@mtreinish mtreinish Feb 26, 2025

Choose a reason for hiding this comment

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

This was the only ruff error after moving off of pylint (which was causing the install issues). It said either do this or add __all__ and put __version__ in it.

Copy link
Member

Choose a reason for hiding this comment

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

that's a pretty stupid lint rule, but ok haha

Copy link
Member

Choose a reason for hiding this comment

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

I guess it wasn't doing anything, but did you mean to delete it?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, as part of removing unnecessary requirements I removed it along with the reno dev requirement.

Copy link
Collaborator

Choose a reason for hiding this comment

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

if it wasn't doing anything I am in favor of deleting it

@mtreinish mtreinish merged commit 4e7ebd0 into main Feb 26, 2025
10 checks passed
@mtreinish mtreinish deleted the revive-ci branch February 26, 2025 16:03
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.

3 participants