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
chore: include Python 3.11 #1602
Conversation
This will be easier after #1550, so will rebase after that. |
Codecov Report
|
This should probably be done instead of #1583 since that one doesn't add testing for 3.11, but just the new wheel builds only. |
d83a4af
to
459bf2d
Compare
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
459bf2d
to
a791612
Compare
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
e139c59
to
3703600
Compare
- uses: pypa/cibuildwheel@v2.9.0 | ||
if: matrix.os == 'ubuntu-latest' | ||
env: | ||
CIBW_BUILD: cp311-manylinux_x86_64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are hardcoding manylinux1 above, and manylinux1 doesn't support 3.11 (or 3.10, IIRC), so made this a separate step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this what becomes easier when we drop Python 3.6? I'm going to open issues for dropping 3.6 in Uproot and Awkward as a reminder.
@@ -19,6 +19,7 @@ repos: | |||
rev: v2.0.0 | |||
hooks: | |||
- id: setup-cfg-fmt | |||
args: [--include-version-classifiers, --max-py-version=3.11] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This got missed recently, you now need --include-version-classifiers
as of setup-cfg-fmt 2.
@@ -74,6 +74,7 @@ filterwarnings = [ | |||
"ignore:the imp module is deprecated in favour of importlib:DeprecationWarning", # move to importlib to fix (setuptools issue) | |||
"ignore:The NumPy module was reloaded:UserWarning", | |||
"ignore:.*np\\.MachAr.*:DeprecationWarning", # until https://github.com/numba/numba/issues/7758 is fixed | |||
"ignore:module 'sre_.*' is deprecated:DeprecationWarning", # From lark & Python 3.11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, this can also be "default", "once", or "all" if you want the warning to still show up in the tests. But they aren't really our fault so I think ignoring them is fine. But there are options.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
Similar to the last few new tests, I'll flip the switch to start requiring "3.11-dev" in about a week. On my calendar for August 31.
To be clear: this updates pybind11 on purpose, right? (I missed that when scanning over the files that have changed, since the whole submodule is one small line.) The new pybind11 commit coincides with release 2.10.0, which looks very intentional. I'll make a note in tomorrow's slides to be careful about accidentally back-porting pybind11 (and I'll be on the lookout for that, too, since it happens so easily). |
pybind11 2.10.0 is required for CPython 3.11 support, yes. |
Testing this out now that NumPy supports Python 3.11 with binary wheels.