Issues
- 16
Non-namespaced identifiers
#46 opened by encukou - 3
Defining types is messy
#49 opened by encukou - 2
Const correctness
#38 opened by encukou - 12
Use of features specific to the C language
#35 opened by encukou - 4
Function must not return a pointer to content without an explicit resource management
#57 opened by vstinner - 15
- 11
- 5
- 42
Naming convention for new C API functions
#52 opened by vstinner - 12
Functions must not suppress exceptions
#51 opened by serhiy-storchaka - 9
Python.h doesn't expose everything
#43 opened by encukou - 3
C standard
#42 opened by encukou - 6
- 44
The C API is weakly typed
#31 opened by markshannon - 4
Use of legacy C integer types
#27 opened by markshannon - 2
- 3
API exposes memory layout of some runtime objects
#22 opened by steve-s - 5
- 6
API with a leading underscore
#58 opened by encukou - 17
Infallible functions
#20 opened by encukou - 5
Concrete strings
#16 opened by encukou - 4
Fast type checking for heap types
#17 opened by encukou - 4
Injecting foreign stack frames
#18 opened by encukou - 7
Interaction with other GC based languages
#19 opened by encukou - 1
- 0
- 3
- 1
- 9
- 1
Clarify what the C API contains
#34 opened by encukou - 8
- 2
C API exposes pointers to real Python objects
#37 opened by steve-s - 9
Supporting multiple ABI versions at once
#39 opened by steve-s - 12
Resistance to small improvements
#44 opened by encukou - 16
- 2
- 0
API for selecting an API subset/tier
#59 opened by encukou - 4
If an incompatible change has to be introduced, how can it be prepared to reduce its impact on users?
#60 opened by vstinner - 8
- 12
CPython project has the lead on the C API, other Python implementations have to follow
#64 opened by vstinner - 4
- 3
- 1
Things that I may work on to make doc more maintainer friendly during the sprint
#76 opened by willingc - 4
Collection of documents about the C API
#48 opened by iritkatriel - 18
- 3
How can an user access old removed functions? Can a 3rd party project provide them?
#62 opened by vstinner - 1
Allow custom allocators for PyObject memory
#69 opened by nascheme - 1
Writer APIs for str and bytes should be public
#70 opened by malemburg - 2
Specific praise for the C API
#30 opened by iritkatriel - 12