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
Originally reported byDanek Duvall (Bitbucket: dhduvall, GitHub: dhduvall)
Currently, the --omit processing code specifically looks for glob characters because of limitations of the Windows shell. That said, if you want to omit a module by its name alone, rather than its full path, then you can't do something like
coverage html --omit */cherrypy
If you let the (unix) shell expand that, the expansion may very well fail, preventing the command from running at all. If you escape the glob character from the shell so that it gets passed into coverage raw, then it will attempt to expand that the way the shell does, and will fail the same way.
It would be useful to use fnmatch to filter out patterns, instead of (or in addition to, depending on the argument) startswith().
Originally reported by Danek Duvall (Bitbucket: dhduvall, GitHub: dhduvall)
Currently, the --omit processing code specifically looks for glob characters because of limitations of the Windows shell. That said, if you want to omit a module by its name alone, rather than its full path, then you can't do something like
If you let the (unix) shell expand that, the expansion may very well fail, preventing the command from running at all. If you escape the glob character from the shell so that it gets passed into coverage raw, then it will attempt to expand that the way the shell does, and will fail the same way.
It would be useful to use fnmatch to filter out patterns, instead of (or in addition to, depending on the argument) startswith().
The text was updated successfully, but these errors were encountered: