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

#12056 Update dis.findlinestarts for Python 3.13 #12059

Merged
merged 10 commits into from
Feb 1, 2024

Conversation

adiroiban
Copy link
Member

@adiroiban adiroiban commented Dec 20, 2023

Scope and purpose

Fixes #12056

This updates the usage of dis.findlinestarts.

The Python 3.13 tests are cherry picked to be executed.
Later we can enable more.

As a drive-by, update GitHub Actions Python helper to the latest version.

@adiroiban adiroiban changed the title #12056 Fix int and None comparison for Python 3.13 #12056 Update dis.findlinestarts for Python 3.13 Dec 21, 2023
@adiroiban
Copy link
Member Author

This is ready for review, but before reviewing this, please take a look at #12058

Once we remove the cgi dependency, we can "unlock" many more tests on Python 3.13

needs-review

@@ -0,0 +1 @@
Update `int` and `None` comparisons as required by Python 3.13.
Copy link
Member

Choose a reason for hiding this comment

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

Seems like a minor change. As a user, what would this mean to me? Just some internal implementation details. "Support Python 3.13" will be a more interesting news fragment, when we get there. :)

Copy link
Member Author

Choose a reason for hiding this comment

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

True. Thanks. This info is wrong.

The change is in the way we use the result of findlinesstarts as mentioned in the title of this pr.

I converted this to a misc.

@adiroiban adiroiban requested a review from a team January 30, 2024 16:14
@befeleme
Copy link

I can confirm that using this patch on our attempted build for Fedora Linux makes all of the failures with builtins.TypeError: '<' not supported between instances of 'NoneType' and 'int' go away - the tests pass again.

tox-env: 'mindeps-nocov-posix'
job-name: 'mindeps-nocov-3.13'
skip-coverage: yes
# FIXME:https://github.com/twisted/twisted/issues/12060
Copy link
Contributor

Choose a reason for hiding this comment

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

I can confirm that this change works with my changes in #12061, allowing tests in twisted.internet to pass on Python 3.13 (excluding those that require cffi and other yet-unsupported dependencies).

@adiroiban
Copy link
Member Author

Thanks for your reviews.

@exarkun I have updated the release notes and automated tests so that we can have part of the curren test running on 3.13.

Do you have time to take another look at this?

With future PRs we can enable more tests.

I think is important to have this merged as the base for future py3 changes.

@adiroiban adiroiban merged commit 40ca8d0 into trunk Feb 1, 2024
24 checks passed
@adiroiban adiroiban deleted the 12056-none-and-int-comparision branch February 1, 2024 01:47
@adiroiban
Copy link
Member Author

Many thanks for your reviews. I have merged this.
Now, when we work in Python 3.13 PR we can enable the test for the parts that were fixed.

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.

Update for Python 3.13 builtins.TypeError: '<' not supported between instances of 'NoneType' and 'int'
5 participants