issues
search
capi-workgroup
/
problems
Discussions about problems with the current C Api
19
stars
6
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Exported data (`PyAPI_DATA` rather than `PyAPI_FUNC`)
#80
encukou
opened
2 months ago
2
Private APIs used in Pyodide
#79
hoodmane
opened
2 months ago
4
Add references section to doc
#78
willingc
closed
11 months ago
0
Edits to Introduction section to add headings to skim and small readability tweaks
#77
willingc
closed
3 weeks ago
1
Things that I may work on to make doc more maintainer friendly during the sprint
#76
willingc
closed
3 months ago
2
Improve doc structure and edit for readability
#75
willingc
closed
11 months ago
0
More precisely define what is meant by C API.
#74
steve-s
closed
11 months ago
0
Expand the stakeholders section
#73
steve-s
closed
12 months ago
7
Add more context to the README to prepare for a formal workgroup
#72
malemburg
closed
1 year ago
1
Clean up the Python C API for consistency, completeness and usefulness
#71
malemburg
closed
1 year ago
18
Writer APIs for str and bytes should be public
#70
malemburg
opened
1 year ago
4
Allow custom allocators for PyObject memory
#69
nascheme
opened
1 year ago
1
Language bindings → Binding generators
#68
encukou
closed
1 year ago
0
Fix typos & some terse wording
#67
encukou
closed
1 year ago
0
add sections on strengths and stakeholers
#66
iritkatriel
closed
1 year ago
0
edit intro paragraph about the origins of the C API
#65
iritkatriel
closed
1 year ago
0
CPython project has the lead on the C API, other Python implementations have to follow
#64
vstinner
closed
3 weeks ago
13
First draft of problems document
#63
iritkatriel
closed
1 year ago
2
How can an user access old removed functions? Can a 3rd party project provide them?
#62
vstinner
closed
1 year ago
4
No clear separation between "fast API" (unsafe) and "safe API"
#61
vstinner
closed
1 week ago
9
If an incompatible change has to be introduced, how can it be prepared to reduce its impact on users?
#60
vstinner
closed
3 weeks ago
5
API for selecting an API subset/tier
#59
encukou
opened
1 year ago
1
API with a leading underscore
#58
encukou
opened
1 year ago
6
Function must not return a pointer to content without an explicit resource management
#57
vstinner
closed
3 months ago
5
Disallow creation of incomplete/inconsistent objects
#56
vstinner
opened
1 year ago
20
Opt-in macro for a new clean API? Subset of functions with no known issues
#54
vstinner
closed
6 months ago
12
How to shrink the size of the C API? Or at least, slow down its growth?
#53
vstinner
closed
3 months ago
6
Naming convention for new C API functions
#52
vstinner
closed
3 months ago
43
Functions must not suppress exceptions
#51
serhiy-storchaka
closed
3 months ago
13
Hard to reason about which functions are or are not part of the stable ABI
#50
koubaa
opened
1 year ago
3
Defining types is messy
#49
encukou
opened
1 year ago
3
Collection of documents about the C API
#48
iritkatriel
opened
1 year ago
4
Argument accepting a Python object or NULL: error prone API
#47
vstinner
opened
1 year ago
2
Non-namespaced identifiers
#46
encukou
opened
1 year ago
16
Evolving the Stable ABI to use functions for INCREF, DECREF, TYPE
#45
gvanrossum
closed
3 months ago
17
Resistance to small improvements
#44
encukou
opened
1 year ago
12
Python.h doesn't expose everything
#43
encukou
opened
1 year ago
9
C standard
#42
encukou
opened
1 year ago
3
README: Add link to the write-up of the Language Summit discussions
#41
AlexWaygood
closed
1 year ago
0
Expose _PyExc_PrepReraiseStar (and other intrinsics?) in the unstable api
#40
da-woods
opened
1 year ago
4
Supporting multiple ABI versions at once
#39
steve-s
opened
1 year ago
9
Const correctness
#38
encukou
opened
1 year ago
5
C API exposes pointers to real Python objects
#37
steve-s
closed
3 months ago
3
Debug mode that can be easily activated without recompilation
#36
steve-s
opened
1 year ago
8
Use of features specific to the C language
#35
encukou
opened
1 year ago
12
Clarify what the C API contains
#34
encukou
opened
1 year ago
1
References between Python objects are opaque to the runtime
#33
steve-s
opened
1 year ago
8
Introspection capabilities are incomplete for C objects
#32
iritkatriel
opened
1 year ago
10
The C API is weakly typed
#31
markshannon
opened
1 year ago
44
Specific praise for the C API
#30
iritkatriel
opened
1 year ago
2
Next