What makes you think that????
Python code can have errors which trigger all kinds of asserts and even lead to crashes.
Python modders wouldn't normally know what the dll asserts mean. If there's a python error those show up even on final release dll, even if the error is in the dll as python will report it as an unknown c++ error.
If python sets values in the dll to something illlegal, and this triggers asserts later, not while the python code is waiting for an answer from the dll, e.g a negative number or an integer overflow number asa dll function parameter, then a python modder wouldn't know the assert is related to python code, and wouldn't be the person to debug it either.
I've never seen an assert that I suspected could be related to python code, and I used the debug.dll a lot while developing PPIO. Not because I was checking PPIO though, I used the debug dll to test MToS, my xml modmod, and I almost always had PPIO installed at the same time. I frequently discovered xml mistakes in MToS with the debug dll, but I never once saw an assert that I thought could be connected to python code.
The dll is a library in the eyes of the python modder, the dll library should be robust enough to not accept negative values as parameters provided by python if negative values are not the kind of number that would work in the given function call. It is then in my opinion a dll explicit bug described as a lack of sanity checks on the input parameters for the python to dll entrypoint function.
I can't think of a single way to actually cause a dll assert through python code, one would have to do something extremely weird to get asserts from using any of the python's API for the dll library.
Something extremely weird done in python would probably manifest in noticeable bugs or crashes that the python modder could use as a cue to not commit the modification in question to the repository before the issue is solved, the python modder could try the assert dll to see if there's any asserts that may explain why the python code is not working as it should, but I seriously doubt that would be an efficient way to debug the issue in 99% of cases like that.
If python code can easily cause the dll to break down without the python modder becoming aware of that fact without getting asserts, then there's a 100% chance that my PPIO modmod, which is in core C2C now, is causing dozens, if not hundreds, of different asserts.
I say that as I pretty much rewrote 50% of all the python code in C2C without ever seeing a single assert I thought was caused by my modifications even though I used the debug dll frequently in its development.
I'm ok with having the assert dll as the default dll once I get to experience that it is consistently possible to not get three assert the first 15 minutes of game-play.
You saved an important game for me and I really do appreciate that.
