Re: py3k - I think we're really close - I've rebased my local kgiusti-python3 
to latest trunk, and have a few bugs to sort out but I don't think that will 
take too long.

The one missing 'feature' I had planned for py3: modify the tox tests to 
automagically run under all installed versions of python.   

But this all should be do-able before the end of the month IMHO.



----- Original Message -----
> From: "Flavio Percoco" <fla...@redhat.com>
> To: "Rafael Schloming" <r...@alum.mit.edu>
> Cc: us...@qpid.apache.org, proton@qpid.apache.org
> Sent: Wednesday, June 17, 2015 2:20:09 AM
> Subject: Re: Can we release proton 0.10? Can we add Py3K to that release?
> 
> On 16/06/15 23:38 -0400, Rafael Schloming wrote:
> >I'd like to get the proton-j-reactor branch into 0.10 also. It should be
> >ready
> >soon, so if py3k can be sorted and merged in a similar timeframe we could
> >target a release for the end of the month.
> 
> This sounds awesome, I think it can be done based on the latest email
> from Ken about Py3K.
> 
> Thanks,
> Flavio
> 
> >
> >--Rafael
> >
> >On Tue, Jun 16, 2015 at 3:32 PM, Flavio Percoco <fla...@redhat.com> wrote:
> >
> >    Greetings,
> >
> >    I've been looking with great pleasure all the progress happening in
> >    proton lately and I was wondering whether it'd be possible to have an
> >    0.10 release cut soon.
> >
> >    There are some bugfixes I'm personally interested in but also some
> >    important changes (specifically in the python bindings) that will make
> >    consuming proton easier for users (OpenStack among those).
> >
> >    Is there a chance for the above to happen any time soon?
> >
> >    Can I push my request a bit further and ask for the py3k code to be
> >    merged as well?
> >
> >    All the above are key pieces to make proton more consumable and allow
> >    for services like OpenStack to fully adopt it.
> >
> >    Thanks,
> >    Flavio
> >
> >    --
> >    @flaper87
> >    Flavio Percoco
> >
> >
> 
> --
> @flaper87
> Flavio Percoco
> 

-- 
-K

Reply via email to