Pony ORM Release 0.6

Merge branch 'master' into orm

Pony ORM Release Candidate 0.6rc2

Pony ORM Release Candidate 0.6rc1

http://blog.ponyorm.com/2014/10/08/pony-orm-0-6-release-candidate-1

# New features:

* Python 3 support
* pymysql adapter support for MySQL databases

# Backward incompatible changes

Now Pony treats both `str`` and `unicode`` attribute types as they are unicode strings in both Python 2 and 3. So, the attribute declaration `attr = Required(str)` is equal to `attr = Required(unicode)` in Python 2 and 3. The same thing is with `LongStr` and `LongUnicode` - both of them are represented as unicode strings now.

For the sake of backward compatibility Pony adds `unicode` as an alias to `str` and `buffer` as an alias to `bytes` in Python 3.

# Other changes and bug fixes

* Fixes ponyorm#74: Wrong FK column type when using sql_type on foreign ID column
* Fixes ponyorm#75: MappingError for self-referenced entities in a many-to-many relationship
* Fixes ponyorm#80: “Entity NoneType does not belong to database” when using to_dict

Pony ORM release 0.5.4

Pony ORM Release 0.5.3

This release fixes the setup.py problem that was found after the previous release was uploaded to PyPI.

Pony ORM release 0.5.2

http://blog.ponyorm.com/2014/08/11/pony-orm-release-0-5-2/

This release is a step forward to Python 3 support. While the external API wasn't changed, the internals were significantly refactored to provide forward compatibility with Python 3.

# Changes/features:

* New to_dict() method can be used to convert entity instance to dictionary. This method can be useful when you need to serialize an object to JSON or other format

# Bugfixes:

* Now select() function and filter() method of the query object can accept lambdas with closures
* Some minor bugs were fixed

Pony ORM release 0.5.1

# Changes/features:

Before this release, if a text attribute was defined without the max length specified (e.g. `name = Required(unicode)`), Pony set the maximum length equal to 200 and used SQL type `VARCHAR(200)`. Actually, PostgreSQL and SQLite do not require specifying the maximum length for strings. Starting with this release such text attributes are declared as `TEXT` in SQLite and PostgreSQL. In these DBMSes, the `TEXT` datatype has the same performance as `VARCHAR(N)` and doesn't have arbitrary length restrictions.

For other DBMSes default varchar limit was increased up to 255 in MySQL and to 1000 in Oracle.

# Bugfixes:

* Correct parsing of datetime values with T separator between date and time
* Entity.delete() bug fixed
* Lazy attribute loading bug fixed

Pony ORM release 0.5.post1

Pony ORM release 0.5