dave.pawson at gmail.com
Thu Dec 8 16:47:01 UTC 2016
On 8 December 2016 at 12:46, Martin Falatic <martin at falatic.com> wrote:
> When you run `pip2.7 list` (pretty sure that's what you need for python2,
> or `pip list` may be the defacto python2 pip on Fedora) and `pip3.5 list`
> (for python3), what are you seeing in the area of "pycrypto*" for each of
> these? I'm hopeful that once you have the proper libs installed for
> python3 via pip3.5 things should work better.
pip2 list | grep crypt
No such thing as pip3.x
dnf install python3-pip
Last metadata expiration check: 0:00:48 ago on Thu Dec 8 16:40:04 2016.
Package python3-pip-8.1.2-2.fc25.noarch is already installed, skipping.
Nothing to do.
dnf info python3-pip
Last metadata expiration check: 0:03:38 ago on Thu Dec 8 16:40:04 2016.
Name : python3-pip
Arch : noarch
Epoch : 0
Version : 8.1.2
Release : 2.fc25
Size : 8.6 M
Repo : @System
>From repo : fedora
Summary : A tool for installing and managing Python3 packages
URL : http://www.pip-installer.org
License : MIT
Description : Pip is a replacement for `easy_install
It uses mostly the
: same techniques for finding packages, so packages that were made
: easy_installable should be pip-installable as well.
Looks like python3-pip is pip?
# pip -V
pip 9.0.1 from /usr/lib/python2.7/site-packages (python 2.7)
So (possibly?) there is a pip looking at python3.
> Normally you'd use the pip variant for python3 (e.g., pip3.5) to install
> packages for python3. Can you give that a look and retry?
> Note that I'm not an expert on pycryptodome - my understanding is that
> pycryptodome can be used instead of pycrypto, and it seems to work fine on
> Windows (and I don't have reason to think it'd be any different on Linux).
> I have no experience with pycryptodomex currently. I have pycryptodome
> installed on python 2.7 and 3.5 on my Windows box (and pycrypto NOT
> installed on either) and the test you described ran fine for both.
> That said, if this continues, what version of Fedora are you running? I
> can stand up a VM and see for myself.
Latest - Fedora 25.
Is there a separate mailing list for pycryptodome?
Perhaps I should ask there?
> - M
> On Thu, December 8, 2016 01:44, Dave Pawson wrote:
>> Additional information.
>> pip install pycryptodomex Requirement already satisfied: pycryptodomex in
>> File "/usr/lib64/python3.5/site-packages/Crypto/Cipher/blockalgo.py",
>> line 141, in __init__ self._cipher = factory.new(key, *args, **kwargs)
>> ValueError: IV must be 16 bytes long
>> So (since I'm using python3) it's picking up the Crypto library from
>> python 3.5 and pip is installing it in python 2.7
>> (aside. Yum no longer used in Fedora, just replace with dnf)
>> python3 -m Cryptodome.Selftest /usr/bin/python3: Error while finding spec
>> for 'Cryptodome.Selftest' (ImportError: No module named 'Cryptodome')
>> regards Dave
>> On 8 December 2016 at 09:20, Dave Pawson <dave.pawson at gmail.com> wrote:
>>> python3 -m Cryptodome.SelfTest /usr/bin/python3: Error while finding
>>> spec for 'Cryptodome.SelfTest' (ImportError: No module named
>>> python3 exp1.py Traceback (most recent call last):
>>> File "exp1.py", line 12, in <module>
>>> cipher = AES.new(key, AES.MODE_EAX) AttributeError: module
>>> 'Crypto.Cipher.AES' has no attribute 'MODE_EAX'
>>> which seems to be true
>>> dir(AES) ['AESCipher', 'MODE_CBC', 'MODE_CFB', 'MODE_CTR', 'MODE_ECB',
>>> 'MODE_OFB', 'MODE_OPENPGP', 'MODE_PGP', '_AES', '__builtins__',
>>> '__cached__', '__doc__', '__file__', '__loader__', '__name__',
>>> '__package__', '__revision__', '__spec__', 'block_size', 'blockalgo',
>>> 'key_size', 'new']
>>> Bugs in docs? Library?
>>> Suggestions please.
>>> Dave Pawson
>>> XSLT XSL-FO FAQ.
>>> Docbook FAQ.
>> Dave Pawson
>> XSLT XSL-FO FAQ.
>> Docbook FAQ.
>> pycrypto mailing list pycrypto at lists.dlitz.net
> pycrypto mailing list
> pycrypto at lists.dlitz.net
XSLT XSL-FO FAQ.
More information about the pycrypto