StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17895206
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-27T07:06:16.450
FavoriteCount
0
LastActivityDate
2013-07-27T16:57:31.530
LastEditDate
2013-07-27T16:57:31.530
LastEditorUserId
901925
OwnerUserId
901925
ParentId
6880169
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
As of Python 3.3, <code>parse_args</code> checks its set of <code>seen_actions</code> against the set of actions that are required, and issues a <code>the following arguments are required...</code> error as needed. Previously it checked its list of remaining <code>positionals</code> and raised the <code>too few arguments</code> error message. So for newer versions, this snippet should do what you want: <pre><code>parser = argparse.ArgumentParser() lat=parser.add_argument('lat', help="latitude") lon=parser.add_argument('lon', help="longitude") parser.add_argument('--method', help="calculation method (default: add)", default="add") class MyAction(argparse._StoreTrueAction): def __call__(self, parser, namespace, values, option_string=None): setattr(namespace, self.dest, self.const) lat.required = False lon.required = False parser.add_argument('--list-methods', help="list available methods", action=MyAction) </code></pre> Normally <code>lat</code> and <code>lon</code> are required positionals, but if the <code>--list...</code> action is taken, those actions are no longer required, and no error message is raised if they are missing. <hr> Another way to customize argparse is to use several parsers. In this case you could use one parser to check for the <code>--list-methods</code> option, and based on what it gets, call another that looks for the positionals. <pre><code>parser1 = argparse.ArgumentParser(add_help=False) parser1.add_argument('--list-methods', help="list available methods", action='store_true') parser2 = argparse.ArgumentParser() parser2.add_argument('lat', help="latitude") parser2.add_argument('lon', help="longitude") parser2.add_argument('--method', help="calculation method (default: add)", default="add") parser2.add_argument('--list-methods', help="list available methods", action='store_true') def foo(argv): args,rest = parser1.parse_known_args(argv) if not args.list_methods: args = parser2.parse_args(argv) return args </code></pre> <code>parser2</code> responds to the help command. <code>parse_known_args</code> parses what it can, and returns the rest in a list. <code>parser2</code> could also have been write to take <code>rest, args</code> as arguments.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOne optional argument which does not require positional arguments
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UShpaulj
UserOwnerUserId
1. UShpaulj
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.