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

Refactored code to make Sherlock a proper CLI tool and python package #152

Closed
wants to merge 13 commits into from

Conversation

avinashshenoy97
Copy link
Contributor

@avinashshenoy97 avinashshenoy97 commented Jan 26, 2019

  1. Changed code structure for to be a python package - can create setup.py and register on PyPI to make sherlock pip installable

  2. Moved Sherlock to a class that needs to be instantiated with a username. This sherlock object can be used to check that username on some/all supported sites

  3. Prints and CLI features moved to main.py so that all the findings are printed only when "python sherlock --site " is run.

  4. The site arg can now be "facebook" or even just "face" and it will be matched to facebook because of how the argument is compared to the name of the websites on the supported sites list.

  5. Moved helper functions to watson.py (hehe)

  6. Adding a "loading /" line that shows up while Sherlock analyzes the given username's presence across all the sites.

will be saved at this folder.
--output OUTPUT, -o OUTPUT
If using single username, the output of the result
will be saved at this file.
--tor, -t Make requests over TOR; increases runtime; requires
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get why --rank, --folderoutput and --json were removed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Slight oversight on my part... added them back :)

@hoadlck
Copy link
Contributor

hoadlck commented Jan 26, 2019

This is the 3rd pull request for doing the restructuring. I would like to get from @TheYahya on what is the way forward on these? It does not seem sensible to have multiple people doing the same thing.

@avinashshenoy97
Copy link
Contributor Author

The checks are failing because of a connection error... it's a transient error. If the build is triggered again, it will probably go through.

@TheYahya
Copy link
Contributor

Thank you @avinashshenoy97,
I prefer the way @knijam did at #112 @hoadlck, but it has so many changes and there's so conflicts too.
And I check all of them and compare them.

@hoadlck
Copy link
Contributor

hoadlck commented Apr 30, 2020

Much of the goals in this has been incorporated into #590.

@hoadlck hoadlck closed this Apr 30, 2020
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

Successfully merging this pull request may close these issues.

4 participants