Skip to content

Conversation

@alex
Copy link
Contributor

@alex alex commented Oct 4, 2025

No description provided.

@alex alex force-pushed the add-note branch 2 times, most recently from bd97972 to c6618ad Compare October 4, 2025 18:21
@davidhewitt
Copy link
Member

See also #5349 (comment) - a long discussion about using whether we would use .set_note() internally within PyO3.

I see no harm in adding this API for now. cc @Icxolu just in case you have a different opinion?

@alex
Copy link
Contributor Author

alex commented Oct 5, 2025

Yes -- it'd be nice if there was a CPython API for this. I added this utility internally to cryptography, and figured it'd be useful for others.

@Icxolu
Copy link
Contributor

Icxolu commented Oct 5, 2025

I think adding the API is fine. I still wouldn't you use it internally, its to easy to miss the notes in both Rust and Python IMO, but giving downstream users the option for their error sounds good.

@alex alex enabled auto-merge October 5, 2025 17:54
@alex alex added this pull request to the merge queue Oct 5, 2025
Merged via the queue into PyO3:main with commit 5152711 Oct 5, 2025
43 of 44 checks passed
@alex alex deleted the add-note branch October 5, 2025 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants