Victor,
Sorry for the late response. I think what I would need is some kind of flag in
the python runtime to choose the old behavior (without having to have my own
branch). Of course there is a workaround but we've invested a lot of time in
designing the API for both CPython & IronPython and
A dump of thoughts on the matter: IronPython is Python 2 only, Python.NET 3.0+ is Python 3 only. Why not use 2.5.x until you are comfortable to change API?Flag is possible, but I would not recommend that approach, because it makes combining multiple libraries that use different global flags problem
Victor,
Our API is C# and some of our users actually directly use C# to access them and
don't use python. We don't intend to change the API. Of course, users may
have to change their scripts to be python3 compatible when they opt into using
our API from CPython, but we expect most anything un
Prior to the change the only way to call explicitly implemented member of an interface was to call it through the interface type, e.g. System.IDisposable.Dispose(instance). From: Mohamed KoubaaSent: Monday, February 8, 2021 11:19 AMTo: A list for users and developers of Python.NETSubject: [Python.N
