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
Great, so in response to your email (below) and Flavio's email [1], I submit to
you that the way to handle this is as we had discussed at earlier meeting(s)
and that is to wait for Newton.
Thanks,
-amrith
[1] http://openstack.markmail.org/thread/4uksb3kmhnagoc5a
> -Original Message-
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
On 18/02/16 13:15 +, Amrith Kumar wrote:
Victor, thanks for the changes and the patch sets.
TL;DR: We've discussed this a couple of times already, once at a Trove
meeting[1], once at length at the midcycle, and concluded that post-Mitaka is
the right time to merge changes relative to
Victor, thanks for the changes and the patch sets.
TL;DR: We've discussed this a couple of times already, once at a Trove
meeting[1], once at length at the midcycle, and concluded that post-Mitaka is
the right time to merge changes relative to Python 3. Once you have all the
changes that you
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 :-/
