Bandit takes longer than 1 hour on phonenumbers v8.5.2 library
Bug #1735559 reported by
Mark MacVicar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bandit |
New
|
Medium
|
Unassigned |
Bug Description
Bandit takes longer than 1 hour on phonenumbers v8.5.2 library
Reproduced in Bandit v1.4.0
Reproducible Steps:
# untar the attached library
# run "bandit -r -lll phonenumbers-
bandit takes over 1 hour to process. I didn't wait for it to complete.
Changed in bandit: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Looks like a lot of time is spent in here initially.
[node_visitor] DEBUG Str(s='474771') 8.5.2/phonenumb ers/carrierdata /data0. py', 'linerange': [4969], 'lineno': 4969, 'import_aliases': {'u': 'util.u'}}
[meta_ast] DEBUG adding node : 0x10c9d9250 [2]
[node_visitor] DEBUG entering: 0x10c9d9250 <class '_ast.Str'> [2]
[node_visitor] DEBUG {'node': <_ast.Str object at 0x10c9d9250>, 'imports': set(['util.u']), 'filename': 'phonenumbers-
[node_visitor] DEBUG visit_Str called (Str(s='474771'))
There is a fairly large hard-coded dictionary that is probably not the most performant.