Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@Tric333

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

I don't think this change is correct due to the C standard. In particular, CPython uses "PyObject*" to represent pointers to values. This is correct (according to aliasing rules) when the pointed-to value is either a PyObject struct, or a struct where the first field is a PyObject value.

PyVarObject is currently a struct with a PyObject value as the first field (second case), which means a "PyVarObject*" can be safely casted to "PyObject*". With your change this is no longer valid according C's aliasing rules.