Upgrade py-ecc past a buggy release, to 1.4.6

[carver]

What was wrong?

py-ecc was pinned to an old version to resolve a bug.

How was it fixed?

Upgrade py-ecc past the buggy release.

Cute Animal Picture

[carver]

Looks like some flake8 errors made it into master. I'll go through all the other PRs/Issues before trying to fix it here.

[veox]

Experiencing same lint CI run failure as here ATM in PR #1579.

(Subscribing myself so I get to see how to fix it.)

[pipermerriam]

Not flake8. It is the new release of py_ecc which now exposes it's type hints, and thus, our type checks are now mad about a few things.

[cburgdorf]

which now exposes it's type hints

PEP561 at work, beautiful

[hwwhww]

@carver @pipermerriam
Fix py_ecc: ethereum/py_ecc#40
py-evm side: hwwhww@a326a0e

• A few FQP_point_to_FQ2_point transformation, not a perfect solution here...
  On the other hand, I'm not sure if we should make it looser by just making all FQ2 and FQ12 type hinting to FQP. Might need to think about it more after or during Library refactor py_ecc#31.

• Also will need another py_ecc version bump + update py-evm requires.

EDIT: Since there's no type hinting for bls12-381, some error won't be shown after #1581 is merged. That also needs to be figured out after bls12-381 has type hinting.

[pipermerriam]

@hwwhww I bumped py_ecc here in the PR

[hwwhww]

@pipermerriam thank you! 👍

@carver hwwhww/py-evm@a326a0e passed the CI: https://circleci.com/gh/hwwhww/py-evm/tree/pr1576