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

pdir: Python 3.13 #79

Closed
wants to merge 1 commit into from
Closed

pdir: Python 3.13 #79

wants to merge 1 commit into from

Conversation

supakeen
Copy link

@supakeen supakeen commented Oct 6, 2024

Adds the new attributes that were added in Python 3.13 to the test cases and the attribute lists.

Perhaps these should live in different categories?

Closes #78.

Adds the new attributes that were added in Python 3.13 to the test cases
and the attribute lists.

Perhaps these should live in different categories?

Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
@supakeen
Copy link
Author

supakeen commented Oct 6, 2024

It seems to me tests should be scoped on their expected values per Python version as they're failing on expected attributes in the tests that don't exist in the versions used for the test :(

@laike9m
Copy link
Owner

laike9m commented Oct 6, 2024

Admittedly, the tests are becoming harder and harder to maintain with each new version. Given the code seldom changes and almost never breaks, I think it makes sense to only run the tests under the current and upcoming version, to minimize the maintenance cost. In this case, it means 3.12 and 3.13.

To make the tests pass, I suggest to remove Python 3.8 - 3.11 from
https://github.com/laike9m/pdir2/blob/master/tox.ini

@laike9m
Copy link
Owner

laike9m commented Oct 6, 2024

Though, you'll still have to deal with the differences between 3.12 and 3.13, which is unavoidable. Or, you can wait for the official release of 3.13, by then I would be fine to remove 3.12 as well.

@supakeen
Copy link
Author

supakeen commented Oct 6, 2024

I'll think about the test situation a bit, the idea of only running on the latest version was also something I thought about (and didn't quite like) :)

@laike9m
Copy link
Owner

laike9m commented Oct 7, 2024

Sure, take your time

@supakeen
Copy link
Author

I saw 3.13 support got into main and a new release was pushed. I'll reconsider the testing perhaps in a separate PR.

@supakeen supakeen closed this Oct 11, 2024
@laike9m
Copy link
Owner

laike9m commented Oct 11, 2024

I should have informed you earlier but I forgot, sorry about that.

I'll reconsider the testing perhaps in a separate PR.

Really appreciate it!

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.13 support + fix broken tests
2 participants