Releases: powered-by-wq/vera
vera 1.0.0
vera 1.0.0 builds on the second beta with a couple of improvements for compatibility with the final releases of wq.db 1.0 and Django Data Wizard 1.0.
Changes since vera 1.0 beta 2
- Leverage the new cache option in wq.db (79e58ca, fdc1dd3).
- Invert the relationship between vera and the Django Data Wizard (73e992f, see wq/django-data-wizard#3). Where as the wizard formerly depended on vera, vera now depends on the wizard and implements four wizard templates (serializers), as described in the updated documentation.
Other changes since vera 0.8.0
- Changes in Beta 1
- Compatibility with wq.db 1.0 beta and the new standalone natural-keys library.
- Changes in Beta 2
- Split app into three modules (
vera.params
,vera.series
, andvera.results
) to work around persistent challenges with swappable models (see openwisp/django-swappable-models#12)
- Split app into three modules (
vera 1.0 beta 2
vera 1.0 beta 2 brings a project reorganization to work around issues with swappable models and migrations (see openwisp/django-swappable-models#12). The models have been grouped into three apps without default migrations. Once you have determined which models you want to override (if any), run ./manage.py makemigrations
to have the appropriate vera migrations generated for you.
The models have been renamed as follows:
Old Name | New App | New Name | Notes |
---|---|---|---|
vera.Site |
vera.params |
params.Site |
BaseSite is now an IdentifiedModel. |
vera.ReportType |
vera.params |
params.ReportType |
|
vera.Parameter |
vera.params |
params.Parameter |
|
vera.Event |
vera.series |
series.Event |
|
vera.Report |
vera.series |
series.Report |
|
vera.Result |
vera.results |
results.Result |
A new ValueValidator automatically checks Parameter.is_numeric |
vera.EventResult |
vera.results |
results.EventResult |
The old models (and their base implementations) can be accessed from vera.base_models
:
from vera.base_models import BaseSite
class MySite(BaseSite)
# ...
# settings.py
WQ_SITE_MODEL = "myapp.MySite"
The vera.models
module now serves as a shortcut to access the currently active version of each of the seven models.
from vera.models import Site
from myapp.models import MySite
assert(Site == MySite)
Be sure to update your settings:
INSTALLED_APPS = (
- "vera",
+ "vera.params",
+ "vera.series",
+ "vera.results",
)
vera 1.0 beta
vera 1.0.0b1 is the beta version of the upcoming 1.0 release of vera. The main focus of this release is compatibility with the upcoming wq.db 1.0 release and the new standalone natural-keys library.
vera 0.8.0
vera 0.8.0 brings a number of updates and breaking changes for compatibility with wq.db 0.8.
Some highlights from the wq.db release notes:
- Compatibility with Django 1.8 and Django REST Framework 3
- The charting API has been changed to take advantage of Django REST Pandas 0.4.0.
Be sure to view the release notes for wq.db and Django REST Pandas to see what changes to make in your project.
vera 0.7.0
vera 0.7.0 brings Python 3 & Django 1.7 compatibility, and (more significantly) the transition from a wq.db contrib
module to a full PyPi package (see wq/wq.db#29). The API is the same, but instead of:
from wq.db.contrib.vera.models import BaseEvent
You can just do:
from vera.models import BaseEvent
The full history of the wq.db version of vera has been merged into this repository. In addition, the vera-specific components of wq.db chart have been moved to here (see 5ed6317 and wq/wq.db@8368e88 ).
Be sure to check out the updated readme for new documentation on the models included in vera.
vera 0.6.2
Seventh release of vera, included in wq.db 0.6.2.
vera 0.6.1
Sixth release of vera, included in wq.db 0.6.1.
vera 0.6.0
Fifth release of vera, included in wq.db 0.6.0.
See the climata-viewer project for an example of vera in action.
vera 0.5.0
Fourth release of vera, included in wq.db 0.5.0
vera 0.4.0
Third release of vera, included in wq.db 0.4.0