Wq

**wq.db 0.7.0** introduces Python 3 and Django 1.7 support, as well as a number of minor bug fixes and API cleanup.

API Improvements
- Support for Python 3 (2). Python 2.7 is still supported (for now), but we strongly recommend using Python 3 for new projects.
- Support for Django 1.7, including new [swapper](https://github.com/wq/django-swappable-models)-enabled Django 1.7 migrations (#28)
- Ability to use [chart](http://wq.io/docs/chart) for arbitrary time series models in addition to [vera](#29).
- Continued to expand test suite (13), wq.app compatibility (25), and documentation (wq/wq7)
- Various minor bug fixes

New Features
- New [mark](http://wq.io/docs/markdown) pattern to support attaching one or more markdown snippets to models (#30)
- `dump_config` command for generating a static [wq config](http://wq.io/docs/config) object to speed up application load (ed14f600694016ab66f7d4b81d50327b17ef3da9). Requires Django 1.7.
- `set_extra_config()` method to define arbitrary wq config properties (570b9ad1d5bef4b9f28c9be1d954b5a0734823d7)

Removed Features
- A number of contrib modules have been extracted into separate PyPI packages (29). This includes [vera](http://wq.io/vera), [dbio](http://wq.io/dbio), and the [media thumbnailer](https://github.com/wq/django-media-thumbnailer) that was previously part of [files](http://wq.io/docs/files). If your code depends on any of these modules, you will need to install them separately and update your import statements (e.g. `from wq.db.contrib.vera import models` -> `from vera import models`.
- Removed support for auto-discovering `views.py` and `serializers.py`. All of your auto-discoverable router configurations should be defined in `rest.py` (12)

This release provides additional improvements to wq.db 0.6.0, particularly to the `wq.db.contrib.dbio` submodule.
- made auto_import a fully async task
- serialize import exceptions with `str()`
- hooks to filter and modify identified metadata
- use timezone-aware now() for `Report.entered`

As part of the [wq 0.6.0](https://github.com/wq/wq/releases/tag/v0.6.0) release, **wq.db 0.6.0** builds on version 0.5.0 with improved server rendering of `*_edit.html` templates, to more closely match how [wq/app.js](http://wq.io/docs/app-js) renders the same screens. In addition, the [dbio](http://wq.io/docs/dbio) module now supports arbitrary [wq.io](http://wq.io/wq.io) IO classes in addition to uploaded files (#26). Finally, this release adds a new `Scatter` backend to [chart](http://wq.io/docs/chart), and number of smaller API improvements and bug fixes.

API improvements
- 5: Improve template rendering (particularly of edit screens) for compatibility with [wq/app.js](http://wq.io/docs/app-js):
- Fully implement `add_lookups()` functionality on `ModelViewSet`
- Render `None` as "" for better compatibility JavaScript Mustache implementation
- Improve pagination and template name detection
- Fix bug that could lead to infinite recursion in nested serializers
- Call component views to ensure proper queryset is used in `multi.json`
- 19: Various optimizations [vera](http://wq.io/vera) and related modules:
- Improved `vera.EventResult` denormalization; optimized `set_for_events` function to update event results based on an event query (rather than raw event ids)
- Improve handling of nested keys
- Improve `Identifier` lookups to exclude `dbio.UnknownItem`
- Added `Scatter` chart support to [wq.db.contrib.chart](http://wq.io/docs/chart)
- 26: Generalize [dbio](http://wq.io/docs/dbio) module
- Provide a new `IoModel` base class for connecting [wq.io](http://wq.io/wq.io) classes to the dbio importer tasks. Subclasses should implement the `load_io()` method. Two working examples are:
- The [File model](https://github.com/wq/wq.db/blob/master/contrib/files/models.py#L92-L97) in `wq.db.contrib.files`, which can handle uploaded spreadsheet data (the original use case for dbio)
- The [DataRequest model](https://github.com/heigeo/climata-viewer/blob/master/db/data/models.py#L76-L81) in the new [climata-viewer project](https://github.com/heigeo/climata-viewer).
- 12: Search for `[myapp].rest` in `wq.db.rest.app.autodiscover()`:
- Rather than overloading `views.py` with both router declarations and actual view definitions, the former can/should now be put in a separate `rest.py`
- The old `autodiscover()` behavior (which searched for `[myapp].views` and `[myapp].serializers`) is deprecated and **will be removed** in wq.db 0.7.0.

Backwards-Incompatible Changes
- `wq.db.contrib.views.FileViewSet` renamed to `IoViewSet` (as part of 26). Some response / context objects have changed.
- Removed response caching functionality which was not being used (27)

Other Changes
- Update generated config object with better foreign key support (wq/wq.app16)
- Update internal `contenttypes` cache usage to match Django 1.6
- Use `application/vnd.geo+json` media type (geojson/draft-geojson24)
- Improved API for retrieving the config for a given model

As part of the [wq 0.5.0 "Charted Waters"](https://github.com/wq/wq/releases/tag/v0.5.0) release, this release of brings a number of enhancements to the data management and exploration capabilities of wq.db. This release also brings a number of improvements and tests for compatibility with Django 1.6.

API improvements
- Restructured the [vera](http://wq.io/vera) module to improve stability and performance (#10, 17).
1. Completely separated the `models` implementation from that of `annotate`. While vera's [ERAV](http://wq.io/docs/erav) data model is logically an extension of [annotate's EAV](http://wq.io/docs/annotate), tying the the implementations together limited the stability of the former and the generality of the latter. Specifically, `BaseParameter` and `BaseResult` are no longer subclasses of `BaseAnnotationType` and `BaseAnnotation`.
2. Added a denormalized `EventResult` model for fast read-only analysis (i.e. charting). This model uses a signal to track changes to the `Event`, `Report`, and `Result` models, automatically maintaining a list of the "authoritative" versions of the Results for each Event-Parameter pair. Since Event and Result may be swapped for user-supplied versions, the actual class definition is created at run time via `create_eventresult_model()`.
- Don't set CRS object when serializing models with simple latitude and longitude in GeoJSON (in 17)

New Modules (in `contrib`)
- **[dbio](http://wq.io/docs/dbio)**: Replaces `vera.io` as part of the above reorganization (#10)
- **[chart](http://wq.io/docs/chart)**: a charting service for [wq.app's](http://wq.io/wq.app) [chart.js](http://wq.io/docs/chart-js) that utilizes the new `vera.EventResult` model. Uses the new [Django REST Pandas](https://github.com/wq/django-rest-pandas) library to facilitated data transformation. (#10, 17)

Other Changes
- Extended the wq.db test suite with tests for `annotate`, `vera`, and `dbio`, and `files`. The plan is that going forward, each improvement to wq.db will generally start as a pull request with a failing test.
- Split the internal `swapper` API into a [separate PyPI module](https://github.com/wq/django-swappable-models)
- Fixed issues with Django 1.6 compatibility in `patterns` (9), and submitted a patch to Django REST Framework (tomchristie/django-rest-framework1318).
- Fixed various issues with nested serializers (4, 15), file management (in 16), and the `{{user}}` context variable (in 10).