Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change requirement on pycrypto to pycryptodome #10

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

RobertKirk
Copy link

pycrypto isn't maintained, possibly has some exploits, and doesn't work
on python 3.8. pycryptodome is a maintained alternative that does.

@RobertKirk RobertKirk force-pushed the master branch 2 times, most recently from ebbbef4 to 86054d4 Compare July 7, 2020 10:30
pycrypto isn't maintained, possibly has some exploits, and doesn't work
on python 3.8. pycryptodome is a maintained alternative that does.

Change the location of imports to handle changes in package.
We should use the compatiblity layer for pycrypto as this provides the
behaviour we expect.
@kostas-zealid
Copy link

kostas-zealid commented Mar 18, 2021

Hello, any updates on the above? @leonardocsantoss

This client SDK does not work on python 3.8 because of pycrypto, which in turn pulls in time.clock python interface dependency which is not supported in python 3.8 (was deprecated). So API initialization fails for us in python 3.8.

We have been successfully using this SDK with pycryptodome because it has a pycrypto-compatible interface. But we need to manually replace the dependency and this complicates our deployment process and incurs maintenance overhead.

Can you therefore please merge this?

Thank you
Kostas

@leonardocsantoss
Copy link

I'm not allowed to merge this. So, I made a fork and change this that: https://github.com/leonardocsantoss/trustly-client-python

@kostas-zealid
Copy link

@RobertKirk maybe you have permission to merge?

@kostas-zealid
Copy link

@RobertKirk ping

@RobertKirk
Copy link
Author

@kostas-zealid I don't, it needs at least 1 approving review by a reviewer with write access, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants