Re: [openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/30/2017 02:38 PM, Doug Hellmann wrote: > If we only update the constraint list, it would not be safe to > release something that relied on the features in the newer version, > because our minimum version in the global requirements list will > then be wrong. I've gone ahead and abandoned the patch for now. It's not critical at the moment and 2.8.1 should be acceptable for Ocata. Thanks, though! - -- Major Hayden -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYj7SnAAoJEHNwUeDBAR+xpGcP/24gEQq//FLwpiLHvHZRlOe+ Vh7zKzvSrU2KdPUo8dhM6pQdvtqR/j/NnyhkjCqTHyBwj3aG89kFxhpieOTtfy05 frSjzqXcjRG7RPHmTmA6HTkk4b2B+hK/BXgqCaNSzF1mNBoxAhgd54nWYANdp5Z/ 887dpiHYNMtxQ1VWusHrJb/6eefEMybfZH9EqrFgHLzwkITzdmdSFycsdlNnrIMo JtHI5iXxnJ8UX1JKnCEWPG+rpPQ83kp3Vs9Hdx3G7zlZhKafnEDOvdo0JnDzDyVp pD5vzlr9kfwoCtbH5+dCS3rRAT43IjvaqSXKLzMx7pZpWbQyl4wC8+RMyhRYcmnN uVC3uGzuo3jPCmS15Xcq0uBv36iUrqaw75g6wW3eHsFlqKd9HwA05fs2Z73gkdET M6fIva+yjAjTLGFsQS6H452duohxHBqijIfzCNvzEDhb6u7tuG7R2DYx/Yv3czg7 rMDW59Yvt/156H/+Z/zje6NcSyljHK1ACvFh1vWY6uh5j42hCBF64sl3Q8Pxcbsr 50b0QAwUX+YlPkxyLCedEatDZB3ZxV/KvPthCQtRbUv9tkseGRV38USWfC6o51kG 3uI6rOcFsdLAT85Vq8KKSqJFAdYhV56gPRZ9wcXlgSUPK/u1/d7mQXNg1HcMbCFd E810NXJvHf7uJUT1kBYe =UBla -END PGP SIGNATURE- __ 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
Re: [openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint
Excerpts from Major Hayden's message of 2017-01-30 11:55:39 -0600: > Hello there, > > I just submitted a patch[0] to bump Jinja2's upper constraint to 2.9.5. > > We previously set the upper constraint to 2.8.1[1] when a change appeared > that broke Ansible. The bug caused the `groupby` filter to return a > namedtuple and it was fixed later in 2.9.5, which was released[2] two days > ago. Other than that bug, the 2.9.0-2.9.4 releases worked fine. > > Version 2.9.5 also contains two new tests[3] which are very helpful for the > openstack-ansible-security role. > > Would it be possible to get the upper constraint for Jinja2 changed for > Ocata? Thanks! > > [0] https://review.openstack.org/#/c/426857/ > [1] https://review.openstack.org/#/c/418494/ > [2] https://github.com/pallets/jinja/releases/tag/2.9.5 > [3] https://github.com/pallets/jinja/pull/624 > If we only update the constraint list, it would not be safe to release something that relied on the features in the newer version, because our minimum version in the global requirements list will then be wrong. Doug __ 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
[openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello there, I just submitted a patch[0] to bump Jinja2's upper constraint to 2.9.5. We previously set the upper constraint to 2.8.1[1] when a change appeared that broke Ansible. The bug caused the `groupby` filter to return a namedtuple and it was fixed later in 2.9.5, which was released[2] two days ago. Other than that bug, the 2.9.0-2.9.4 releases worked fine. Version 2.9.5 also contains two new tests[3] which are very helpful for the openstack-ansible-security role. Would it be possible to get the upper constraint for Jinja2 changed for Ocata? Thanks! [0] https://review.openstack.org/#/c/426857/ [1] https://review.openstack.org/#/c/418494/ [2] https://github.com/pallets/jinja/releases/tag/2.9.5 [3] https://github.com/pallets/jinja/pull/624 - -- Major Hayden -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYj34YAAoJEHNwUeDBAR+xvCAQAJjzgtP+u8LyQN0C/jZ5Xbe3 OXNO9ENTzPIaGNLt0Tu+vxtFD7n/3V3sksvd4oJC9IfuEWOCBASD8WzBMrPsaJ6n yfuyomemoJnNA8GOVUjGzkOyjZyCnEiiXeHsffsog81She7J4BCCyVmMM+NZYTob cTabwgQCLRUFcmdCOkDsnYyFhc6QZL4QNB3ERi6dMSfwMigmAvfYWqULuLR/puHI 907ePIa5zfbEzUxcEpRMo+m/NdEiE6ILCHWvrWGFzcvo/12wBE6QlrCDKfzVQCt2 GTq3/Dr4gaSeAjzGei5XR8I3IIQ27iCeFfFKiRACd1Dj4xP1IG/BI+7uJSlDotCp UQKmysBjCHolaGsfziwQD5162c57j7MPnBiLPU1tOXYphqkQBVKyd79TPWjxQjah LA+pXK9XBs8YtSUNz0xgGr7NtvfivkIyUdhlbzjcKlsfEc9y3b6Qv4m2Ye3Ixdsv WJ50eZK4wtCZZsXO5fq2oFUHPPofz5+nfFOCaySfw9rz+3pSiw1eVK8wVNzdKaRw JOZpEzh7JAWTLfO+cOTQhlE0S4SqKLmcdjCw9qOf4zAya5nhHPBUescQmzSHmPoB X+K69W3Tr9Db6D35OK0fXDoT7q9IeSSNCv8enNcxXUK66CsywUPpcSUmlUg4I4E3 Y2/uzCSbHSgNexf8Tjc7 =TUs4 -END PGP SIGNATURE- __ 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
