chore: CI after merging into main, add pyton 3.13, update README#24
Merged
Conversation
CI is currently only run on PRs. However, it is a good practice to also run CI on `main` after merging to make sure that checks on `main` always pass. I also added Python 3.13 to the `python-version`s in the workflows - I don't see a reason why we wouldn't support 3.13.
This adds shields to the README that show supported python versions and the status of our github workflows. The shields are currently grayed out, but once this PR is merged, they will be show how the workflows on the `main` branches did. I gave the README another sturcture, it now starts with a tl;dr section at the very top. I also added a minimal example right to the README - I find that nice, a lot of people won't click any links to example notebooks. I also added a section for citing the paper.
philipp-jung
changed the title
chandlerNick
approved these changes
Jan 2, 2026
chandlerNick
left a comment
chandlerNick
left a comment
Contributor
There was a problem hiding this comment.
I think this is good. The addition of CI after merging makes sense and python 3.13 should be supported as long as the tests pass.
se-jaeger
added a commit
that referenced
this pull request
Jan 19, 2026
I addition to #24, this one adds full support for python 3.13 and python 3.14 and drops support for 3.9 (because it is EOL). Pandas is now supports up to python 3.14, which was the blocker for supporting these version in `tab-err`. See: - https://pyreadiness.org/3.9/ - https://pyreadiness.org/3.13 - https://pyreadiness.org/3.14 --------- Signed-off-by: Sebastian Jäger <git@sebastian-jaeger.me>
philipp-jung
pushed a commit
that referenced
this pull request
Jan 19, 2026
I addition to #24, this one adds full support for python 3.13 and python 3.14 and drops support for 3.9 (because it is EOL). Pandas is now supports up to python 3.14, which was the blocker for supporting these version in `tab-err`. See: - https://pyreadiness.org/3.9/ - https://pyreadiness.org/3.13 - https://pyreadiness.org/3.14 --------- Signed-off-by: Sebastian Jäger <git@sebastian-jaeger.me>
philipp-jung
pushed a commit
that referenced
this pull request
Jan 19, 2026
I addition to #24, this one adds full support for python 3.13 and python 3.14 and drops support for 3.9 (because it is EOL). Pandas is now supports up to python 3.14, which was the blocker for supporting these version in `tab-err`. See: - https://pyreadiness.org/3.9/ - https://pyreadiness.org/3.13 - https://pyreadiness.org/3.14 --------- Signed-off-by: Sebastian Jäger <git@sebastian-jaeger.me>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI is currently only run on PRs. However, it is a good practice to also run CI on
mainafter merging to make sure that checks onmainalways pass.I also added Python 3.13 to the
python-versions in the workflows - I don't see a reason why we wouldn't support 3.13.