slozier

Thanks for the report. Interestingly it's also crashing my CPython 3.8.5 interpreter.

Thanks for the report. I managed to reproduce the issue here. I think it's ABB doing something funny with the EventHandler delegates (but I don't know enough about all this...

I know this is a 3.6 change, but I'd like to get it in sooner rather than later. I think knowing that the sys.stdout encoding is utf-8 may be helpful...

No idea if it's related, but the simple example issue reminds me of the following (from https://github.com/IronLanguages/ironpython2/issues/653) ```py import ctypes class POINT(ctypes.Structure): _fields_ = [('x', ctypes.c_long), ('y', ctypes.c_long)] buf =...

Thanks for the reminder. I updated the nuspec in https://github.com/IronLanguages/ironpython3/commit/5d98bd8ed243649981ae6719bce94780d9e39d8d. I think I may hold off for 3.4-final before publishing (since it's most likely going to happen this summer). Unless...

As I understand it, Mono's API surface supports .NET Standard 2.1 (since 6.4 according to the .NET Standard page) which means it makes sense that these APIs appear on BigInteger....

https://github.com/IronLanguages/ironpython3/blob/master/Src/IronPython.Modules/ResourceMetaPathImporter.cs

Here's a sample C# unit test: https://github.com/IronLanguages/ironpython3/blob/35e230e0ce0b99f1d399cc496006bd51c1faebbc/Src/IronPythonTest/EngineTest.cs#L636-L644

Resolves the issue, but breaks the traceback of: ```Python def g(): f() def f(): try: raise Exception except: raise g() ```

Yes, I've noticed the same. The way I added the .NET 5 Wpf project is a bit hacky so may be worth trying to find a more proper solution.