David Bieber

Sorry to hear you're hitting this issue. Unfortunately, there's not an obvious fix: Fire supports chaining functions, which means that the output of a function like `add` may determine what...

Thanks for the feedback. We may be able to fix this after all. The fix would be to require explicit chaining (using a separator, which is "-" by default) when...

Thanks for the interest. The change we're considering is to require explicit chaining (using a separator, which is "-" by default) when not all the arguments are received, and to...

Agreed on multi-line docstrings. This is particularly important if people use whitespace for formatting in their docstrings, such as including usage examples. The param descriptions should be showing up in...

Multi-line docstrings issue is resolved. As for the params, it works if you 1) add the missing `self` args to your methods (or mark them as @staticmethod) and 2) include...

Hi okada8, I think your request is misplaced. This is an issue thread for Python Fire.

This is an unintended side-effect of our reliance on the python ast when parsing inputs: https://github.com/google/python-fire/blob/c1266d0dbb2114514fcf8be62044344b5a51c733/fire/parser.py#L77 As a workaround for now, you can add an extra layer of quotes. `python...

I don't think that will work, unfortunately. If the input is "1", json.dumps will produce '"1"' which will get parsed as a string, whereas an int is desired.

Thanks for the PR. 🙏 We generally don’t accept changes to the console module directly in the fire repo though, in order to keep any diffs between it and its...

> Apologies from my end, I wasn't aware of that. No worries! There was no way for you to know. > @dbieber Any updates? I'll let you know about making...