issues
search
markshannon
/
New-C-API-for-Python
Design and discussion for the new C-API for Python
Creative Commons Zero v1.0 Universal
15
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Suggestion: use `PyAny` instead of `PyRef`
#23
davidhewitt
opened
1 year ago
0
Fix comment
#22
markshannon
closed
1 year ago
0
Add generated api
#21
markshannon
closed
1 year ago
0
Clarify ABI
#20
markshannon
closed
1 year ago
0
Clarify ABI
#19
markshannon
closed
1 year ago
0
Clarify use of C99 integer types, and a couple of other edits.
#18
markshannon
closed
1 year ago
0
Avoid `NULL`s as much as possible.
#17
markshannon
opened
1 year ago
0
No `long`, `unsigned int`, etc. Use <stdint.h> throughout.
#16
markshannon
closed
1 year ago
0
Always pass a context.
#15
markshannon
closed
1 year ago
0
Change design from returning struct to returning int kind and result through out parameter.
#14
markshannon
closed
1 year ago
0
Don't return structs.
#13
markshannon
closed
1 year ago
0
Add table describing portability vs performance.
#12
markshannon
opened
2 years ago
1
Update issue templates
#11
markshannon
closed
2 years ago
0
Address reference-handling performance
#10
encukou
closed
2 years ago
1
Define migration path for extensions
#9
ronaldoussoren
opened
2 years ago
0
Add section listing alternative approaches
#8
ericsnowcurrently
opened
2 years ago
7
Prior Art: Steve Dower's "Rings and Layers"
#7
ericsnowcurrently
opened
2 years ago
7
Should we pass the interpreter as an explicit parameter?
#6
markshannon
closed
1 year ago
9
Define what is a "safe" value more precisely.
#5
markshannon
opened
2 years ago
0
Design type creation API
#4
encukou
opened
2 years ago
11
Needs a name
#3
markshannon
opened
2 years ago
0
My initial thoughts
#2
encukou
opened
2 years ago
7
Question about relation to HPy
#1
timfel
closed
1 year ago
7