René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"pythonnet 3.0 breaks access to methods whos signature returns an interface but clients want to use the concrete type","articleBody":"### Environment\r\n\r\n-   Pythonnet version: 3.0+\r\n-   Python version: any\r\n-   Operating System: any\r\n-   .NET Runtime: any\r\n\r\ntldr;\r\n#1240 changes the behavior of pythonnet to wrap only the interface methods/members of objects returned by a .NET method whose method declaration states that it returns an interface. Prior to this change, the python object that pythonnet created for the return object wrapped the returned object instance, but did not necessarily implement the interface. The prior behavior was useful for idiomatic C# patterns like the factory pattern.\r\n\r\nThis was [discussed on the mailing list](https://mail.python.org/archives/list/pythonnet@python.org/thread/2WXCLSE7INFAASKT342N7R7S7EBCM4U5/#E6QPZKWP3DQGGPRW6RBGZH7Q3J3JSQPI) and I wanted to file an issue here.\r\n\r\nApparently, the change was also reverted in the [QuantConnect fork](https://github.com/QuantConnect/pythonnet/commit/da8f3d2fb1cd31b87e94314c0f4e8e26d7086c8d).\r\n\r\n\r\nMy preferred fix, for what its worth, is option 4 (from the list of options mentioned by Victor in that thread):\r\n\u003e IronPython apparently allows explicit interface implementations to be called (instead of returning interface-wrapped instances), if there’s no conflict with regular methods. Perhaps we should consider this as an option.","author":{"url":"https://github.com/koubaa","@type":"Person","name":"koubaa"},"datePublished":"2022-08-15T18:04:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/1914/pythonnet/issues/1914"}