David Bieber

Right now `foo --version` is not supported but `foo -- --version` is. The reason we originally chose not to support `foo --version` is that the function foo could have an...

I would be supportive of a change that makes `foo --version` in addition to `foo -- --version` in all cases except where --version is an acceptable flag to foo. However,...

Another thing that works is --noflag

Implementing this request would have to come as part of a larger change: using type annotations to infer types and parse arguments accordingly; this isn't planned at this time.

Yes, Fire does not take into account type annotations at this time. While this could be a big improvement for Fire, it is not planned at this time.

The docstring parsing code is in https://github.com/google/python-fire/blob/master/fire/docstrings.py Multiline rst args should be handled by https://github.com/google/python-fire/blob/d44d33d4ac9389854b046ca0270c112693b309e6/fire/docstrings.py#L468-L469 You may have identified a bug.

The first step would be to add one or more failing test cases, e.g. inspired from the comment above https://github.com/google/python-fire/issues/448#issue-1659522480 Then if you see the issue and can fix it,...

I agree that it would be OK to adjust the behavior of those 3 tests. I do have one concern about simply always using \n, and that's that it might...

> so if the arg name is long or the description starts on the same line, it would be extracted as a really long string. See the part of the...

It looks like for the RST format, whole lines are used are used so my concern would not arise. For the Google format, the concern I have arises at https://github.com/google/python-fire/blob/d44d33d4ac9389854b046ca0270c112693b309e6/fire/docstrings.py#L397...