René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"pythonnet (clr) hacks the import mechanism in Python - not compatible with Kivy","articleBody":"https://groups.google.com/forum/#!search/pythonnet%7Csort:date/kivy-users/X0R7FUtysAk/IBKUJuyGBQAJ\r\n\r\n\r\n\u003e The problem was that importing the clr module does modify the __import__ function and this seems to be globally.  \r\n\u003e \r\n\u003e For standard importing (i.e. import xyz  or from xyz imprt abc) this does not cause a problem, but in kivy/factory.py it calls __import__ in a way that is not supported by the overridden __import__() from the clr implementation.\r\n\u003e \r\n\u003e As a work around I now have factory.py create a reference to the __import__ as self._local_import and then around line 140 in factory.py I replace\r\n\u003e \r\n\u003e \r\n\u003e      module = __import__(name=item['module'], fromlist='.') \r\n\u003e \r\n\u003e with \r\n\u003e \r\n\u003e    module = self._local_import(name=item['module'], fromlist='.')\r\n\u003e \r\n\u003e \r\n\u003e And it appears that as long as factory.py is used at least once before the clr module is imported then things seem to work out.\r\n\u003e \r\n\u003e This seems like a hack and I would prefer to have something local to the clr importing that reverts __import__ to what it was, but my attempts to do so only fixed the __import__ locally to the module that did the importing and not globally like the import clr is doing.\r\n\u003e \r\n\u003e I guess this is more of a python thing but can anyone think of a way to correct this w/o having to modify kivy/factory.py?\r\n\u003e ","author":{"url":"https://github.com/den-run-ai","@type":"Person","name":"den-run-ai"},"datePublished":"2017-09-26T17:37:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/547/pythonnet/issues/547"}