On 02/18/2016 08:20 PM, Victor Stinner wrote:
> I discussed with some Trove developers who are interested to start the
> Python 3 port right now. What do you think?
Mitaka b3 is just around the corner (in less than 10 days now), so at
the end, it doesn't change things much, unless all of your patc
Message-
> From: Victor Stinner [mailto:vstin...@redhat.com]
> Sent: Thursday, February 18, 2016 9:42 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] Start to port Trove to Python 3 in
> Mitaka cycle?
>
> Le
Le 18/02/2016 14:15, Amrith Kumar a écrit :
Let's definitely discuss this again once you have all the changes that you feel
should be merged for Mitaka ready.
I don't like working on long patch series. In my experience, after more
than 4 patches, it's more expensive to maintain the patch seri
16
[2] https://review.openstack.org/#/c/256057/
-Original Message-
From: Victor Stinner [mailto:vstin...@redhat.com]
Sent: Thursday, February 18, 2016 7:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [trove] Start to port Trove to Python
6 7:20 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka
> cycle?
>
> Hi,
>
> When I began to work on porting Trove to Python 3, I was blocked by MySQL-
> Python which is no
Hi,
When I began to work on porting Trove to Python 3, I was blocked by
MySQL-Python which is not compatible with Python 3. I tried a big change
replacing MySQL-Python with PyMySQL, since other OpenStack services also
moved to PyMySQL. But tests fail and I'm unable to fix them :-/
https://rev
