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

feat: remove python 3.8 support #197

Merged
merged 4 commits into from
Dec 5, 2024
Merged

feat: remove python 3.8 support #197

merged 4 commits into from
Dec 5, 2024

Conversation

nh13
Copy link
Member

@nh13 nh13 commented Dec 5, 2024

No description provided.

Copy link

codecov bot commented Dec 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.91%. Comparing base (4feb697) to head (cdab3cb).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #197      +/-   ##
==========================================
+ Coverage   89.78%   89.91%   +0.13%     
==========================================
  Files          18       18              
  Lines        2222     2222              
  Branches      493      321     -172     
==========================================
+ Hits         1995     1998       +3     
- Misses        149      150       +1     
+ Partials       78       74       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@clintval clintval left a comment

Choose a reason for hiding this comment

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

If you have the time to comment I'm curious why the bump and pin to the Ubuntu versions in all our GitHub runners? Is there a reason not to use latest any longer?

pyproject.toml Outdated Show resolved Hide resolved
Co-authored-by: Clint Valentine <[email protected]>
@nh13 nh13 marked this pull request as ready for review December 5, 2024 18:23
@nh13 nh13 requested a review from tfenne as a code owner December 5, 2024 18:23
@@ -9,10 +9,10 @@ permissions:

jobs:
testing:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

See: #196

Copy link
Contributor

coderabbitai bot commented Dec 5, 2024

Walkthrough

The pull request includes several updates across multiple files. The GitHub Actions workflow for the Python package has been modified to run on Ubuntu 24.04 and now supports Python versions 3.9, 3.10, 3.11, and 3.12, excluding Python 3.8. Similarly, the Read the Docs workflow has been updated to run on Ubuntu 24.04. The README.md file has been updated to reflect a new Python version requirement of 3.9, replacing the previous requirement of 3.8.

In the fgpyo/util/inspect.py file, the __dataclasses_fields__ attribute type has been changed to allow for any type of field in dataclasses, enhancing type specificity. The mkdocs.yml file has seen updates to the plugins section, including new configurations for the autorefs and gen-files plugins, which improve documentation generation. Lastly, the pyproject.toml file has updated the Python version requirement to 3.9 and adjusted the mypy configuration to align with this change. No other alterations to public entities were made across these files.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)
README.md (1)

40-40: Use heading instead of bold

Replace bold syntax with heading for better document structure.

-**Requires python 3.9+**
+## Requirements
+
+Requires Python 3.9+
🧰 Tools
🪛 Markdownlint (0.35.0)

40-40: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

pyproject.toml (2)

Line range hint 31-35: Remove redundant numpy version constraint.

The python = "<3.9" constraint can be removed as the project now requires Python ≥3.9.

numpy = [
  {version = "^1.26.4", python = ">=3.12"},
-  {version = "^1.25.2", python = ">=3.9,<3.12"},
-  {version = "^1.24.4", python = "<3.9"}
+  {version = "^1.25.2", python = "<3.12"}
]

Line range hint 89-89: Update ruff target-version to py39.

Ruff configuration should match the new minimum Python version requirement.

-target-version = "py38"
+target-version = "py39"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4feb697 and cdab3cb.

⛔ Files ignored due to path filters (1)
  • poetry.lock is excluded by !**/*.lock
📒 Files selected for processing (6)
  • .github/workflows/pythonpackage.yml (1 hunks)
  • .github/workflows/readthedocs.yaml (1 hunks)
  • README.md (2 hunks)
  • fgpyo/util/inspect.py (2 hunks)
  • mkdocs.yml (1 hunks)
  • pyproject.toml (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .github/workflows/readthedocs.yaml
🧰 Additional context used
🪛 Markdownlint (0.35.0)
README.md

40-40: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🔇 Additional comments (6)
mkdocs.yml (1)

16-17: LGTM: Documentation enhancement

Autorefs configuration improves reference resolution.

.github/workflows/pythonpackage.yml (1)

12-12: Verify dependency compatibility

Workflow updates match PR objective. Verify all dependencies support Python 3.9+.

Also applies to: 15-15

✅ Verification successful

Dependencies compatible with Python 3.9+ confirmed

Project's pyproject.toml specifies Python ">=3.9.0,<4.0" with compatible dependency versions:

  • numpy: version matrix covers 3.9-3.12
  • typing_extensions: properly constrained for <3.12
  • All other dependencies have no version conflicts
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check dependencies in poetry.lock for Python version compatibility
poetry show | grep -E "requires.*python"

Length of output: 139


Script:

#!/bin/bash
# Check requirements.txt or setup.py for Python version requirements
fd "requirements.txt|setup.py|pyproject.toml" --type f --exec cat {}

Length of output: 2835

README.md (1)

51-51: LGTM: Version requirement update

Conda command correctly updated to Python 3.9.

pyproject.toml (1)

26-26: LGTM: Python version requirement updated correctly.

fgpyo/util/inspect.py (2)

74-76: LGTM: Type hint update is correct.

The Field[Any] type hint is more precise for Python 3.9+.


460-460: LGTM: Type ignore comment is appropriate.

The type ignore for operator is necessary for Python 3.9+ type checking.

@nh13 nh13 merged commit 017dbc2 into main Dec 5, 2024
8 checks passed
@nh13 nh13 deleted the feat/remove-py38-support branch December 5, 2024 18:31
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.

2 participants