On 27/09/2016 01:36, Ryan Petrello wrote:
> Apologies for the trouble this caused. As Dave mentioned, this change
> warranted a new major version of pecan, and I missed it. I've reverted the
> offending commit and re-released a new version of pecan (1.2.1) to PyPI:
>
>
Apologies for the trouble this caused. As Dave mentioned, this change
warranted a new major version of pecan, and I missed it. I've reverted the
offending commit and re-released a new version of pecan (1.2.1) to PyPI:
Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] Pecan Version 1.2
I'm interested to hear how this works out.
I thought upper-constraints was somehow supposed to work to p
ns)"
<openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] Pecan Version 1.2
I'm interested to hear how this works out.
I thought upper-constraints was somehow supposed to work to prevent
this? Like maybe don't install a bra
On 2016-09-26 15:03:19 -0700 (-0700), Clay Gerrard wrote:
[...]
> I thought upper-constraints was somehow supposed to work to prevent this?
> Like maybe don't install a brand new shiny upstream version on the gate
> infrastructure test jobs until it passes all our tests? Prevent a fire
> drill?
to:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] Pecan Version 1.2
I'm interested to hear how this works out.
I thought upper-constraints was somehow supposed to work to prevent this? Like
maybe don't install a brand new shiny upstream version on the gate
infrastr
I'm interested to hear how this works out.
I thought upper-constraints was somehow supposed to work to prevent this?
Like maybe don't install a brand new shiny upstream version on the gate
infrastructure test jobs until it passes all our tests? Prevent a fire
drill? That bug was active back in
The Barbican project uses Pecan as our web framework.
At some point recently, OpenStack started picking up their new version 1.2.
This version [1] changed one of their APIs such that certain calls that used to
return 200 now return 204. This has caused immediate problems for Barbican
(our
