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.

Sign up for GitHub

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

Jump to bottom

Force python3 in all analyzers #361

Closed
4 of 5 tasks
jeromeleonard opened this issue Oct 22, 2018 · 4 comments
Closed
4 of 5 tasks

Force python3 in all analyzers #361

jeromeleonard opened this issue Oct 22, 2018 · 4 comments
Assignees
@nadouani @3c7 @jeromeleonard
Labels
category:enhancement Issue is related to an existing feature to improve scope:analyzer Issue is analyzer related
Milestone
2.4.0

Comments

@jeromeleonard
Copy link
Contributor

jeromeleonard commented Oct 22, 2018 •
edited
Loading

Review all analyzer and make them working with python3 (at leat, try to :) )

List of analyzers that might be reviewed :

  • Abuse_Finder
  • StopForumSpam
  • MaxMind
  • Virustotal

Doc

  • Update "How to create an analyzer"

To be completed
@jeromeleonard jeromeleonard added category:enhancement Issue is related to an existing feature to improve scope:analyzer Issue is analyzer related labels Oct 22, 2018
@Nergie Nergie mentioned this issue Mar 26, 2019
Merged
@LetMeR00t
Copy link
Contributor

LetMeR00t commented Apr 21, 2019 •
edited
Loading

Hi guys,
I proposed this PR for Abuse_Finder but it will need another PR (in the repository abuse_finder) to be used : #469

@nadouani
Copy link
Contributor

Same thing for VirusTotal, the PR #446 solves the issue. We will merge these ASAP

@nadouani nadouani self-assigned this Apr 26, 2019
jeromeleonard added a commit that referenced this issue May 14, 2019
@jeromeleonard
#446 #361 use python3 and the library maintained by blacktop instead …
cd0cf6d 
…of a local one https://pypi.org/project/virustotal-api/
@nadouani
Copy link
Contributor

We need to UP this one

@nadouani nadouani added this to the 2.4.0 milestone Dec 25, 2019
@nadouani
Copy link
Contributor

@3c7 @jeromeleonard Do we need to update the the shebang statement of all the analyzers to replace python with python3?

@dadokkio dadokkio mentioned this issue Feb 5, 2020
Closed
jeromeleonard added a commit that referenced this issue Feb 8, 2020
@jeromeleonard
#361 use python3
f74d6b0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nadouani nadouani

@3c7 3c7

@jeromeleonard jeromeleonard

Labels
category:enhancement Issue is related to an existing feature to improve scope:analyzer Issue is analyzer related
Projects
None yet
Milestone
2.4.0
Development

No branches or pull requests
4 participants
@nadouani @3c7 @LetMeR00t @jeromeleonard