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

Support python 3.11 #1560

Closed
natestemen opened this issue Oct 19, 2022 · 7 comments · Fixed by #1663
Closed

Support python 3.11 #1560

natestemen opened this issue Oct 19, 2022 · 7 comments · Fixed by #1663
Labels
infrastructure For issues related to building, packaging, and continuous integration.

Comments

@natestemen
Copy link
Member

It's supposed to arrive in 5 days (schedule). There are some serious speed improvements.

@natestemen natestemen added the infrastructure For issues related to building, packaging, and continuous integration. label Oct 19, 2022
@nathanshammah
Copy link
Member

+1 for supporting this, and indeed it's been released.

@natestemen
Copy link
Member Author

This seems to be blocked until oqpy loosens dependency requirements, which they are planning to release this week: openqasm/oqpy#19 (comment)

@karalekas
Copy link
Member

@natestemen OQpy v0.1.2 has been released: https://pypi.org/project/oqpy/

@natestemen
Copy link
Member Author

Thanks Peter for letting us know! I've opened a PR on braket to loosen the oqpy dependency requirement so we don't have to do this tango so often. Hopefully we can work something out. Once that (or something similar) is merged, we can move forward on this.

@karalekas
Copy link
Member

I doubt they'll elect to fully unpin OQpy as it's such a critical dependency for the Braket SDK. There shouldn't need to be much of a tango after this though? Supporting a new Python version only happens once a year

@natestemen
Copy link
Member Author

I doubt they'll elect to fully unpin OQpy as it's such a critical dependency for the Braket SDK.

Yeah, that makes sense. I'll see what they recommend. Maybe there's an acceptable range. If not, it's not a problem, but 2 weeks ago I bumped the oqpy version in braket (PR) after the numpy and openpulse versions were loosed (in oqpy) as that was blocking us from upgrading to the latest version of braket.

This is the "tango" of dependency resolution that I referred to. You're right, hopefully this will be smoother going forward.

@natestemen natestemen added monitor-for-external-solution Tracking issues caused by external packages and removed monitor-for-external-solution Tracking issues caused by external packages labels Dec 2, 2022
@natestemen
Copy link
Member Author

#1626 has been merged, and this should be ready to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure For issues related to building, packaging, and continuous integration.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants