Other package version constraints have been removed
as they where there to ensure either that the
dependency was new or old enough to work with either
the Django version used or the Python version
available on the system.

More recent versions require jsonfied greater or equal to 3
which itself requires a newer django version.

Samuel GAIST authored 5 years ago and Flavio TARSETTI committed 5 years ago

When pushing a completely new experiment on the platform,
an error occurs when calling update_blocks on the cache
content check. If the object does not exists, then an
exception is rightfully raised. This patch changes that
by using get_or_create like of the outputs handling.

Samuel GAIST authored 5 years ago and Samuel GAIST committed 5 years ago

These are used in some pages but were not listed here.

[conda-env/buildout] Minimize conda environment specification; Update python to 3.6; Use bob/beat-devel for specs; Remove sysegg recipe from buildout files

This avoids the need to build the psycopg2 packages and thus requires
PostgreSQL dependencies.

It's not used anywhere in the code.

Otherwise the version from the CI are used and are too old

Otherwise system eggs for Django 1.9.5 are used on CI

beat.core must be 1.6.x
beat.backend.python must be 1.5.x

This fixes the issue that the examples on the latest master are using
the 1.5 version of the python backend which is not yet released.

Relates to:
beat.examples#12