Release 2.2
New features & enhancements
Tickets closed in this release:
- Non-integer primary keys (#631). Updating features with POST didn't work when the type of the primary key wasn't an integer.
- Be less strict when defining requirements in setup.py (#629).
For further details, see the actual tickets.
For every new non-patch version a new package repository is created. So a new package repository was created for MapFish 2.2: http://www.mapfish.org/downloads/2.2/pkg/. The 2.2 repository includes SQLAlchemy 0.7.1 and GeoAlchemy 0.6. MapFish 2.2 has been tested with these two versions, and things look good.
MapFish 2.2 for Application Developers
With [3778] requirements in the setup.py file of MapFish are defined in a less strict way. They used to be defined like this:
Shapely>=1.2,<=1.2.99
They're now defined like this:
Shapely>=1.2
We decided to do that to give more freedom to application developers. But more freedom also means more responsibility, as working with fixed dependency versions now requires application developers to fix the versions in the setup.py file of their applications.
Application developers that rely on MapFish repositories only for installing and updating MapFish won't really be affected by this change, as the package versions will be fixed by the actual versions available in the MapFish repository. People installing and updating MapFish from http://pypi.python.org should be more cautious.
