0.2.21
0.2.21
-
New: Switched from
nose
+unittest
topytest
as the main testing framework (withpytest-xdist
tests complete 4x faster). -
New: Added
DBSession.save()
shortcut method for convenience which does anadd
oradd_all
(depending to the input) followed by acommit
at once. -
Update: Updated the about page for a more appealing introduction to the library.
-
New: Stalker now creates default
StatusList
forProject
instances on database initialization. -
Update: SQLite3 support is back. In fact it was newer gone. It was dropped for the sake of adding more PostgreSQL oriented features. But then it is recognized that the system can handle both. Though a two new Variant had to be created for JSON and Datetime columns. For simplicity of first time users the default database is again SQLite3.
-
Update: With the reintroduction of SQLite3, the new JSON type column in
WorkingHours
class has been upgraded to support SQLite3. So with SQLite3 the column stores the data as TEXT but seamlessly convert them to JSON when ORM loads or commits the data. -
New: Added
ConfigBase
as a base class forConfig
to let it be used in other config classes. -
Fix: Fixed
testing.create_db()
andtesting.drop_db()
to fallback tosubprocess.check_call
method for Python 2.6. -
Fix: Fixed
stalker.models.auth.User._validate_password()
method to work with Python 2.6. -
Update: Updated all of the tests to use
pytest
style assertions to support Python 2.6 along with 2.7 and 3.0+. -
Fix: Fixed
stalker.db.check_alembic_version()
function to invalidate the connection, so it is not possible to continue with the current session, preventing users to ignore the raisedValueError
when thealembic_version
of the database is not matching thealembic_version
of Stalker's current version.