-
Notifications
You must be signed in to change notification settings - Fork 95
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
4.0.1 + mastet: pytest is failing because incorrect pycryptodome module name #302
Comments
This is desirable for us because we don't want to accidentally import the There was a related discussion for Gentoo: #232 |
Hmm .. however https://pypi.org/project/pycryptodomex/ "Source" link points to https://github.com/Legrandin/pycryptodome/ |
It's the same package, it's just that the author toggles a flag in |
What distro is this, by the way? edit: nevermind. Seems to be Fedora 35 |
No I'm using my own distro which ia relatively close to fedora rawhide. |
I'm trying to package your module as an rpm package. So I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesI've tested 4.0.1 + master commits and found that pytest is failing with:
In requirements.txt is listed
pycryptodomex==3.14.1
however looks like that module effectively provides notCryptodome
butCrypto
module.After apply below patch
I was able to pass cleanly test suite
Please let me know do you want that pach as PR.
BTW: fo you have any plans to make new reelease?
Looks all master patches are needed to be able at least build
pykeepass
with latest versions of all required modules so IMO it would be good to make new rel;ease 😄To be honet it would be good to add proper pytest support to not force pass tests/tests.py as param (without that pytest is not able to find units).
The text was updated successfully, but these errors were encountered: