Adds the ability to create Python-only property types - #387
Merged
Conversation
jwaldrop107
previously approved these changes
Aug 3, 2026
Co-authored-by: Jonathan M. Waldrop <relik107@gmail.com>
ryanmrichard
enabled auto-merge (squash)
August 3, 2026 17:22
jwaldrop107
approved these changes
Aug 3, 2026
Contributor
|
🚀 [bumpr] Bumped! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Is this pull request associated with an issue(s)?
No.
Description
For a long time we've only had the ability to declare property types in C++. This PR introduces a mechanism for declaring Python-only PTs. PTs declared this way can only be leveraged by modules written in Python. Python-only PTs are duck-typing compatible and largely amount to labeling arguments and enforcing numbers of inputs/results.
FWIW the motivation for this PR is that I need to declare an API compatible with the QCArchive ecosystem which requires me to take/return Pydantic objects, which are pure Python objects. I thus can't declare a C++ property type for such a module.
TODOs
None (if tests pass)