Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>doctest</code> is meant to run python code, so you have to do a conversion somewhere. If you are determined to test the commandline interface directly via <code>doctest</code>, one possibility is to do a regexp substitution to <code>__doc__</code> before you pass it to <code>argparse</code>, to take out the <code>os.popen</code> wrapper:</p> <pre><code>clean = re.sub(r"^&gt;&gt;&gt; os\.popen\('(.*)'\).*", r"% \1", __doc__) p = ArgumentParser(description=clean, ...) </code></pre> <p>(Of course there are all sorts of nicer ways to do that, depending on what you consider "nice"). </p> <p>That'll clean it up for the end user. If you also want it to look cleaner in the source, you can go the other way: Put commandline examples in the docstring and don't use doctest.testmodule(). Run your docstring through <code>doctest.script_from_examples</code> and post-process it to insert the <code>os</code> calls. (Then you'll have to embed it into something so you can test it with <code>run_docstring_examples</code>.) <code>doctest</code> doesn't care if the input is valid python, so you can do the following:</p> <pre><code>&gt;&gt;&gt; print doctest.script_from_examples(""" Here is a commandline example I want converted: &gt;&gt;&gt; add -n 3 4 7 """) # Here is a commandline example I want converted: add -n 3 4 # Expected: ## 7 </code></pre> <p>This will still expose the python prompt <code>&gt;&gt;&gt;</code> in the help. If this bothers you, you may just have to process the string in both directions.</p>
    singulars
    1. This table or related slice is empty.
    1. POPython doctest for shell scripts that test argument parsing without polluting docstring with os.popen()
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USalexis
    1. USalexis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThat is a nice way to hide the docstring that tests the argument parser, but it doesn't provide any examples (with expected output) when the user runs `add --help` from the OS shell. Your use of `sys.argv` seems rougly equivalent to the `os.popen` in my code, and it looks equally ugly when the docstring is used for documentation and 'help' rather than for doctest testing.
      singulars
      1. PO
      1. UShobs
    2. COOk, if you really want commandline-oriented doc and tests, see the new answer.
      singulars
      1. PO
      1. USalexis
    3. COWow. Quite tricky. Thanks for getting me out of a bind. I understand now why you didn't propose all this complexity in your first answer. Maybe doctest or argparse will incorporate some shell testing features in the future. `$$$` instead of `>>>` anyone?
      singulars
      1. PO
      1. UShobs
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload