Skip to content

Conversation

@guitargeek
Copy link
Contributor

@guitargeek guitargeek commented Aug 15, 2025

This is to reduce the patches between Wim's cppyy and ROOT's while also reducing complexity (if @wlav is fine with it 🙂 ).

@github-actions
Copy link

github-actions bot commented Aug 15, 2025

Test Results

    20 files      20 suites   3d 16h 45m 53s ⏱️
 3 641 tests  3 488 ✅   0 💤 153 ❌
71 122 runs  70 850 ✅ 119 💤 153 ❌

For more details on these failures, see this check.

Results for commit f3c618a.

♻️ This comment has been updated with latest results.

Copy link
Member

@vepadulano vepadulano left a comment

Choose a reason for hiding this comment

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

LGTM, but I would indeed wait for the followup on wlav/CPyCppyy#63

Steering the memory policy locally at the level of methods and functions
is redundant, because one can always define pythonizations that take
care of that.

Removing this feature allows us to add new policy flags without
increasing the net complexity of the library.
@guitargeek
Copy link
Contributor Author

The upstream review has not happened yet, but I think it's important to merge this early to get some exposure of this change to the users of ROOT master before the 6.38 release

@guitargeek guitargeek merged commit d95484d into root-project:master Sep 15, 2025
21 of 25 checks passed
@guitargeek guitargeek deleted the mempolicy branch September 15, 2025 20:17
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