I suggest:
- pin anything that moves
- start being strict ourselves to prepare for moving
- work with paramiko to help them move
Sadly Python doesn't have either-or dependencies as yet, so we're
going to be in the position of having to override pip for some time
during the migration process.
I'm getting these nova tox errors now (from pip-missing-reqs):
Missing requirements:
nova/crypto.py:29 dist=pycrypto module=Crypto.PublicKey.RSA
I think requirements.txt should now include pycrypto ? Or am I missing
something.
Thanks,
/ludovic
-Original Message-
From: Davanum Srinivas
Douglas,
Which means we should make sure pysaml2 and paramiko do switch to the
" pyca/cryptography" ASAP. However, what do we do in the mean time?
-- Dims
On Mon, Feb 15, 2016 at 1:30 PM, Douglas Mendizábal
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
One more thing: I forgot to point out that pyca/cryptography is
already part of global-requirements. [1]
- - Douglas Mendizábal
[1]
http://git.openstack.org/cgit/openstack/requirements/tree/global-require
ments.txt#n25
On 2/15/16 12:24 PM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I had not previously heard of pycryptodome. Is this supposed to be a
drop-in replacement for pycrypto? If so then it sounds like they're
doing a terrible job of it.
The plan for Barbican has been to wait for pyca/cryptography [1] to
add support
On 14/02/16 17:16 -0500, Davanum Srinivas wrote:
Hi,
Short Story:
pycryptodome if installed inadvertently will break several projects:
Example : https://review.openstack.org/#/c/279926/
Long Story:
There's a new kid in town pycryptodome:
https://github.com/Legrandin/pycryptodome
Because
2016-02-14 23:16 GMT+01:00 Davanum Srinivas :
> Hi,
>
> Short Story:
> pycryptodome if installed inadvertently will break several projects:
> Example : https://review.openstack.org/#/c/279926/
>
> Long Story:
> There's a new kid in town pycryptodome:
>