Allow virtual env creation in dir with leading dash #2415
Following feedback from PR #2399, I decided to close that PR and go in a new direction. Instead of sanitizing the virtualenv name, I fixed how
The test is also a much better representation of the problem, albeit more complex.
Invoke pew with a double dash separator ("--"), to make it clear that the virtualenv name is a positional argument. Since the virtualenv name includes all or at least the beginning of the directory name, trying to create a virtualenv in a directory with a leading dash in its name will cause pew to erroneously parse the virtualenv name as an optional argument. Adding the separator causes the virtualenv name to be parsed correctly. Fixes #439