On Mon, Apr 29, 2019 at 5:01 PM Neil Schemenauer wrote:
> As far as I understand, we have a similar problem already for
> gc.get_objects() because those static type objects don't have a
> PyGC_Head. My 2-cent proposal for fixing things in the long term
> would be to introduce a function like PyTy
You have my support is you work on removing static types :-)
Here are my notes on the current C APIs to define a type:
https://pythoncapi.readthedocs.io/type_object.html
IMHO static types should go away in the long term. They are causing
too many practical issues.
Victor
Le mar. 30 avr. 2019 à
On 2019-04-27, Nathaniel Smith wrote:
> For Py_TRACE_REFS specifically, IIUC the only goal is to be able to produce
> a list of all live objects on demand. If that's the goal, then static type
> objects aren't a huge deal. You can't add extra data into the type objects
> themselves, but since there
On 29.04.2019 16:30, Victor Stinner wrote:
I reviewed and merged Paul's PR. I concur with Guido, the new
constructor perfectly makes sense and is useful.
About the implementation: date and time are crazy beasts. Extract of the code:
if not 0 < week < 53:
out_of_range = Tru
I reviewed and merged Paul's PR. I concur with Guido, the new
constructor perfectly makes sense and is useful.
About the implementation: date and time are crazy beasts. Extract of the code:
if not 0 < week < 53:
out_of_range = True
if week == 53:
#
