# Changelog¶

## Release 0.2.1¶

• Updates to the latest xoutil release that introduces changes in xoutil.context API.

• A lots of fixes to the xotl.ql.translation.py module. The core translation algorithm is now reasonably tested.

The sub-query interpretation for functions like all_ and other like it, is now implemented and partially tested.

We have also introduced a class-level protocol for instances so that the search space for objects be reduced in the hope of making this translator usable for one-user-only, short-lived applications.

## Release 0.2.0¶

• Another round of redesign has been completed: The old and clunky QueryPart concept was removed, now just expressions, bound terms, and generator tokens <generator token> are the needed.

However a new protocol was introduced.

• Compatible with Python 3.2 out-of-the-box, no need to use the 2to3 script.

• Hooray! We have now a test-bed translator partially implemented. It’s quite new and under-tested and sub-queries functions (like xotl.ql.expressions.all_) are not yet translated.

Although PyPy is not fully supported, it passes all tests of the core language, but fails in the translation. Nevertheless the xotl.ql.translation.py is not meant to be used in production.

## 2012/12/20 - Release 0.1.8¶

• Fixed a bug discovered while cleaning up the implementation. Arguments for N_ARITY functions where not being properly handled.

This was fixed actually by simplifying xotl.ql.core.QueryPart to implement the target protocol to extract is expressions.

• Provides a “wish list” for future releases in Next releases goals.

## 2012/12/18 - Release 0.1.7¶

• Fixes pending bug that make tests fail randomly. Now this is deemed stable enough!

Start developing translators!

• Proposing to release a version 0.2, to mark the current level of maturity.

## 2012/12/08 - Release 0.1.6¶

• Fixes several bugs. But there’s still pending a non-determinancy bug.
• Improved an explanation of internal details of the current implementation.
• Starts to comply more closely with PEP8: Use a single blank line to separate class-level definitions (we used 2); use two blank lines separate module-level definitions.

## 2012/11/05 - Release 0.1.5¶

• Huge revamp of design (again). Introduced the metaphor of “particles bubble” to capture the query expression most precisely.

A draft of the description of “Internal details...” is provided.

## 2012/10/22 - Release 0.1.4¶

• Huge revamp of design. Now I’m proud to say the query language is almost done in its first stage.

Introduces QueryPart, loads of documentation has been updated. Tests for design are now almost done, etc...

You’re encourage to try it!