(I think I forgot to send out the previous meeting notes - you can find them in the Google doc linked at the bottom of this message)
Attendees: Benedikt, Mark, Victor, Benoit, Felix, Amos Agenda Review last week's action items: Benedikt will fix 32-bit issues Benedikt to add test that loads unicode function names Felix will submit PR for #1333 (function delegates) Felix will submit PR that rewrites import hook to use pure Python (see #1096 & #727) Notes: 32-bit issues nothing done yet, Benedikt will look into this test that loads unicode function names merged! PR #1329 problem was that we need to make sure we always use our own UTF-8 marshaller we can't use the .NET one because it doesn't exist in all .NET frameworks PR fixes the issue where Benedikt saw it, but there are possibly other places where the same issue exists follow-up issue is #1354 let's link all encoding problems to this issue in Python 3 it's all UTF-8 this particular issue (unicode function names) is fixed function delegates merged! PR #1333 rewrite of import hook to use pure Python (see #1096 & #727) in progress (Felix) rewrite avoids entering C# unless we absolutely need to, because there's no way to prevent C# from "owning" a thread that calls C#, and once C# owns it domain reload hangs waiting for the thread to exit fixes a common pattern "try import PySide; except: import PySide2" - previous implementation hits C# on the first import call, even if PySide doesn't exist internal compiler error (https://github.com/dotnet/roslyn/issues/49760) still present in latest .NET 5.0.2 might still be a Roslyn point release? doesn't help because Roslyn likely frozen until .NET 6 Victor will find out when they plan on releasing a fix required for replacing PInvoke delegates for reference types with using unmanaged function pointers (supposed to work in new C#, but triggers an internal compiler error) blocking our ability to do a multi-stage startup and dynamically bind to the right Python dll/dso/dylib anywhere but Mono (which supports __Internal as the DllImport string) helpful for embedding .NET in Python since want to use the statically linked symbols in the python executable - using a dynamic library, even if present, leads to weird problems we'll find out if a fix is forthcoming and if not, use a workaround Action items: Benedikt will fix 32-bit issues Felix will complete rewrite of import hook to avoid calling C# unless necessary Victor will find out if there will be a Roslyn release fixing the internal compiler error The meeting notes google doc is here <https://docs.google.com/document/d/1rJVU84B_dgx58-_EopjRtOJVFAI2WfHJYV0n7uE1Oak/edit#>. Feel free to correct or add additional information. The next meeting will be held on Thursday, January 28 at 12pm EST (click for your time zone) <https://www.google.com/search?q=12:00+pm+EST>. Mark Visser Senior Dev Manager, M&E Unity Technologies - www.unity3d.com <http://www.unity3d.com/>
_______________________________________________ PythonNet mailing list -- pythonnet@python.org To unsubscribe send an email to pythonnet-le...@python.org https://mail.python.org/mailman3/lists/pythonnet.python.org/ Member address: arch...@mail-archive.com
