Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

emails is not defined #17

Closed
Maleus opened this issue Oct 16, 2018 · 5 comments
Closed

emails is not defined #17

Maleus opened this issue Oct 16, 2018 · 5 comments

Comments

@Maleus
Copy link

Maleus commented Oct 16, 2018

File "./InSpy.py", line 89, in
output("csv", args.csv, args.company, domain, employees, emails)
NameError: name 'emails' is not defined

Traceback (most recent call last):
File "./InSpy.py", line 89, in
output("csv", args.csv, args.company, domain, employees, email)
File "/root/tools/InSpy/lib/export.py", line 8, in output
ocsv(file, company, domain, employees, emails)
File "/root/tools/InSpy/lib/export.py", line 21, in ocsv
writer.writerow({"Employee Name": name, "Title": title.replace('&', '&'), "Email": emails[name]})
TypeError: string indices must be integers, not str

@nullg0re
Copy link

nullg0re commented Oct 28, 2018

I'm getting the same thing:
File "./InSpy.py", line 89, in
output("csv", args.csv, args.company, domain, employees, emails)
NameError: name 'emails' is not defined

@jobroche
Copy link
Owner

Will look into this!

@jobroche jobroche added the bug label Oct 29, 2018
@jobroche
Copy link
Owner

jobroche commented Nov 9, 2018

What arguments are you guys using when this happens?

@nullg0re
Copy link

nullg0re commented Nov 9, 2018 via email

ismisepaul added a commit to ismisepaul/InSpy that referenced this issue Jan 18, 2019
Fixes jobroche#17. If no employees are found then 'emails' (line 72) never gets initialised
@jobroche jobroche removed the bug label Feb 12, 2019
@ismisepaul
Copy link

@gojhonny I'm unsure why this was closed when the fix #24 was not merged in?

Was there something else that addressed this problem and if not should this not be reopened until the merge is complete?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants