NEP: add NEP-0058 for bytestringdtype - #32433
Conversation
Sorry, something went wrong.
|
@jorenham I appreciate the comments about this and I think it's a discussion worth having. However, per NEP 0, we're supposed to have discussions about substantive issues in the design on the mailing list. Would you mind replying to my mailing list thread to start a discussion about this there? The idea is that this PR gets merged quickly so the NEP can be published and I'd rather not block that on resolving design problems like what you're pointing out. |
Sorry, something went wrong.
|
Ah sorry I missed the mailing list post.
I see, ignore what I said then. |
Sorry, something went wrong.
PR summary
I'm putting this NEP up for review now. See the text below and please give feedback on the text and details here. I'd appreciate it if you keep high-level comments and design feedback to the mailing list thread:
https://mail.python.org/archives/list/numpy-discussion@python.org/thread/O4BIZE4YIYAS2SYOMXIENVS7BP2NNNWI/
AI Disclosure
I used AI models to review and iterate on the NEP and prototype code. While there is AI advice throughout both, I take ownership of the NEP text and all code in the PR branch.