Skip to content

Conversation

@Flamefire
Copy link
Contributor

(created using eb --new-pr)

Copy link
Contributor

@Micket Micket left a comment

Choose a reason for hiding this comment

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

lgtm

@Flamefire
Copy link
Contributor Author

Note: This currently doesn't change anything because the only difference of CargoPythonPackage to PythonPackage doesn't matter (yet) for Extensions.
Maybe for the components but there currently would need to be a default easyblock anyway which I haven't seen.
Speaking of it: Should we really unconditionally overwrite the default easyblock in (Cargo)PythonBundle and ignore if it was set by the EC?

@boegel boegel changed the title Make CargoPythonPackage the default class for extensions/components of CargoPythonBundle Make CargoPythonPackage the default class for extensions/components of CargoPythonBundle Nov 19, 2025
@boegel boegel added the change label Nov 19, 2025
@boegel boegel added this to the next release (5.2.0) milestone Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants