Skip to content

[Python] Decouple Pythonizations from CPyCppyy internals via public API#21694

Open
guitargeek wants to merge 2 commits intoroot-project:masterfrom
guitargeek:cppyy_api_1
Open

[Python] Decouple Pythonizations from CPyCppyy internals via public API#21694
guitargeek wants to merge 2 commits intoroot-project:masterfrom
guitargeek:cppyy_api_1

Conversation

@guitargeek
Copy link
Contributor

Replace most direct usage of CPyCppyy internal headers and implementation details in PyROOT with calls to the public CPyCppyy API.

This removes implicit coupling between PyROOT and CPyCppyy internals, improves ABI robustness, and clarifies the boundary between the two components while preserving existing functionality.

@github-actions
Copy link

Test Results

    22 files      22 suites   3d 2h 3m 25s ⏱️
 3 832 tests  3 831 ✅  1 💤 0 ❌
75 651 runs  75 633 ✅ 18 💤 0 ❌

Results for commit e5b9122.

Copy link
Contributor

@aaronj0 aaronj0 left a comment

Choose a reason for hiding this comment

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

For the new public APIs in CPyCppyy - LGTM!

Replace most direct usage of CPyCppyy internal headers and
implementation details in PyROOT with calls to the public CPyCppyy API.

This removes implicit coupling between PyROOT and CPyCppyy internals,
improves ABI robustness, and clarifies the boundary between the two
components while preserving existing functionality.
The `Utiliy::GetBuffer` function from CPyCppyy is an overkill for the
simple usecase in the ROOT Pythonization library. We can have our own
helper there, avoiding yet another usage of internal CPyCppyy functions.
@guitargeek
Copy link
Contributor Author

Resolved merge conflicts. @vepadulano, is this PR also okay for you?

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