New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How is this different from autoprogram? #16

Closed
mr-c opened this Issue Jul 30, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@ribozz

This comment has been minimized.

Show comment
Hide comment
@ribozz

ribozz Jul 31, 2014

Owner

For now sphinx-argparse is more feature rich:

  • allows to extend output of generated commands
  • more control over subcommands
  • better formating
  • improved support for man pages - was contributed recently
  • we have more contributors (see changelog)

Our extension was started far before autoprogram. If, at the time when I initiated the project, there would be at least something like autoprogram, then I wouldn't start my own extension.

Owner

ribozz commented Jul 31, 2014

For now sphinx-argparse is more feature rich:

  • allows to extend output of generated commands
  • more control over subcommands
  • better formating
  • improved support for man pages - was contributed recently
  • we have more contributors (see changelog)

Our extension was started far before autoprogram. If, at the time when I initiated the project, there would be at least something like autoprogram, then I wouldn't start my own extension.

@mr-c

This comment has been minimized.

Show comment
Hide comment
@mr-c

mr-c Jul 31, 2014

Cool, thanks for the summary. Perhaps you can get this package mentioned in
the Sphinx docs to aid discovery. I'll give it a whirl soon.
On Jul 31, 2014 12:49 AM, "Alex Rudakov" notifications@github.com wrote:

For now sphinx-argparse is more feature rich:

  • allows to extend output of generated commands
  • more control over subcommands
  • better formating
  • improved support for man pages - was contributed recently
  • we have more contributors (see changelog)

Our extension was started far before autoprogram. If, at the time when I
initiated the project, there would be at least something like autoprogram,
then I wouldn't start my own extension.


Reply to this email directly or view it on GitHub
#16 (comment)
.

mr-c commented Jul 31, 2014

Cool, thanks for the summary. Perhaps you can get this package mentioned in
the Sphinx docs to aid discovery. I'll give it a whirl soon.
On Jul 31, 2014 12:49 AM, "Alex Rudakov" notifications@github.com wrote:

For now sphinx-argparse is more feature rich:

  • allows to extend output of generated commands
  • more control over subcommands
  • better formating
  • improved support for man pages - was contributed recently
  • we have more contributors (see changelog)

Our extension was started far before autoprogram. If, at the time when I
initiated the project, there would be at least something like autoprogram,
then I wouldn't start my own extension.


Reply to this email directly or view it on GitHub
#16 (comment)
.

@ribozz

This comment has been minimized.

Show comment
Hide comment
@ribozz

ribozz Aug 18, 2014

Owner

Added note about this package to the docs.

Owner

ribozz commented Aug 18, 2014

Added note about this package to the docs.

@ribozz ribozz closed this Aug 18, 2014

@asmeurer

This comment has been minimized.

Show comment
Hide comment
@asmeurer

asmeurer Oct 13, 2014

My take on this (I've only looked at each a little bit so far):

  • I disagree that the output format of sphinx-argparse is better. It uses tables, which aren't easy to read, and don't handle long option help text well (they scroll off in a frame and wrap weird, at least in the theme I'm using).
  • autoprogram doesn't handle argparse.SUPPRESS
  • It's annoying to use either with my existing code, as I don't already have a function that returns a parser. sphinx-argparse is better here because it allows a function, whereas autoprogram expects the parser to be in the module namespace.

Can you explain what the manpage support is?

asmeurer commented Oct 13, 2014

My take on this (I've only looked at each a little bit so far):

  • I disagree that the output format of sphinx-argparse is better. It uses tables, which aren't easy to read, and don't handle long option help text well (they scroll off in a frame and wrap weird, at least in the theme I'm using).
  • autoprogram doesn't handle argparse.SUPPRESS
  • It's annoying to use either with my existing code, as I don't already have a function that returns a parser. sphinx-argparse is better here because it allows a function, whereas autoprogram expects the parser to be in the module namespace.

Can you explain what the manpage support is?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment