Pyecore

+++++

**Bugfixes**

- Fix issue with the new version of the ``ordered-set`` dependency. The new
version introduces a change in the way the sublist returned from a slices
is managed. The fix proposed in PyEcore introduces a patch for the
``OrderedSet`` class that proposes the same behavior from the new version
while letting the opportunity to change it when subclassing ``OrderedSet``.

+++++

**Bugfixes**

- Fix issue with empty strings in XMI for 'many' ``EAttribute``.

+++++

**Features**

- Add support for ``tag`` attributes in XMI.
- Add ``URI`` change support for ``Resource``.
- Add patch for ``issubclass`` so the test works regardless the input parameters
are ``EClass`` instances or not.
- Add ``xsi:schemaLocation`` deserialization support.

**Bugfixes**

- Fix bad containment feature value for ``contents`` on ``EAnnotation``.
- Fix resource resolving for non-trivial ``URI``.
- Fix bad crossreferences serialization for "many" features (collections).
- Fix issue for strings serialization in 'many' ``EAttribute``. Issue where
happening when whitespaces were in a String for 'many' ``EAttribute``.

+++++

**Bugfixes**

- Fixed ``many`` faulty computation in cases where ``upper == lower > 1``. This
case is not very common, but it could occurs.
- Fixed missing deserialization for ``EDate`` datatype. The missing method on
resulted in a bad ``str`` object conversion leading to an exception as the
a ``datetime`` object was expected instead of a ``str``.

**Miscellaneous**

- Improve ``many`` derived attribute computation, resulting in performance
improvements.
- Add performance improvement tweaks.
- Move ``dispatch`` from ``pyecore.dispatch`` to ``pyecore.utils``

+++++

**Features**

- Add ``dispatch`` decorator to mimic the ``doSwitch`` from EMF. This
implementation relies on the use of the ``singleDispatch`` decorator and does
not include a ``ComposedSwitch`` equivalent as some restrictions from EMF are
no longer an issue in Python.


**Bugfixes**

- Fixed ``lower`` and ``upper`` derived attributes computation. The previous
implementation were considering the attributes as normal ones instead of
derived ones.

- Fixed merge issue during ``0.8.0`` release. A case test was not properly
working, and models which have crossref towards models that were using
UUID raised an exception.

**Miscellaneous**

- Improved performances of the ``many`` derived attribute.

+++++

**Features**

- Add first support for ``EDerivedCollection``. The derived collections are
obtained from many features that are also marked as derived. A derived
collection does not stores nor gets direct information, instead it fetches
information from other collection, compute a result and store it. In the
realisation, a derived collection will inherits from a generic derived
collection that only proposed an empty implementation. Then, the
implementation must be manually added.

- Add multi-root support for XMI and JSON resources. XMI and JSON with multiple
roots can now be serialized and deserialized. Their handling is pretty
transparent as the addition of a new root goes through the ``append(...)``
method.

- Add a ``remove(...)`` method on resources. This method is pretty much the
opposite of the ``append(...)`` method on resources, it simply remove a
root from the resource.

**Bugfixes**

- Exception when a wrong type value was inserted in a reference for generated
code. The call to the ``EcoreUtils.isinstance`` method were raising an
exception as the last part of the code tries to deal with an unexisting
methods from the generated class.

- Fix ``EProxy`` 'force resolve' for static metamodels. When a proxy is set
towards a static metaclass, the proxy resolution tries to handle the
inverse reference list which only exists in the ``.eClass`` "level".
Consequently, when a static metaclass is used, the corresponding ``EClass``
instance must be used.

**Miscellaneous**

- Add new module for basic values and collections. This module contains the
``ECollection`` and ``EValue`` classes. These class were formerly in the
``ecore`` module, but due to further development, it is better to have it
into a dedicated place. This modification is retrocompatible and invisible
for existing manual/generated code.