Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First, it is necessary to make a small distinction. The <code>argparse</code> module does not parse your command-line arguments, the shell does. The shell is responsible for transforming the line you type in the shell into tokens, which are then passed to <code>sys.argv</code>, a python array/sequence of command-line arguments. The <code>argparse</code> module simply makes sense of what appears in <code>sys.argv</code>.</p> <p>This distinction will clarify both of the "errors" you noticed. First, consider <code>-w "-4.5.5-double_non-parallel_gcc"</code> (note the lack of equal sign). The shell parses these two tokens as <code>-w</code> and <code>-4.5.5-double_non-parallel_gcc</code>, and both of these strings are passed to sys.argv. Without the equal sign, this appears to be two options: <code>-w</code> (with no argument) and <code>-4</code> with <code>.5.5-double_non-parallel_gcc</code> as an argument. You need the equals sign so that everything is parsed as a single token.</p> <p><strong>EDITED SECTION</strong></p> <p>As for <code>2&amp;&gt;</code>, it is impossible for argparse to control whether a given token is treated as an argument or not. If something appears in sys.argv, that means your <em>shell</em> is treating it as an argument.</p> <p>The telltale sign here is the error message. Note that the message is not <code>unrecognized arguments: 2&amp;&gt;</code>, but rather, <code>unrecognized arguments: 2</code>. Your shell recognizes "&amp;>" as output redirection, and parses the rest of the line (including the log file) accordingly. The only argument being passed is the "2", because <code>2&amp;&gt;</code> is not a real type of redirection. (<code>&amp;&gt;</code> already covers both stderr and stdout, so what would the <code>2</code> add to it?)</p> <p>In a comment, you claimed that <code>optparse</code> could "handle" the "2&amp;>". That is not actually the case. The <code>optparse</code> module did exactly what <code>argparse</code> does, but <code>optparse</code> does not validate positional arguments like <code>argparse</code> does. In fact, <code>optparse</code> is letting a real programming error (in this case, using <code>2&amp;&gt;</code> as a type of shell redirection) slip by undetected! You should post your original optparse code, but I suspect you parsed your arguments as follows:</p> <pre><code>opt, args = parser.parse_args() </code></pre> <p>Your script takes no positional arguments, so I imagine you did nothing else with <code>args</code> afterwards. But if you were to inspect <code>args</code>, you would find that <code>2</code> was considered a positional argument! </p> <p>In general, if a script takes no positional arguments and you use <code>optparse</code>, it is good practice to verify that you receive no positional arguments, like so:</p> <pre><code>opt, args = parser.parse_args() if args: parser.error("script takes no positional arguments") </code></pre> <p>The <code>argparse</code> module does that work for you, which is what puts it miles ahead of <code>optparse</code> (among other reasons).</p>
    singulars
    1. This table or related slice is empty.
    1. POPython: switching from optparse to argparse
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHardlyKnowEm
    1. USHardlyKnowEm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPython: switching from optparse to argparse
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COEverything was working fine with `optparse`. But it looks like that `"-4.5.5-double_non-parallel_gcc"` is a "bad option name", and while `optparse` leaves the quotes, `argparse` does not - hence the error. But what about the `2&>` part? It was working fine with `optparse`. It works fine with no 2: `&>`. I can live this way - but isn't it strange? It should be solved. It should work with `2&>` as well.
      singulars
      1. PO
      1. USAdobe
    2. COI've edited my answer above to address your concern. Again, `2&>` is not a real redirection flag; `2>` is, and `&>` is, and even `2>&1`, but not `2&>`. If you don't believe me, try it with a shell built-in: `ls 2&> tmp.txt`. The `&>` captures stderr, so you won't see it immediately, but if you look at tmp.txt you'll see the error message.
      singulars
      1. PO
      1. USHardlyKnowEm
    3. COI've never used `args` indeed. So You solved it all!
      singulars
      1. PO
      1. USAdobe
 

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