Hi,
> Keystone client version of the middleware is deprecated and only receiving
> minimal security updates. This code is unlikely to see any real changes due
> it its deprecation and frozen state.
>
> We are evaluating how to remove it from the client lib.
I wrote a patch to remove keystonecl
Keystone client version of the middleware is deprecated and only receiving
minimal security updates. This code is unlikely to see any real changes due it
its deprecation and frozen state.
We are evaluating how to remove it from the client lib.
Sent via mobile
> On Apr 24, 2015, at 00:27, Vic
On Fri, Apr 24, 2015 at 12:36 AM, Victor Stinner
wrote:
> Hi,
>
> I wrote my spec to Port Nova to Python 3:
> https://review.openstack.org/#/c/176868/
>
> >> I squashed all my commits into a single commit of my draft port and I
> pushed it at:
> >>
> https://github.com/haypo/nova/commit/bad54bc2b
On 04/23/2015 11:29 PM, Thomas Goirand wrote:
On 04/23/2015 04:24 PM, Victor Stinner wrote:
Also, on the Python 3 topic, there's still a big issue with memcached
(aka: python-memcache).
Oh, thanks Thomas for the reminder. I just sent a pull request to port
python-memcached to Python 3:
On Fri, Apr 24 2015, Victor Stinner wrote:
> What should we do with the following bug?
>
>"memcache tests are skipped on python 3"
>https://bugs.launchpad.net/python-keystoneclient/+bug/1447731
Check if it applies to keystonemiddleware and if so move it there
otherwise close it?
--
Juli
Hi,
I wrote my spec to Port Nova to Python 3:
https://review.openstack.org/#/c/176868/
>> I squashed all my commits into a single commit of my draft port and I pushed
>> it at:
>> https://github.com/haypo/nova/commit/bad54bc2b278c7c7cb7fa6cc73d03c70138bd89d
>>
>
> I like how the sha1 starts w
Hi,
> The part of keystoneclient that uses the memcached client was deprecated in
> Juno (as it was moved to the keystonemiddleware repo),
Oh, I was not aware of the keystonemiddleware project. I see that Nova uses it
for example.
> so I think we can remove it now.
Do someone know if the mid
On Thu, Apr 23, 2015 at 4:41 AM, Thomas Goirand wrote:
>
>
> On 04/10/2015 09:41 AM, Thierry Carrez wrote:
>
>> Victor Stinner wrote:
>>
>>> I fixed 4 issues with monkey-patching in Python 3 (importlib, os.open(),
>>> threading.RLock, threading.Thread). Good news: the just released eventlet
>>> 0
On 04/23/2015 04:24 PM, Victor Stinner wrote:
Also, on the Python 3 topic, there's still a big issue with memcached
(aka: python-memcache).
Oh, thanks Thomas for the reminder. I just sent a pull request to port
python-memcached to Python 3:
https://github.com/linsomniac/python-memcached
Victor Stinner wrote:
Also, on the Python 3 topic, there's still a big issue with memcached
(aka: python-memcache).
Oh, thanks Thomas for the reminder. I just sent a pull request to port
python-memcached to Python 3:
https://github.com/linsomniac/python-memcached/pull/67
I don't understa
On Thu, Apr 23, 2015 at 12:10 AM, Victor Stinner
wrote:
> Hi,
>
> > How invasive would the port to python3 be?
>
> I squashed all my commits into a single commit of my draft port and I
> pushed it at:
>
> https://github.com/haypo/nova/commit/bad54bc2b278c7c7cb7fa6cc73d03c70138bd89d
I like how t
Excerpts from Victor Stinner's message of 2015-04-23 07:24:06 -0700:
> > Also, on the Python 3 topic, there's still a big issue with memcached
> > (aka: python-memcache).
>
> Oh, thanks Thomas for the reminder. I just sent a pull request to port
> python-memcached to Python 3:
>
>https://gi
> Also, on the Python 3 topic, there's still a big issue with memcached
> (aka: python-memcache).
Oh, thanks Thomas for the reminder. I just sent a pull request to port
python-memcached to Python 3:
https://github.com/linsomniac/python-memcached/pull/67
I don't understand. I saw a lot of "P
On 04/10/2015 09:41 AM, Thierry Carrez wrote:
Victor Stinner wrote:
I fixed 4 issues with monkey-patching in Python 3 (importlib, os.open(),
threading.RLock, threading.Thread). Good news: the just released eventlet
0.17.3 includes these fixes and it is now fully compatible with Python 3! For
Victor Stinner writes:
>> Is there already a static analysis tool that helps find these things? (Would
>> a
>> pylint check for the above be useful? Some of them would be hard to find
>> reliably, but a bunch of the above would be trivial)
>
> I read that hacking has some checks. It's quite easy
Hi,
>> These changes are not enough to port nova to Python 3. But they are required
>> to be able to find next Python 3 bugs.
> Is there already a static analysis tool that helps find these things? (Would
> a pylint check for the above be useful? Some of them would be hard to find
> reliably,
On Thu, 23 Apr 2015 at 17:11 Victor Stinner wrote:
> As announced, changes are boring, just obvious Python2/Python3 issues:
>
> - strip L from long integer literals: 123L => 123
> - replace dict.iteritems() with six.iteritems(dict)
> - replace list.sort(cmp_func) with list.sort(key=key_func)
> -
>> I recommend to use mysqlclient instead of MySQL-python even on
>> Python 2.
>>
>> https://pypi.python.org/pypi/mysqlclient
>> https://github.com/PyMySQL/mysqlclient-python
> Is it packaged in popular distributions? RHEL? Fedora? SuSe? Ubuntu?
> Debian? Gentoo?
If this library solves real bug
Hi,
> How invasive would the port to python3 be?
I squashed all my commits into a single commit of my draft port and I pushed it
at:
https://github.com/haypo/nova/commit/bad54bc2b278c7c7cb7fa6cc73d03c70138bd89d
As announced, changes are boring, just obvious Python2/Python3 issues:
- strip L fr
On Wed, Apr 22, 2015 at 3:15 AM, Victor Stinner wrote:
> Hi,
>
> It's moving fast. I'm currently working on porting remaining libraries to
> prepare my spec for nova.
>
Great, I did't realize how close all the dependencies were.
>
> > oslo.db -- looks like it is almost there
>
> I don't know t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/22/2015 05:02 PM, INADA Naoki wrote:
>
> Hi, All,
>
> My 2c are:
>
> - yes, oslo.db supports python 3 (unittests passes, at least :) ) -
> MySQL-python still default MySQL DB driver in OpenStack, but at
> the moment the only DB driver for My
> Hi, All,
>
> My 2c are:
>
> - yes, oslo.db supports python 3 (unittests passes, at least :) )
> - MySQL-python still default MySQL DB driver in OpenStack, but at the
> moment the only DB driver for MySQL in python3 environment is PyMySQL, so I
> think, it's ok to use it with python 3.
>
>
>
Hi.
Hi, All,
My 2c are:
- yes, oslo.db supports python 3 (unittests passes, at least :) )
- MySQL-python still default MySQL DB driver in OpenStack, but at the
moment the only DB driver for MySQL in python3 environment is PyMySQL, so I
think, it's ok to use it with python 3.
On Wed, Apr 22, 2015 a
On Wed, Apr 22, 2015 at 12:57:01PM +0200, Kashyap Chamarthy wrote:
> On Tue, Apr 21, 2015 at 02:58:57PM -0700, Joe Gordon wrote:
> > On Fri, Apr 17, 2015 at 1:22 AM, Victor Stinner wrote:
> >
> > > >> For the full list, see the wiki page:
> > > >> https://wiki.openstack.org/wiki/Python3#Core_Open
On Tue, Apr 21, 2015 at 02:58:57PM -0700, Joe Gordon wrote:
> On Fri, Apr 17, 2015 at 1:22 AM, Victor Stinner wrote:
>
> > >> For the full list, see the wiki page:
> > >> https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects
> >
> > > Thanks for updating the wiki page that is a very use
Hi,
It's moving fast. I'm currently working on porting remaining libraries to
prepare my spec for nova.
> oslo.db -- looks like it is almost there
I don't know the status of oslo.db support of Python 3. I guess that it already
works on Python 3, it's just a matter of running tests with MySQL
Hi,
sqlachemy-migrate already works on Python3. I sent a patch to add missing
Python 3 classifiers, so the "caniusepython3" automated tool will stop
reporting false alarm on this library.
https://review.openstack.org/174738
Or is someone aware of issues with Python 3?
Again, check the wiki pag
On 21/04/15 21:37, Ian Cordasco wrote:
> Also, isn’t sqlalchemy-migrate something we currently maintain (or a group
> of OpenStack developers do it for OpenStack. Can’t we work with them to
> add support for Python 3?
There seems to have been some work on that already:
https://github.com/stackforg
On Fri, Apr 17, 2015 at 1:22 AM, Victor Stinner wrote:
> >> For the full list, see the wiki page:
> >> https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects
>
> > Thanks for updating the wiki page that is a very useful list.
> > From the looks of things, it seems like nova getting Pytho
On Tue, Apr 21, 2015 at 1:37 PM, Ian Cordasco
wrote:
> On 4/16/15, 17:54, "Clint Byrum" wrote:
>
> >Excerpts from Joe Gordon's message of 2015-04-16 15:15:01 -0700:
> >> On Fri, Apr 10, 2015 at 4:01 AM, Victor Stinner
> >>wrote:
> >>
> >> > > https://wiki.openstack.org/wiki/Python3#Dependencies
On 4/16/15, 17:54, "Clint Byrum" wrote:
>Excerpts from Joe Gordon's message of 2015-04-16 15:15:01 -0700:
>> On Fri, Apr 10, 2015 at 4:01 AM, Victor Stinner
>>wrote:
>>
>> > > https://wiki.openstack.org/wiki/Python3#Dependencies appears to be
>> > fairly out of date.
>> >
>> > You're right. I u
>> For the full list, see the wiki page:
>> https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects
> Thanks for updating the wiki page that is a very useful list.
> From the looks of things, it seems like nova getting Python3 support in
> Liberty is not going to happen.
Why? I plan to
Excerpts from Joe Gordon's message of 2015-04-16 15:15:01 -0700:
> On Fri, Apr 10, 2015 at 4:01 AM, Victor Stinner wrote:
>
> > > https://wiki.openstack.org/wiki/Python3#Dependencies appears to be
> > fairly out of date.
> >
> > You're right. I updated this wiki page. In practice, much more OpenS
On Fri, Apr 10, 2015 at 4:01 AM, Victor Stinner wrote:
> > https://wiki.openstack.org/wiki/Python3#Dependencies appears to be
> fairly out of date.
>
> You're right. I updated this wiki page. In practice, much more OpenStack
> clients, Common Libraries and Development Tools are already Python 3
>
On 2015-04-13 04:03:49 -0400 (-0400), Victor Stinner wrote:
> Great. Did you notice a performance regression?
Nope. Worth noting, we implemented it primarily for its lack of
compiled extensions, and to a lesser because it supports Python 3.x.
I suspect if we do later run into any unexpected perfor
> Worth noting we've already switched to using PyMySQL in nodepool,
> storyboard and some of the subunit2sql tooling. It's been working
> out great so far.
Great. Did you notice a performance regression? Mike wrote that PyMySQL is much
slower than MySQL-Python.
Victor
__
On Thu, Apr 9, 2015 at 9:25 AM, Victor Stinner wrote:
> Hi,
>
> During the last OpenStack Summit at Paris, we discussed how we can port
> OpenStack to Python 3, because eventlet was not compatible with Python 3.
> There are multiple approaches: port eventlet to Python 3, replace eventlet
> with a
Thanks for your work on this! :)
On Thu, Apr 9, 2015 at 7:25 PM, Victor Stinner wrote:
> Hi,
>
> During the last OpenStack Summit at Paris, we discussed how we can port
> OpenStack to Python 3, because eventlet was not compatible with Python 3.
> There are multiple approaches: port eventlet to P
Hi,
During the last OpenStack Summit at Paris, we discussed how we can port
OpenStack to Python 3, because eventlet was not compatible with Python 3. There
are multiple approaches: port eventlet to Python 3, replace eventlet with
asyncio, replace eventlet with threads, etc. We decided to not ta
39 matches
Mail list logo
