Skip to content

chore: reorganize pyproject.toml structure and dependencies #18

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

Merged
merged 1 commit into from
Jun 27, 2025

Conversation

jeandemeusy
Copy link
Owner

@jeandemeusy jeandemeusy commented Jun 27, 2025

Summary by CodeRabbit

  • Refactor
    • Improved organization of configuration settings for better readability and structure. No functional changes were made.

@jeandemeusy jeandemeusy self-assigned this Jun 27, 2025
Copy link

coderabbitai bot commented Jun 27, 2025

Walkthrough

The pyproject.toml file was structurally reorganized by relocating several configuration sections to group related metadata together. No values, keys, or configuration content were altered, added, or removed. These adjustments only affect the file's layout and do not impact any functionality or public interfaces.

Changes

File Change Summary
pyproject.toml Reorganized section order: moved [project.urls], [build-system], [tool.uv.workspace], and [tool.hatch.version] to group related metadata; no content changes.

Poem

In the garden of code, I hop and rearrange,
Moving sections here and there, nothing strange.
No new seeds planted, no carrots removed—
Just tidying up, so the garden’s improved.
With a whisk of my paw, the paths are now clear,
A neater TOML file—spring cleaning is here!
🥕✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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

@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

🧹 Nitpick comments (2)
pyproject.toml (2)

12-15: Nice regrouping – consider adding Source / Documentation URLs

Purely optional, but PyPI renders these extra links and improves UX.


35-37: Remove empty [tool.uv.workspace] block

An empty workspace array adds noise and may confuse tooling. Unless you plan to populate it, drop the section:

-[tool.uv.workspace]
-members = []
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3318fef and 8e6ad99.

📒 Files selected for processing (1)
  • pyproject.toml (3 hunks)
🔇 Additional comments (3)
pyproject.toml (3)

16-18: Build-system relocation looks correct

Section now sits next to project metadata and still includes the required hatch-vcs. No further action.


63-64: [tool.hatch.version] correctly paired with hatch-vcs

Dynamic versioning via VCS is properly configured.


10-10: Confirm aiohttp>=3.12.13 is installable

aiohttp releases are still in the 3.9 series; a 3.12.13 tag doesn’t exist on PyPI. An impossible lower-bound will break installs.

#!/bin/bash
# Show the highest published aiohttp versions
curl -s https://pypi.org/pypi/aiohttp/json | jq -r '.releases | keys | sort | .[-10:]'

If the version is absent, update to a realistic constraint (e.g. aiohttp>=3.9,<4.0).

@jeandemeusy jeandemeusy merged commit e560a16 into master Jun 27, 2025
2 checks passed
@jeandemeusy jeandemeusy deleted the clean-up-pyproject branch June 27, 2025 09:50
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.

1 participant