Explicitly declare pyperclip requirement

pyperclip version 1.6.0 introduces an API change: the class `pyperclip.exceptions.PyperclipException` is moved to `pyperclip.PyperclipException`. As mitmproxy uses the latter, it's better to explicitly declare the requirement.
This commit is contained in:
Chih-Hsuan Yen 2018-02-24 00:26:49 +08:00 committed by GitHub
parent 8ef2539426
commit d1ecf9df94
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -75,7 +75,7 @@ setup(
"pyasn1>=0.3.1,<0.5", "pyasn1>=0.3.1,<0.5",
"pyOpenSSL>=17.5,<17.6", "pyOpenSSL>=17.5,<17.6",
"pyparsing>=2.1.3, <2.3", "pyparsing>=2.1.3, <2.3",
"pyperclip>=1.5.22, <1.7", "pyperclip>=1.6.0, <1.7",
"requests>=2.9.1, <3", "requests>=2.9.1, <3",
"ruamel.yaml>=0.13.2, <0.16", "ruamel.yaml>=0.13.2, <0.16",
"sortedcontainers>=1.5.4, <1.6", "sortedcontainers>=1.5.4, <1.6",