[Python.NET] Re: Wrap in interface (#1240)

ng interface member. It might still affect `hasattr`, but this is somewhat expected. Regards, Victor From: Mohamed Koubaa<mailto:mohamed.kou...@ansys.com> Sent: Monday, February 8, 2021 8:34 AM To: A list for users and developers of Python.NET<mailto:pythonnet@python.org> Su

[Python.NET] Re: Wrap in interface (#1240)

there’s a workaround for the scenario you described which is just doing m.GetShape(1).__raw_implementation__.Length or m.GetShape(1).__implementation__.Length depending if you need an encoded instance. Regards, Victor Milovanov From: Mohamed Koubaa<mailto:mohamed.kou...@ansys.com> Sent: Mon

[Python.NET] Wrap in interface (#1240)

Hello, This PR changed behavior of pythonnet to use stricter typing when a method returns an interface. I'd like a way to opt-out of this behavior, and I'll share a representative use-case below. The tl;dr is that python is a dynamic language

[Python.NET] Building with vs2019

you do? A better question might be how UnmanagedExports is making use of Microsoft.Build.Utilities. I know that there is a modernization project<https://github.com/pythonnet/pythonnet/projects/6> that may address this in the future. Thanks! Mohamed Koub