Hello,
I'm figuring out a strategy for the future of Python's C-API, and as one of the 
goals I'd like to make it friendly for non-C languages. I'd like to ask you for 
any suggestions, pain points or comments on how to better do that.
Would you like to help?
I understand PyPy solved a lot of these issues and won't get too much benefit, 
but I'd like to improve things for future projects.
I'm also aware of HPy, a long-term solution. I'd like to meet in the middle.

I started a [Google 
doc](https://docs.google.com/document/d/1fDfF7JanOEyQ9awhKE87-Ajp3H4k7qXL3cmyzPMoNPQ/edit#)
 to collect notes. If you don't mind Google, please feel free to comment there, 
but I'll be happy to discuss here as well. If you have a link to a 
document/rant, I'd love to go through it.

In particular, I'd like to ask if any of the following would help, or would 
have helped in the past:
- Regularity in strong/borrowed references (always returning strong references 
and taking borrowed ones)
- Regularity in error handling (all functions should have a dedicated return 
value, an exception should be set set iff that value is returned)
- Avoiding preprocessor macros
- Avoiding bit fields
- Avoiding enums
- Exposing API/ABI information in a structured format, rather than C headers
Is anything else missing from this list?

Thank you for your time!
_______________________________________________
pypy-dev mailing list -- pypy-dev@python.org
To unsubscribe send an email to pypy-dev-le...@python.org
https://mail.python.org/mailman3/lists/pypy-dev.python.org/
Member address: arch...@mail-archive.com

Reply via email to