On Aug 24, 2014 9:04 AM, "Morgan Fainberg"
wrote:
>
>
>
> On Sunday, August 24, 2014, Anne Gentle wrote:
>>
>> I'm following this as well since I have the exact same problem in a
docstring patch for heat.
>>
>
> Keystone saw an oddity with the new sample config generator (changing how
options are
On Aug 24, 2014, at 12:30 PM, Ruslan Kamaldinov
wrote:
> On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer wrote:
>> What I really need to know is what to do when committing a change that
>> really does require a change in the sample configuration file. Of course I
>> tried running generate_sa
k Development Mailing List (not for usage questions)"
> > ,
> > Date: 08/24/2014 12:32 PM
> > Subject: Re: [openstack-dev] [heat] "heat.conf.sample is not up to date"
> >
> > On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer
> wrote:
> > > What I rea
Ruslan Kamaldinov wrote on 08/24/2014 12:30:04
PM:
> From: Ruslan Kamaldinov
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 08/24/2014 12:32 PM
> Subject: Re: [openstack-dev] [heat] "heat.conf.sample is not up to date"
&g
On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer wrote:
> What I really need to know is what to do when committing a change that
> really does require a change in the sample configuration file. Of course I
> tried running generate_sample.sh, but `tox -epep8` still complains. What is
> the right
Morgan Fainberg wrote on 08/24/2014 12:01:37
PM:
> ...
>
> Keystone saw an oddity with the new sample config generator
> (changing how options are sorted and therefore changing the way the
> sample config is rendered). This could be a similar / related issue.
>
> Most of the projects stoppe
On Sunday, August 24, 2014, Anne Gentle wrote:
> I'm following this as well since I have the exact same problem in a
> docstring patch for heat.
>
>
Keystone saw an oddity with the new sample config generator (changing how
options are sorted and therefore changing the way the sample config is
ren
/24/2014 05:00:21 AM:
>
> > From: Clint Byrum
> > To: openstack-dev ,
> > Date: 08/24/2014 05:02 AM
> > Subject: Re: [openstack-dev] [heat] "heat.conf.sample is not up to date"
> >
> > Guessing this is due to the new tox feature which randomizes pyth
The differences do not look to me like ones that would follow from a
difference in hash seed.
Clint Byrum wrote on 08/24/2014 05:00:21 AM:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 08/24/2014 05:02 AM
> Subject: Re: [openstack-dev] [heat] "heat.conf.sample
Guessing this is due to the new tox feature which randomizes python's
hash seed.
Excerpts from Mike Spreitzer's message of 2014-08-24 00:10:42 -0700:
> What is going on with this? If I do a fresh clone of heat and run `tox
> -epep8` then I get that complaint. If I then run the recommended comma
10 matches
Mail list logo