Update to new eradicate api

[Cielquan]

Even so the API of eradicate does change the new implementation is not that different.

• I updated the usage of eradicate's API
• I added the new CLI flags: --eradicate-whitelist and --eradicate-whitelist-extend which correspond to the appropriate flags from eradicate.
• I removed the _Options class because I could not find a reason to keep it. Instead it is now a dict.
• I removed the in_place option which was present in the _Options class because this setting only effects Eradicate.fix_file() which is the 'parent' function to the here used Eradicate.filter_commented_out_code() and does not get called.
• I fixed test_incorrect_fixture() which should have failed on current master but does not. I dunno why.
• I added 2 new tests for the new CLI args.
• I updated the docs with the new CLI args

EDIT: when eradicate 2.0.0 is released I will update the dependency and finish this PR. Then the CI should also succeed. I tested all thing the CI does locally with success.

[sobolevn]

Related #161

[coveralls]

Pull Request Test Coverage Report for Build 499

• 12 of 12 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 489:	0.0%
Covered Lines:	41
Relevant Lines:	41

---

💛 - Coveralls

[Cielquan]

So I updated the dependency to eradicate v2.

The failed CI is because of safety complaining about pip<19.2 used in the py35 test.

[sobolevn]

Let's drop py35 then.

[Cielquan]

Let's drop py35 then.

Should I do this in this PR or do u want to do this in another PR?

[sobolevn]

Yes, this PR is fine 👍

[Cielquan]

Py3.5 is dropped.

[sobolevn]

Awesome work! 👍

[Cielquan]

So finally got the time to fix the CI issue.

Hope now its OK?

[sobolevn]

Yes! Great work!

[sobolevn]

Thanks a lot! 👍

[Surgo]

@sobolevn I'm looking forward to it being released it :)

[sobolevn]

Will do soon 🙂