Remove pycrypto.

[busunkim96]

Closes #653.

[theacodes]

Honestly both of these libraries are problematic. We should just move to cryptography.

[theacodes]

Well now I'm curious what the dependency was doing at all. 🤷‍♀

[busunkim96]

:) I was about to ask what pycrypto was used for.

There are 3 places PyCrypto is mentioned:

1. tox.ini
2. README as a development dependency
3. Changelog:
   

   google-api-python-client/CHANGELOG

   Lines 323 to 328 in ffea1a7

   	v1.1
   	Version 1.1
   	Add PEM support to SignedJWTAssertionCredentials (used to only support
   	PKCS12 formatted keys). Note that if you use PEM formatted keys you can use
   	PyCrypto 2.6 or later instead of OpenSSL.

If you don't have any concerns, I'll probably delete it. 🤷‍♀️

[theacodes]

Do it.

…

On Mon, Jun 10, 2019, 5:09 PM Bu Sun Kim ***@***.***> wrote: :) I was about to ask what pycrypto was used for. There are 3 places PyCrypto is mentioned: 1. tox.ini 2. README <https://github.com/googleapis/google-api-python-client/blob/d82f3e76180bf822fc01f362e5a119988d896432/README.md#third-party-libraries-and-dependencies> as a development dependency 3. Changelog: https://github.com/googleapis/google-api-python-client/blob/ffea1a7fe9d381d23ab59048263c631cc2b45323/CHANGELOG#L323-L328 If you don't have any concerns, I'll probably delete it. 🤷‍♀ — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#692?email_source=notifications&email_token=AAB5I47XIOBNORDLRH5DWT3PZ3UJ3A5CNFSM4HWX24XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLR5XQ#issuecomment-500637406>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB5I45WGHMV3UOYD7SBHHLPZ3UJ3ANCNFSM4HWX24XA> .