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:
https://github.com/pecan/pecan/commit/4cfe319738304ca5dcc97694e12b3d2b2e24b1bb
https://github.com/pecan/pecan/commit/b3699aeae1f70b223a84308894523a64ede2b083
https://pypi.python.org/pypi/pecan/1.2.1
Once the dust settles in a few days, I'll re-release the new functionality in
a major point release of pecan.
On 09/26/16 09:21 PM, Dave McCowan (dmccowan) wrote:
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 gates for /master, stable/newton, and stable/mitaka all fail) and a
potential larger impact (changing the return code of REST calls is not
acceptable for a stable API).
Before I start hacking three releases of Barbican to work around Pecan's
change, I'd like to ask: are any other projects having trouble with
Pecan Version 1.2? Would it be possible/appropriate to block this version as
not working for OpenStack?
Thanks,
Dave McCowan
[1]
http://pecan.readthedocs.io/en/latest/changes.html
https://github.com/pecan/pecan/issues/72
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Petrello
Senior Developer, DreamHost
ryan.petre...@dreamhost.com
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
