2013-08-30 16:15:47 +02:00
|
|
|
|
|
|
|
|
.. _changelog:
|
|
|
|
|
|
|
|
|
|
Changelog
|
|
|
|
|
=========
|
|
|
|
|
|
2013-09-02 17:13:36 +02:00
|
|
|
This document describes the main changes in TRIQS.
|
|
|
|
|
|
2014-07-23 17:25:02 +02:00
|
|
|
version 1.2.0
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
* New C++/Python wrapper generator.
|
|
|
|
|
* HDF5 cleaned, now using only C library (not C++) for simpler installation.
|
|
|
|
|
|
2013-10-16 17:36:19 +02:00
|
|
|
version 1.1.0
|
|
|
|
|
-------------
|
2013-09-02 17:13:36 +02:00
|
|
|
|
2013-10-16 17:36:19 +02:00
|
|
|
* New constructors for the gf [api change]
|
|
|
|
|
* Fix for gf expression templates
|
|
|
|
|
* The gf tails now have fixed size to avoid mpi problems
|
|
|
|
|
* Fixes in gf expression templates
|
|
|
|
|
* New python random generator interface
|
|
|
|
|
* Fixes for issues #11, #18, #25
|
2013-09-11 18:23:38 +02:00
|
|
|
|
|
|
|
|
version 1.0.0
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
There have been changes from versions 0.x to 1.0.0 that will most likely have
|
2013-09-02 17:13:36 +02:00
|
|
|
consequences for your scripts and archives.
|
2013-08-30 16:15:47 +02:00
|
|
|
|
|
|
|
|
Python classes
|
2013-09-02 17:13:36 +02:00
|
|
|
~~~~~~~~~~~~~~
|
2013-08-30 16:15:47 +02:00
|
|
|
|
|
|
|
|
The number of python classes in the old 0.x releases was increasing with no
|
|
|
|
|
clear naming convention. In TRIQS 1.0 we have unified the naming of the classes
|
|
|
|
|
following the `PEP naming conventions
|
|
|
|
|
<http://www.python.org/dev/peps/pep-0008/#naming-conventions>`_:
|
|
|
|
|
|
|
|
|
|
* Package and module names: lowercase with underscores
|
|
|
|
|
* Class names: CapWords
|
2013-09-02 17:13:36 +02:00
|
|
|
* Function names: lowercase with underscores
|
2013-08-30 16:15:47 +02:00
|
|
|
* Function and method arguments: lowercase with underscores
|
|
|
|
|
|
|
|
|
|
Archives
|
2013-09-02 17:13:36 +02:00
|
|
|
~~~~~~~~
|
|
|
|
|
|
|
|
|
|
We provide :download:`an update script <scripts/update_archive.py>` which should
|
|
|
|
|
help you upgrade your archive. The usage is very simple::
|
2013-08-30 16:15:47 +02:00
|
|
|
|
2013-09-02 17:13:36 +02:00
|
|
|
$ python update_archive.py old_archive new_archive
|
2013-08-30 16:15:47 +02:00
|
|
|
|
2013-09-02 17:13:36 +02:00
|
|
|
where ``old_archive`` is your old archive to be upgraded and ``new_archive`` is
|
|
|
|
|
the name of the new archive. If you encounter problems please post an
|
|
|
|
|
issue with a copy of your archive.
|
