Author ronaldoussoren
Recipients DeKrain, ronaldoussoren, steven.daprano
Date 2018-09-03.11:05:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535972703.24.0.56676864532.issue34543@psf.upfronthosting.co.za>
In-reply-to
Content
It's not as easy as that, the SystemError in the original report is caused by invalid use of a C-API due to partial initialisation of an _struct.Struct instance.

The solution is likely two-fold:

1) Ensure that __new__ fully initialises the fields in de C struct to some value

2) (Possibly) check that fields in the C structure have a sane value before using them. This part can have a measurable performance cost, and it would be nicer to avoid this by picking smart values in (1). 

The most important bit is the first step, even if that keeps raising SystemError when only calling Struct.__new__ because this avoid crashing the interpreter.
History
Date User Action Args
2018-09-03 11:05:03ronaldoussorensetrecipients: + ronaldoussoren, steven.daprano, DeKrain
2018-09-03 11:05:03ronaldoussorensetmessageid: <1535972703.24.0.56676864532.issue34543@psf.upfronthosting.co.za>
2018-09-03 11:05:03ronaldoussorenlinkissue34543 messages
2018-09-03 11:05:03ronaldoussorencreate