On Mon, Apr 2, 2018 at 8:26 AM, Jim Rollenhagen <j...@jimrollenhagen.com> wrote:
> On Sat, Mar 31, 2018 at 7:24 PM, Matthew Thode <prometheanf...@gentoo.org> > wrote: > >> Here's the current status. I'd like to ask the projects what's keeping >> them from removing pycrypto in facor of a maintained library. >> >> pyghmi: >> - (merge conflict) https://review.openstack.org/#/c/331828 >> - (merge conflict) https://review.openstack.org/#/c/545465 >> - (doesn't change the import) https://review.openstack.org/#/c/545182 > > > Looks like py26 support might be a blocker here. While we've brought > pyghmi into the ironic project, it's still a project mostly built and > maintained > by Jarrod, and he has customers outside of OpenStack that depend on it. > The ironic team will have to discuss this with Jarrod and find a good path > forward. > > My initial thought is that we need to move forward on this, so > perhaps we can release this change as a major version, and keep a py26 > branch that can be released on the previous minor version for the people > that need this on 2.6. Thoughts? > I reached out to Jarrod off-list and sounds like this is roughly the plan: > FWIW, I did at least merge a change to work with cryptodomex and moved pyghmi to that when available (I could not discern a way to have requirements allow one of multiple choices). > > I thought about cryptodome, but that breaks paramiko in that environment. > > I’ll probably do a 1.1.0 that uses cryptography, and continue 1.0 with pycrypto/pycryptodomex. // jim
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev