On Sep 4, 2014, at 3:38 AM, Yuriy Taraday wrote:
> On Wed, Sep 3, 2014 at 7:24 PM, Doug Hellmann wrote:
> On Sep 3, 2014, at 5:27 AM, Yuriy Taraday wrote:
>> On Tue, Sep 2, 2014 at 11:17 PM, Clark Boylan wrote:
>> It has been pointed out to me that one case where it won't be so easy is
>> osl
On Thu, Sep 4, 2014 at 4:47 AM, Jeremy Stanley wrote:
> On 2014-09-03 13:27:55 +0400 (+0400), Yuriy Taraday wrote:
> [...]
> > May be we should drop 3.3 already?
>
> It's in progress. Search review.openstack.org for open changes in
> all projects with the topic "py34". Shortly I'll also have some
On Wed, Sep 3, 2014 at 8:21 PM, Doug Hellmann wrote:
>
> On Sep 3, 2014, at 11:57 AM, Clark Boylan wrote:
> > On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote:
> >>
> >> On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote:
> >>> The setup.cfg classifiers should be able to do that for us, though
On Wed, Sep 3, 2014 at 7:24 PM, Doug Hellmann wrote:
>
> On Sep 3, 2014, at 5:27 AM, Yuriy Taraday wrote:
>
> On Tue, Sep 2, 2014 at 11:17 PM, Clark Boylan
> wrote:
>
>> It has been pointed out to me that one case where it won't be so easy is
>> oslo.messaging and its use of eventlet under pytho
On 2014-09-03 13:27:55 +0400 (+0400), Yuriy Taraday wrote:
[...]
> May be we should drop 3.3 already?
It's in progress. Search review.openstack.org for open changes in
all projects with the topic "py34". Shortly I'll also have some
infra config changes up to switch python33 jobs out for python34,
On Sep 3, 2014, at 11:57 AM, Clark Boylan wrote:
> On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote:
>>
>> On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote:
>>
>>> On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
Hello.
Currently for alpha releases of oslo libraries w
On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote:
>
> On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote:
>
> > On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
> >> Hello.
> >>
> >> Currently for alpha releases of oslo libraries we generate either
> >> universal
> >> or Python 2.x-only
On Sep 3, 2014, at 5:27 AM, Yuriy Taraday wrote:
> On Tue, Sep 2, 2014 at 11:17 PM, Clark Boylan wrote:
> On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
> > Hello.
> >
> > Currently for alpha releases of oslo libraries we generate either
> > universal
> > or Python 2.x-only wheels. This
On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote:
> On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
>> Hello.
>>
>> Currently for alpha releases of oslo libraries we generate either
>> universal
>> or Python 2.x-only wheels. This presents a problem: we can't adopt alpha
>> releases in proj
On Tue, Sep 2, 2014 at 11:17 PM, Clark Boylan wrote:
> On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
> > Hello.
> >
> > Currently for alpha releases of oslo libraries we generate either
> > universal
> > or Python 2.x-only wheels. This presents a problem: we can't adopt alpha
> > release
On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
> Hello.
>
> Currently for alpha releases of oslo libraries we generate either
> universal
> or Python 2.x-only wheels. This presents a problem: we can't adopt alpha
> releases in projects where Python 3.x is supported and verified in the
> ga
Hello.
Currently for alpha releases of oslo libraries we generate either universal
or Python 2.x-only wheels. This presents a problem: we can't adopt alpha
releases in projects where Python 3.x is supported and verified in the
gate. I've ran into this in change request [1] generated after
global-r
12 matches
Mail list logo
