Skip to content

[Python] Use value_type and not string matching to pythonize STL vector - #23324

Open
guitargeek wants to merge 1 commit into
root-project:masterfrom
guitargeek:stl-vector-value-type
Open

[Python] Use value_type and not string matching to pythonize STL vector#23324
guitargeek wants to merge 1 commit into
root-project:masterfrom
guitargeek:stl-vector-value-type

Conversation

@guitargeek

Copy link
Copy Markdown
Contributor

Instead of matching numpy-compatible element types by string manipulation on the class name, use the value_type typedef that cppyy exposes on std::vector proxies. This decouples the pythonization from how cppyy happens to spell template instantiation names.

@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown

Test Results

    22 files      22 suites   3d 17h 6m 54s ⏱️
 3 878 tests  3 877 ✅ 0 💤 1 ❌
76 365 runs  76 363 ✅ 1 💤 1 ❌

For more details on these failures, see this check.

Results for commit a12551f.

♻️ This comment has been updated with latest results.

Instead of matching numpy-compatible element types by string manipulation
on the class name, use the `value_type` typedef that cppyy exposes on
std::vector proxies. This decouples the pythonization from how cppyy
happens to spell template instantiation names.
@guitargeek
guitargeek force-pushed the stl-vector-value-type branch from 36f302e to a12551f Compare September 10, 2026 09:27

@aaronj0 aaronj0 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM!

@guitargeek guitargeek added the clean build Ask CI to do non-incremental build on PR label Sep 10, 2026
@guitargeek guitargeek closed this Sep 10, 2026
@guitargeek guitargeek reopened this Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clean build Ask CI to do non-incremental build on PR in:Python Interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants