Interpret wildcards in the file exclusion list

[thilp]

Fix #345.

Hello,

This PR changes _is_file_included so that it also uses fnmatch on the excluded_path_strings argument, allowing that list to contain wildcards.

Rationale:

My projects use Codacy, which in turn relies on Bandit. However, they also have test files mixed with source files, the only difference being that their name is prefixed with test_. The result is that Bandit (and therefore Codacy) is unusable on these projects, because they report hundreds of irrelevant “Use of assert detected”. I figured it would be easier (and safer) to add this feature than deactivate Bandit altogether.

I'm very new to the project so I may have made errors. Please point them out! I would really like to see this feature integrated soon in this nice tool.

[ericwb]

Please also update the README which states:

-x EXCLUDED_PATHS, --exclude EXCLUDED_PATHS
                        comma-separated list of paths to exclude from scan
                        (note that these are in addition to the excluded paths
                        provided in the config file)

exclude_dirs - sections of the path, that if matched, will be excluded from scanning

exclude: comma separated list of excluded paths

And also the man page for the CLI.

[thilp]

@ericwb Thanks, what do you think about it now?

[ericwb]

LGTM

[eterna2]

@ericwb Are u planning a release soon? Cuz I need this feature quite badly as my tests are in the same folders as my sources.

[azrdev]

@thilp when using --recursive the whole path is fnmatched against the glob_list, therefore an --exclude_dir expression test_*.py doesn't matches and excludes (py)test files in subdirectories, for that */test_*.py is needed.

I find this rather unintuitive, was it intended?