René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"First-character argument flag is undocumented and behaves strangely when colliding with default options","articleBody":"Consider the function signature:\r\n\r\n```\r\ndef main(headless=False):\r\n  # Construct GUI\r\n  if not headless:\r\n    widget.show()\r\n    app.exec()\r\n\r\nif __name__ == '__main__': fire.Fire(main)\r\n```\r\n\r\nAfter reading through the user guide for fire, I would expect `python myFile -h` to produce the help signature for this file. However, it runs the script with `headless = True`.\r\n\r\nWhile in retrospect I suppose this makes sense, I would like some way of telling fire to disallow shortcut flags if they override user-expected options like --[i]nteractive, --[h]elp, etc. In those cases, the user can be forced to say `python myFile --headless` for the desired behavior.\r\n\r\nMoreover, if my script looked like this:\r\n```\r\ndef main(headless=False, hArg=True):\r\n  # Construct GUI\r\n  if not headless:\r\n    widget.show()\r\n    app.exec()\r\n\r\nif __name__ == '__main__': fire.Fire(main)\r\n```\r\nand I ran the same line of code, fire would appropriately err out. This is also acceptable in my opinion.\r\n\r\nMore importantly, the first-character flag behavior should at the very least be documented. I read through https://github.com/google/python-fire/blob/master/docs/guide.md and couldn't find it there.\r\n","author":{"url":"https://github.com/ntjess","@type":"Person","name":"ntjess"},"datePublished":"2020-04-01T00:34:44.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/238/python-fire/issues/238"}