Releases: azavea/django-queryset-csv
1.1.0
1.0.3
1.0.2
1.0.1
Add support for Python 3.5 and Django 1.10
new features
- add support for Python 3.5 and Django 1.10
breaking changes
- Switches
render_to_csv_response
to return aStreamingHttpResponse
, which is technically a breaking change, though in practice this should not affect most use cases. If you need aHttpResponse
instead, passstreaming=False
when calling the function. - Dropped support for Django 1.5-1.7
Add support for Django 1.9
Add support for Django 1.9, fix bugs in field header resolution.
Fix interaction between custom header map and extra select columns
Fix bug clobbering custom field headers when also providing extra select columns.
Handle Unicode in field names
Previous releases automatically utf8 encoded field values, this release expands on this to also encode field names, including verbose names and custom overrides.
This release also introduces official support for django 1.8.
Add new features
WARNING: this release no longer localizes values by default
new features
- add support for aggregation fields in querysets
- allow custom serialization of fields (columns) by name
breaking changes
Localization has been turned off by default, so django's localize
function will no longer be called on values before they are exported. This is considered a breaking change. The decision was made in light of the fact that CSVs exist first and foremost as a data exchange format, while localization increases human-readability at the expense of machine-readability. This was modified in response to a need presented by a downstream project.
Add support for csv writer keyword arguments
0.2.10 Merge pull request #58 from azavea/topic/54_56_add_support_for_csv_kw…