Skip to content

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Sep 12, 2025

The "Poetry" tool is used to manage the project's Python package dependencies.

Dependencies might be classified into distinct categories. The most basic classification would be:

  • Application dependencies: used by the project's applications
  • Development dependencies: tools used in the development and maintenance of the project, but not by the application

By default, Poetry installs all non-optional dependencies. This can be inefficient in a case where a specific operation is being performed, since a given operation might only require the dependencies from one category and so the installation of dependencies from the other is pointless for that operation.

For this reason, Poetry allows the user to organize dependencies into arbitrary "groups", and to specify which groups should be installed.

The Python package installation task is hereby updated to allow dependency groups to be specified, and the calls to that task updated to specify the groups they require.

The "Poetry" tool is used to manage the project's Python package dependencies.

Dependencies might be classified into distinct categories. The most basic classification would be:

- Application dependencies: used by the project's applications
- Development dependencies: tools used in the development and maintenance of the project, but not by the application

By default, Poetry installs all non-optional dependencies. This can be inefficient in a case where a specific operation
is being performed, since a given operation might only require the dependencies from one category and so the
installation of dependencies from the other is pointless for that operation.

For this reason, Poetry allows the user to organize dependencies into arbitrary "groups", and to specify which groups
should be installed.

The Python package installation task is hereby updated to allow dependency groups to be specified, and the calls to that
task updated to specify the groups they require.
@per1234 per1234 self-assigned this Sep 12, 2025
@per1234 per1234 added type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Sep 12, 2025
Copy link

codecov bot commented Sep 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.33%. Comparing base (3601b0a) to head (a7ac767).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #945   +/-   ##
=======================================
  Coverage   83.33%   83.33%           
=======================================
  Files           1        1           
  Lines         180      180           
=======================================
  Hits          150      150           
  Misses         19       19           
  Partials       11       11           
Flag Coverage Δ
unit 83.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@per1234 per1234 merged commit f5d2043 into arduino:main Sep 12, 2025
60 of 71 checks passed
@per1234 per1234 deleted the poetry-group branch September 12, 2025 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant