-
Notifications
You must be signed in to change notification settings - Fork 636
time.clock is deprecated - python 3.7 #283
Comments
|
Note that pycrypto does not work with python 3.8 since they removed `time.clock` altogether. pycrypto/pycrypto#283
Note that pycrypto does not work with python 3.8 since they removed `time.clock` altogether. pycrypto/pycrypto#283
python 3.8 is now the official 3 for docker images This problem has then to be solved for most people who will use python 3 with docker. We have the problem, as we use a docker container for encrypting fake data in our travis process (https://github.com/histovec/histovec-beta/). Even if the resource is not critical for our project, is would seem hygienic to solve this
Users of the Crytpo lib with docker must now downgrade using a |
Thanks. Please note that this library has been deprecated and one should
switch to pycryptodome for an API-compatible, updated lib, or to
cryptography.io for a more modern API.
…On Thu, Jan 9, 2020, 2:05 PM Fabien Antoine ***@***.***> wrote:
python 3.8 is now the official 3 for docker images
This problem has then to be solved for most people who will use python 3
with docker.
We have the problem, as we use a docker container for encrypting fake data
in our travis process (https://github.com/histovec/histovec-beta/). Even
if the resource is not critical for our project, is would seem hygienic to
solve this
...
iv = Random.new.read(AES.bloc_ksize)
File "/usr/local/lib/python3.7/site-packages/Crypto/Random/_UserFriendlyRNG.py", line 202, in read
return self._singleton.read(bytes)
File "/usr/local/lib/python3.7/site-packages/Crypto/Random/_UserFriendlyRNG.py", line 178, in read
return _UserFriendlyRNG.read(self, bytes)
File "/usr/local/lib/python3.7/site-packages/Crypto/Random/_UserFriendlyRNG.py", line 129, in read
self._ec.collect()
File "/usr/local/lib/python3.7/site-packages/Crypto/Random/_UserFriendlyRNG.py", line 77, in collect
t = time.clock()
DeprecationWarning: time.clock has been deprecated in Python 3.3 and will be removed from Python 3.8: use time.perf_counter or time.process_time instead
Users of the Crytpo lib with docker must now downgrade using a FROM
python:3.7-slim (or FROM python:3.7) instead of FROM python:3-slim (or FROM
python:3) in their Dockerfile, at least until the problem has been fixed
and close here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#283>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKTFVIWKFCK5M4CY4P64GDQ44OJVANCNFSM4GS7HDWA>
.
|
Thank your for your response - this explanation is profitable ! |
@ErwinHaasnoot if this library is deprecated, could it be marked as such on PyPI, GitHub and other relevant pages? It is not clear when stumbling across the project from search results. I luckily found it when running into this Python 3.8 incompatibility. |
That would be great. Unfortunately I don't have commit rights; maybe a
merge request would be accepted if sent.
…On Sat, Feb 8, 2020, 2:37 AM Chad Smith ***@***.***> wrote:
@ErwinHaasnoot <https://github.com/ErwinHaasnoot> if this library is
deprecated, could it be marked as such on PyPI, GitHub and other relevant
pages? It is not clear when stumbling across the project from search
results. I luckily found it when running into this Python 3.8
incompatibility.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#283>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKTFVKXCR6VMTAKBCZ23YDRBYEFPANCNFSM4GS7HDWA>
.
|
Please fix this bug, downgrade to 3.7 is not the acceptable solution |
2020 and still no fixed yet |
@SwapnilSoni1999 see above:
|
Okay thanks tho <3 |
Good idea #283 (comment) |
+1 to waiters |
Please try this polyfill
|
+1 to waiters |
+1 for waiter |
1 similar comment
+1 for waiter |
+1 |
waiter++ |
waiter-- |
When using RSA encrypt with PKCS1_AOEP padding, DeprecationWarnings are thrown.
Prerequisites: an RSA private key in mykey.pem
openssl genrsa -out mykey.pem 1024
Run the following with the "-W error" option to trigger the warning and print stacktrace:
The text was updated successfully, but these errors were encountered: