title: Debugging with PyCharm and support for bash globbing
body: <p>My Python script is intended to iterate over all files given as arguments with the following usage:</p>
  <pre><code>usage: make_it_so.py [-h] filename [filename ...]
  
  Make this and that
  
  positional arguments:
    filename
  
  optional arguments:
    -h, --help  show this help message and exit
  </code></pre>
  <p>To run it I tend to use bash globbing because there are more than one file. Also, I like to stress test any script to ensure it is working properly with folders and files containing white-spaces, like so:</p>
  <pre><code>user@host:~$ ./make_it_so.py /path\ containing\ whitespaces/*.csv
  </code></pre>
  <p>or</p>
  <pre><code>user@host:~$ ./make_it_so.py '/path containing whitespaces/*.csv'
  </code></pre>
  <p>Until now I am programming mainly using a plain text editor and the terminal. But now I would like to use an IDE like PyCharm to debug scripts more comfortably. And here comes my question:</p>
  <p><strong>How to configure a debug configuration</strong> to</p>
  <ul>
  <li>either make use of file glob*bing or</li>
  <li>setting several file path arguments with white-spaces?</li>
  </ul>
  <p>(See an example of my debug configuration below.)</p>
  <p><a href="https://i.stack.imgur.com/tAoTG.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/tAoTG.png" alt="enter image description here" /></a></p>
  <p>The argument list I get inside my script is not what I expect:</p>
  <pre class="lang-py prettyprint-override"><code>['/path', 'containing', 'whitespaces/*.csv', &quot;'/path&quot;, 'containing', 'whitespaces/1st', &quot;file.csv'&quot;, '/path\\', 'containing\\', 'whitespaces/2nd', 'file.csv']
  </code></pre>
  <p>Instead I would expect:</p>
  <pre class="lang-py prettyprint-override"><code>['/path containing whitespaces/1st file.csv', '/path containing whitespaces/2nd file.csv']
  </code></pre>
  <p>I am aware of the fact, that the <em>parameters</em> entry field in the debug configuration of PyCharm is not a bash. But I would expect to make it possible to pass arguments containing white-spaces, somehow.—Any suggestions?</p>