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

Add Python 3.12/3.13 support for connector proxy #2104

Merged
merged 1 commit into from
Oct 9, 2024
Merged

Add Python 3.12/3.13 support for connector proxy #2104

merged 1 commit into from
Oct 9, 2024

Conversation

jbirddog
Copy link
Contributor

@jbirddog jbirddog commented Oct 9, 2024

Bumps spiffworkflow-proxy and ups the docker image to 3.12.

Summary by CodeRabbit

  • Chores
    • Updated the base image in the Dockerfile to a newer version for improved performance.
    • Standardized formatting of the connector-aws dependency in the project configuration file.

Copy link
Contributor

coderabbitai bot commented Oct 9, 2024

📝 Walkthrough

Walkthrough

The pull request includes updates to the Dockerfile and pyproject.toml for the connector-proxy-demo project. The Dockerfile has been modified to use a newer Python base image, changing from python:3.11.6-slim-bookworm to python:3.12-slim, while maintaining existing commands for package management and server execution. The pyproject.toml file features a minor formatting adjustment to the connector-aws dependency entry for consistency, without impacting functionality.

Changes

File Change Summary
connector-proxy-demo/dev.Dockerfile Updated base image from python:3.11.6-slim-bookworm to python:3.12-slim.
connector-proxy-demo/pyproject.toml Adjusted whitespace in connector-aws dependency entry for consistency.

Possibly related PRs

Suggested reviewers

  • danfunk

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.

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 (2)
connector-proxy-demo/dev.Dockerfile (2)

1-1: Approve the base image update with a minor suggestion.

The update to Python 3.12 aligns well with the PR objective of adding support for newer Python versions. This change will allow the project to leverage the latest features and improvements in Python.

Consider specifying the exact patch version (e.g., python:3.12.0-slim) to ensure consistent builds across different environments. This practice helps in reproducing issues and maintaining version parity.

Also, note that while the PR objective mentions Python 3.13 support, this image only updates to 3.12. This is appropriate as Python 3.13 is not yet released for production use.


Line range hint 5-7: Consider updating package versions.

With the upgrade to Python 3.12, it's worth checking if newer versions of pip, poetry, and pytest-xdist are available and compatible. This ensures that you're taking full advantage of the latest features and bug fixes in these tools.

You can check for the latest versions of these packages on PyPI:

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b1359e3 and 5556c54.

⛔ Files ignored due to path filters (1)
  • connector-proxy-demo/poetry.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • connector-proxy-demo/dev.Dockerfile (1 hunks)
  • connector-proxy-demo/pyproject.toml (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • connector-proxy-demo/pyproject.toml
🧰 Additional context used
🔇 Additional comments (1)
connector-proxy-demo/dev.Dockerfile (1)

Line range hint 9-9: Verify script compatibility with Python 3.12.

The CMD instruction remains unchanged, which is generally fine. However, given the update to Python 3.12, it's important to ensure that the run_server_locally script is compatible with this new Python version.

Please review the script contents and test it thoroughly with Python 3.12 to confirm there are no compatibility issues.

To help verify the script's compatibility, you can run the following command:

✅ Verification successful

Script Compatibility Verified with Python 3.12.

The run_server_locally script is configured to use Python version ^3.11, which includes Python 3.12. Additionally, the dependencies managed by Poetry are compatible with Python 3.12.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the contents of the run_server_locally script for potential compatibility issues with Python 3.12

# Test: Display the contents of the run_server_locally script
cat ./bin/run_server_locally

# Note: Manual review of the output is required to identify potential compatibility issues

Length of output: 87


Script:

#!/bin/bash
# Description: Search for the run_server_locally script in the repository

fd run_server_locally

Length of output: 112


Script:

#!/bin/bash
# Description: Check the contents of the connector-proxy-demo/bin/run_server_locally script for potential compatibility issues with Python 3.12

# Test: Display the contents of the run_server_locally script
cat connector-proxy-demo/bin/run_server_locally

Length of output: 458


Script:

#!/bin/bash
# Description: Check the Python version specified in pyproject.toml for compatibility with Python 3.12

# Test: Display the contents of pyproject.toml
cat connector-proxy-demo/pyproject.toml

Length of output: 1055

@jbirddog jbirddog merged commit 3d35ba7 into main Oct 9, 2024
24 checks passed
@jbirddog jbirddog deleted the cp312 branch October 9, 2024 20:18
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