Closed Avasam closed 6 months ago
Not sure what to do with com.win32comext.axscript.server.error.Exception
I'd be super surprised if it is used anywhere, given that the point of using axscript.server would be for other languages to invoke Python code and those other languages really aren't going to have access to this anyway.
Something I came across. This really ought to be removed to avoid shadowing builtin
Exception
Note that this can impact users, so it is a "breaking change". Not that it's a hard one to update (change 1 aliased nameException
->COMException
). So it should at least be communicated in a changelog.Figured with all the recent refactoring it might be a good time.
Not sure what to do with
com.win32comext.axscript.server.error.Exception
. As far as I can tell, it's unused in pywin32's code, but could maybe be used in downstream code for better com object traceback? I could rename it to avoid the builtin shadowing, but it wasn't previously marked as deprecated/obsolete.