It works fine for me. I can't produce a crash by reproducing an exception with this exact line of code. If you can get it to happen again, go ahead and submit the crash when it asks you to.finale00 wrote:Never realized that would be an issue.
Well, as long as it works lol
I'd like to believe not too many games will use such large textures anyways?
Also when writing plugins, sometimes I can crash noesis by causing exceptions during the plugin checking stage.
Namely, if I do something common like
And it doesn't like those bytes.Code: Select all
idstring = noeStrFromBytes(bs.readBytes(5))
Any way to prevent people like me from carelessly not putting that in try blocks?
Unless...by crash, you mean it shows the Python exception dialog? If you write Python code that raises an exception, you're going to see the exception. It wouldn't be wise or desirable for me to change that behavior. As you already mentioned, as well, you can use a try/except if for some reason you really want to write code that you know might raise an exception.