René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Compatibility issue between argparse and pythonnet packages","articleBody":"### Environment\r\n\r\n-   Pythonnet version: 2.3.0.dev1 (built from master on 23/02/2017)\r\n-   Python version: 2.7.13 64bit\r\n-   Operating System: Windows 7 64bit\r\n\r\n### Details\r\n\r\n-   I tested the pythonnet version from yesterday, 23/02/2017, as we are interested in the bug fix for the method overload issue #377. I noticed that we are now running into compatibility issues with the package argparse.\r\n\r\nThe package argparse now only works correctly, if the parsing of the command line arguments is done BEFORE the import statement of pythonnet (import clr).\r\n\r\nIf I revert my pythonnet version to pythonnet==2.2.2, then the problem disappears.\r\n\r\nThe following minimal test code illustrates the problem:\r\n```\r\nfile: test.py\r\nimport argparse\r\n# import clr # can't put it here, args.arg1 will be None\r\n\r\nparser = argparse.ArgumentParser()\r\nparser.add_argument('--arg1', '-a', help='argument 1', dest='arg1')\r\nargs = parser.parse_args()\r\n\r\nimport clr   \r\nprint('Argument 1 = ')\r\nprint(args.arg1)\r\n```\r\nThen I start the script from command line as\r\n\u003e python test.py --arg1 \"Hello World\"\r\n```\r\nIf I run the code with the \"import clr\" statement after the call to parser.parse_args() then I get the desired output: \r\nArgument 1 =\r\nhello world\r\n\r\nHowever, if I put the \"import clr\" at the beginning of the file, I get the output:\r\nArgument 1 =\r\nNone\r\n","author":{"url":"https://github.com/sg08013","@type":"Person","name":"sg08013"},"datePublished":"2017-02-24T07:51:24.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/404/pythonnet/issues/404"}