With YAQL migration on the way [1] I suggest we include a conversion script to the blueprint [2] and call BP done when conversion in place.
DZ> [1] https://review.openstack.org/#/c/206944/ [2] https://blueprints.launchpad.net/mistral/+spec/yaql-v1-0 On Jun 30, 2015, at 3:43 PM, Thomas Goirand <[email protected]> wrote: > On 06/30/2015 07:09 AM, Dmitri Zimine wrote: >> Thanks Stan, >> >> This release is few more months. How soon? Are you planning to support >> 0.2 in the meantime? >> >> We are really pressed on this transition to 1.0. >> For instance. Number 1 user error while dealing with YAQL is using == >> instead of =. >> We had this discussion and you and Alex and you suggested it’s easy to >> redefine. >> >> But… … The short is we need to move to 1.0 to do it. Because from what I >> figured so far, in 0.2 I can’t naively extend the an operator, as it >> won’t parse. I did make it work on 0.2 but this required a hack in the >> YAQL library itself, need to add ‘==‘ to both lexer.py and parser.py. At >> least what I figured. >> >> I see the tokens are already generalized in 1.0. It doesn’t seem to >> worth backporting it to 0.2, but if this is a way, let us know. >> >> Mistral is betting on YAQL, please help. >> >> DZ. > > FYI, I'm also looking forward switching to Yaql 1.0 on the packaging > level, because 0.2.6 has lost support for Py3 (I added some Py3 patches > in Debian for 0.2.4, but 0.2.6 completely broke that...). > > Cheers, > > Thomas Goirand (zigo) > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
