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

support python3.12 #2290

Closed
wants to merge 1 commit into from
Closed

Conversation

branchvincent
Copy link

@branchvincent branchvincent commented Feb 5, 2024

Python 3.12 has removed its bundled setuptools (aka pkg_resources): https://docs.python.org/3.12/whatsnew/3.12.html#removed

Summary by CodeRabbit

  • Refactor
    • Improved plugin handling and version information retrieval in slither-analyzer, ensuring compatibility with Python 3.10.
    • Replaced pkg_resources with importlib.metadata for handling entry points and version information retrieval.
    • Updated the output_to_sarif function to use metadata instead of require.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

coderabbitai bot commented Feb 5, 2024

Walkthrough

The recent update in the slither project involves transitioning from using pkg_resources to importlib.metadata for managing entry points, fetching version information, and enhancing the output_to_sarif function within the analyzer. This modification not only ensures compatibility with Python 3.10 but also optimizes plugin handling and streamlines the process of retrieving version details for slither-analyzer.

Changes

Files Change Summary
slither/__main__.py
slither/utils/output.py
Updated to use importlib.metadata for entry points, version info retrieval, and enhanced output_to_sarif function.

🐇✨
In the realm of code, a change took flight,
From pkg_resources to metadata bright.
Slither through code, with ease now we might,
A rabbit's cheer for progress in sight. 🎉
🌟🐰

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>.
    • Generate unit-tests for this file.
  • 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 tests 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 generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

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.

Review Status

Actionable comments generated: 3

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between e3dcf1e and 93cbf7d.
Files selected for processing (2)
  • slither/main.py (3 hunks)
  • slither/utils/output.py (2 hunks)

@@ -161,7 +160,7 @@ def output_to_sarif(
"driver": {
"name": "Slither",
"informationUri": "https://github.com/crytic/slither",
"version": require("slither-analyzer")[0].version,
"version": metadata.version("slither-analyzer"),
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure that metadata.version("slither-analyzer") is wrapped in a try-except block to handle PackageNotFoundError in case the package is not found.

Comment on lines 168 to 174
if sys.version_info >= (3, 10):
entry_points = metadata.entry_points(group="slither_analyzer.plugin")
else:
from pkg_resources import iter_entry_points
entry_points = iter_entry_points(group="slither_analyzer.plugin", name=None)

Copy link
Contributor

Choose a reason for hiding this comment

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

Consider simplifying the conditional import logic for entry_points by directly using metadata.entry_points(group="slither_analyzer.plugin"), as the minimum supported Python version is now 3.10.

@@ -297,7 +302,7 @@ def parse_args(
parser.add_argument(
"--version",
help="displays the current version",
version=require("slither-analyzer")[0].version,
version=metadata.version("slither-analyzer"),
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure that metadata.version("slither-analyzer") is wrapped in a try-except block to handle PackageNotFoundError in case the package is not found.

@elopez elopez linked an issue Feb 5, 2024 that may be closed by this pull request
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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between e3dcf1e and 410119a.
Files selected for processing (2)
  • slither/main.py (3 hunks)
  • slither/utils/output.py (2 hunks)
Files skipped from review as they are similar to previous changes (2)
  • slither/main.py
  • slither/utils/output.py

@0xalpharush 0xalpharush requested a review from elopez February 5, 2024 04:39
Copy link
Member

@elopez elopez left a comment

Choose a reason for hiding this comment

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

Thanks for the PR @branchvincent! This looks good!

NB @0xalpharush I have not manually confirmed if the plugin system remains working on 3.10+ and I don't think we have an automated test for that.

@@ -166,7 +165,14 @@ def get_detectors_and_printers() -> Tuple[
printers = [p for p in printers_ if inspect.isclass(p) and issubclass(p, AbstractPrinter)]

# Handle plugins!
for entry_point in iter_entry_points(group="slither_analyzer.plugin", name=None):
if sys.version_info >= (3, 10):
entry_points = metadata.entry_points(group="slither_analyzer.plugin")
Copy link
Member

Choose a reason for hiding this comment

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

It may be possible to use this implementation in 3.8+ as well if we added a dependency on importlib_metadata >= 3.6 and imported metadata through it.

@0xalpharush
Copy link
Contributor

We should update this to run 3.8 and 3.12 on every PR and run 3.8-3.12.

python: ${{ (github.event_name == 'pull_request' && fromJSON('["3.8", "3.11"]')) || fromJSON('["3.8", "3.9", "3.10", "3.11"]') }}

@0xalpharush
Copy link
Contributor

@branchvincent Would you be willing to sign the CLA please?

@0xalpharush
Copy link
Contributor

@branchvincent bump

@0xalpharush
Copy link
Contributor

@elopez I guess we are going to have to reopen this ourselves since the OP is unresponsive

@branchvincent
Copy link
Author

branchvincent commented Feb 16, 2024

sorry about that, I have to check with my employer before signing the CLA. alternatively, I'm more than happy for you to just create the same PR

@0xalpharush
Copy link
Contributor

replaced by #2348

@0xalpharush 0xalpharush closed this Mar 1, 2024
@branchvincent branchvincent deleted the python3.12 branch March 4, 2024 03:47
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.

python3.12 support is broken
4 participants