The warnings are expected - Python has to be able to handle arbitrarily bad parameters/use without crashing, while the CRT assumes that bugs belong to the direct caller who needs to fix them. As a result, it will assert and terminate for blatantly incorrect operations.

A while back we discussed suppressing these warnings by default to stop people worrying, while leaving them enabled for the build bots where those analysing the results are more likely to be aware of the intricacies.

Of course, if the assert dialog is actually showing, we have an issue. If it's only the printed warning then it's expected.