| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This introduces the following wrapper functions for the public C-API, so that the wrapped functions (`_capi` un-suffixed) can have more arguments, such as a module state: * `new_datetime_ex_capi()` * `new_time_ex_capi()`, renamed from `new_time_ex`, as it is internally unused. * `new_timezone_capi()` * `new_datetime_ex2_capi()` * `new_time_ex2_capi()` The wrappers need to get a module state from the C-API class or a given object's type.
| } | ||
|
|
||
| static PyObject * | ||
| new_datetime_ex_capi(int year, int month, int day, int hour, int minute, |
There was a problem hiding this comment.
I don't think that "_ex" is useful. Just rename it to "new_datetime_capi", no? Same remark for other functions.
Sorry, something went wrong.
There was a problem hiding this comment.
Your suggestion includes non-capi functions?
Sorry, something went wrong.
|
87408a9 is an attempt to strip _ex? from the non-capi functions except reduce(). |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This introduces the following wrapper functions for the public C-API, so that the wrapped functions can have more arguments, such as a module state:
Subsequently, some internal *_ex?() functions are renamed as well.
The wrappers need to get a module state from the C-API class or a given object's type.
cc @vstinner @erlend-aasland: I'd like to prepare as much as possible.