You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command-line interface load and test commands are both documented to take zero or more command module file paths. However, this rule is broken if a glob pattern is specified that matches no files, in which case the program exits early with an error. The following commands should both have the same behaviour run in an empty directory:
python -m dragonfly test
python -m dragonfly test _*.py
The text was updated successfully, but these errors were encountered:
There is a bug here, but the above is not quite right. I think the correct solution is to treat the string as a normal filename if the pattern matches no files.
Fixes#357.
This fixes a bug where non-matching glob patterns are not treated
as normal filenames. For example, if the pattern "_*.py" matches no
files in the working directory, then the *load* and *test* commands
will attempt to use the pattern string as a filename and give the
usual error message if that fails.
The command-line interface load and test commands are both documented to take zero or more command module file paths. However, this rule is broken if a glob pattern is specified that matches no files, in which case the program exits early with an error. The following commands should both have the same behaviour run in an empty directory:
The text was updated successfully, but these errors were encountered: