Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Wang, Peter Xihong
intel.com> Subject: Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography) On 31 May 2017, at 5:34, Monty Taylor wrote: > On 05/31/2017 06:39 AM, Sean McGinnis wrote: >> On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: >>> W

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Sean McGinnis
> Just a couple things (I don't think it changes the decision made). > > Cryptography does at least claim to support PyPy (see > https://pypi.python.org/pypi/cryptography/ trove identifiers), so > possibly a bug on their end that should get filed? > > Also, our user clients should probably run

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread John Dickinson
On 31 May 2017, at 5:34, Monty Taylor wrote: > On 05/31/2017 06:39 AM, Sean McGinnis wrote: >> On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: >>> We had a discussion a few months back around what to do for cryptography >>> since pycrypto is basically dead [1]. After some

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Clark Boylan
On Wed, May 31, 2017, at 07:39 AM, Sean McGinnis wrote: > On Wed, May 31, 2017 at 09:47:37AM -0400, Doug Hellmann wrote: > > Excerpts from Monty Taylor's message of 2017-05-31 07:34:03 -0500: > > > On 05/31/2017 06:39 AM, Sean McGinnis wrote: > > > > On Wed, May 31, 2017 at 06:37:02AM -0500, Sean

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Sean McGinnis
On Wed, May 31, 2017 at 09:47:37AM -0400, Doug Hellmann wrote: > Excerpts from Monty Taylor's message of 2017-05-31 07:34:03 -0500: > > On 05/31/2017 06:39 AM, Sean McGinnis wrote: > > > On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: > > >> > > >> I am not aware of anyone using

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Doug Hellmann
Excerpts from Monty Taylor's message of 2017-05-31 07:34:03 -0500: > On 05/31/2017 06:39 AM, Sean McGinnis wrote: > > On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: > >> We had a discussion a few months back around what to do for cryptography > >> since pycrypto is basically dead

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Monty Taylor
On 05/31/2017 06:39 AM, Sean McGinnis wrote: On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: We had a discussion a few months back around what to do for cryptography since pycrypto is basically dead [1]. After some discussion, at least on the Cinder project, we decided the best

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Sean McGinnis
On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: > We had a discussion a few months back around what to do for cryptography > since pycrypto is basically dead [1]. After some discussion, at least on > the Cinder project, we decided the best way forward was to use the > cryptography

[openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

2017-05-31 Thread Sean McGinnis
We had a discussion a few months back around what to do for cryptography since pycrypto is basically dead [1]. After some discussion, at least on the Cinder project, we decided the best way forward was to use the cryptography package instead, and work has been done to completely remove pycrypto