Skip to content

⬆️ Migrate to uv#5

Merged
pierrocknroll merged 7 commits intomainfrom
uv
Jan 8, 2026
Merged

⬆️ Migrate to uv#5
pierrocknroll merged 7 commits intomainfrom
uv

Conversation

@pierrocknroll
Copy link
Copy Markdown
Contributor

@pierrocknroll pierrocknroll commented Jan 6, 2026

Pull Request

Description

Migrated Python project management from Rye to uv to leverage better performance, modern tooling, and active maintenance.
This PR includes:

  • Updated project configuration (pyproject.toml)
  • Replaced Rye commands with uv equivalents across scripts and documentation
  • Updated CI/CD workflows to use uv
  • Added uv lock files (.uv.lock)
  • Removed Rye-specific files

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality
    to not work as expected)
  • 📝 Documentation update
  • ♻️ Code refactor
  • ⚡ Performance improvement
  • 🧪 Test implementation/update
  • 🔧 Configuration change
  • 🔄 CI/CD related changes

Motivation and Context

Why migrate from Rye to uv?

  • Performance: uv is significantly faster for dependency resolution and installation (written in Rust)
  • Active Development: uv is actively maintained by Astral and has strong community support
  • Modern Tooling: Better compatibility with the Python ecosystem and PEP standards
  • Unified Tool: uv provides a more comprehensive solution for Python project management

This change maintains all existing functionality while improving developer experience and build times.

How Has This Been Tested?

  • Unit tests
  • Integration tests
  • Manual tests
  • Other (please specify):

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Additional Notes

Additional Notes

  • All dependencies remain at the same versions to ensure stability
  • The migration is fully backward compatible in terms of project functionality
  • Consider updating local development environments after merging
  • CI/CD build times should improve noticeably due to uv's performance

@pierrocknroll pierrocknroll changed the title Uv ⬆️ Migrate to uv Jan 6, 2026
@pierrocknroll pierrocknroll marked this pull request as ready for review January 7, 2026 10:28
@pierrocknroll pierrocknroll merged commit 06497a8 into main Jan 8, 2026
3 checks passed
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