Skip to content

Conversation

@guitargeek
Copy link
Contributor

I try to move away from exposing cppyy directly as a package, so we can hide it in the ROOT implementation details and don't collide with other installed cppyy packages.

This follows up on #20871, but I didn't want to request the avoidance of cppyy imports there, because that policy only came after the new Keras parser was developed.

Ruff warnings and formatting errors are fixed in separate commits.

I try to move away from exposing `cppyy` directly as a package, so we
can hide it in the ROOT implementation details and don't collide with
other installed `cppyy` packages.
@github-actions
Copy link

github-actions bot commented Feb 7, 2026

Test Results

    22 files      22 suites   3d 14h 14m 17s ⏱️
 3 788 tests  3 788 ✅ 0 💤 0 ❌
75 267 runs  75 267 ✅ 0 💤 0 ❌

Results for commit 0eee3b2.

♻️ This comment has been updated with latest results.

Copy link
Member

@lmoneta lmoneta left a comment

Choose a reason for hiding this comment

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

LGTM!
And thanks also to apply the ruff to the Python files

@guitargeek guitargeek merged commit 1282d75 into root-project:master Feb 9, 2026
55 of 56 checks passed
@guitargeek guitargeek deleted the import_cppyy branch February 9, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants