| Commit message (Expand) | Author | Age |
|---|
| * | Update django-debug-toolbar from 1.8 to 1.9.1 | pyup-bot | 2018-04-26 |
| * | requirements: Use 'psycopg2-binary' package•••This resolves a deprecation warning that's recently been raised:
UserWarning: The psycopg2 wheel package will be renamed from release
2.8; in order to keep installing from binary please use "pip install
psycopg2-binary" instead. For details see:
<http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2018-02-13 |
| * | Support testing with PostgreSQL•••This allows us to easily test against PostgreSQL using the same
tooling we normally use. This is helpful in (for example) shaking
out the test failures that were observed on ozlabs.org
To use it:
docker-compose -f docker-compose-pg.yml <usual argument>
(You may find in necessary to do a 'docker-compose down' first,
depending on what state the system is in and what command you're
running.)
Signed-off-by: Daniel Axtens <dja@axtens.net>
Reviewed-by: Stephen Finucane <stephen@that.guru>
| Daniel Axtens | 2017-10-28 |
| * | Update django-debug-toolbar from 1.7 to 1.8•••Reviewed-by: Stephen Finucane <stephen@that.guru>
| pyup-bot | 2017-05-18 |
| * | Don't limit selenium to the any MINOR version | pyup-bot | 2017-04-14 |
| * | Pin selenium to latest version 3.3.x | pyup-bot | 2017-03-13 |
| * | Update django-debug-toolbar from 1.6 to 1.7 | pyup-bot | 2017-03-05 |
| * | Revert "requirements: Test older versions of DRF"•••This partially reverts commit febad055fb6609369f1a465a5eec323549c5c065.
While Django REST Framework works with Django 1.6 and 1.7, the versions
of Django Filters that provide DRF integration do not [1]. It doesn't
really make sense to enable only partial REST API support (i.e. no
filtering) for users with older Django versions and this approach will
cause far too much confusion among users. Better to just drop REST API
support for users with these insecure versions and encourage them to
update to supported versions of Django should they wish to use these
features.
[1] https://github.com/carltongibson/django-filter/blob/0.15.0/CHANGES.rst
Signed-off-by: Stephen Finucane <stephen@that.guru>
Fixes: 0fc32337 ("REST: Integrate django-filter support")
| Stephen Finucane | 2017-01-22 |
| * | REST: Integrate django-filter support•••This mostly works out of the box, thanks to Django REST Framework.
Mostly unique fields, like name or email, are excluded as these will be
handled separately.
Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2017-01-22 |
| * | requirements: Test older versions of DRF•••We still care about Django 1.6 and 1.7, at least until 2.0 is released.
Start testing REST functionality on these versions by using older
versions.
Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2016-11-18 |
| * | requirements: Bump django-rest-framework to 3.5•••This requires explicitly declaring the 'field' parameter.
Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2016-11-18 |
| * | requirements: Bump selenium to 3.0•••3.0 introduces no notable changes for our use cases. Use the latest and
greatest.
Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2016-11-18 |
| * | requirements: Bump django-debug-toolbar to 1.6•••1.6 introduces little to no changes [1]. We already use the explicit
setup, so simply switch to the latest and greatest version.
[1] https://django-debug-toolbar.readthedocs.io/en/1.6/changes.html
Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2016-11-18 |
| * | requirements: Loosen requirements for RDBMS libs•••Signed-off-by: Stephen Finucane <stephen@that.guru>
| Stephen Finucane | 2016-11-18 |
| * | requirements: Bump django-rest-framework to 1.4.x•••This version is compatible with all versions of Django that Patchwork
is recommended for.
Signed-off-by: Stephen Finucane <stephen@that.guru>
Reviewed-by: Daniel Axtens <dja@axtens.net>
| Stephen Finucane | 2016-10-10 |
| * | requirements: Update django debug toolbar to 1.5•••This is the latest version. This breaks compatibility with Django 1.7,
but this version is unsupported and should not be used for development.
We do, however, continue to test support for Django 1.7 and 1.6.
This also prevents the need to manually track sqlparse dependency [1].
[1] https://github.com/jazzband/django-debug-toolbar/issues/856
Signed-off-by: Stephen Finucane <stephenfinucane@hotmail.com>
| Stephen Finucane | 2016-09-01 |
| * | REST: Add Patch Checks to the API•••This exports patch checks via the REST API.
The drf-nested-routers package is used to handle the fact Checks are
nested under a Patch.
Security Constraints:
* Anyone (logged in or not) can read all objects.
* No one can update/delete objects.
* Project maintainers and patch owners may create objects.
Signed-off-by: Andy Doan <andy.doan@linaro.org>
Reviewed-by: Stephen Finucane <stephen.finucane@intel.com>
| Andy Doan | 2016-06-27 |
| * | REST: Add base configuration hooks for a REST API•••This adds the ability to expose a REST API based on the Django REST
framework project. Since this project isn't packaged in most current
distributions, we ensure that its both installed and enabled before
trying to use it.
Signed-off-by: Andy Doan <andy.doan@linaro.org>
Inspired-by: Damien Lespiau <damien.lespiau@intel.com>
Reviewed-by: Stephen Finucane <stephen.finucane@intel.com>
| Andy Doan | 2016-06-27 |
| * | requirements: Loosen testing requirement versions•••There's not really any reason to pin the requirements for dependencies
only used in tests, so don't do it. Replace these specific versions
with broader, major-version checks.
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2016-03-15 |
| * | Add support for 'django-debug-toolbar'•••This tool is exceptionally helpful for debugging issues with Django:
install it as part of the 'dev' configuration. This only works on
Django > 1.6, due to a lack of support for older versions in the
upstream.
A note is included to help users avoid the issues seen when running
patchwork on a different machine.
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2016-03-15 |
| * | requirements: Remove psycopg2•••It would be good to provide the required packages for devs using both
MySQL and PostgreSQL. However, there does not appear to be any way to
specify an exclusive-or condition in pip requirements files and the
existing behavior of including dependencies for both RDBMSs means
system packages have to be installed for both, when you are likely
only using one. This is particularly problematic when you want to
set up a fast dev environment using something like Vagrant.
Settle on MySQL for now, until such a time as the consensus is to go
all-in with PostgreSQL (including docs, for example).
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2016-02-10 |
| * | requirements: Update version of dateutil used•••The version of dateutil currently used does not support Python3, so
instead use the latest version.
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2015-12-03 |
| * | Cleanup requirements•••* python-dateutil is only used in tests, so remove it from the
production requirements
* mysqlclient is prefered to MySQLdb, so use that [1]
* selenium does not have its version fixed, so resolve that
[1] https://docs.djangoproject.com/en/1.8/ref/databases/#mysql-db-api-drivers
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2015-11-21 |
| * | Rework configurable 'PW_TEST_DB_xxx' settings•••There are a number of environment variables that users can set to
configure different aspects of their testing environment. Rework these
like so:
* People use PostgreSQL, so make it as easy as possible for them to
develop and test against it. Add a 'PW_TEST_DB_TYPE' setting
* Attempt to use defaults for the username and password in settings
* Allow the user to configure the database name, if they so wish
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2015-11-21 |
| * | Add requirements-test.txt•••It's annoying that Django is not installed by default when setting up
a development environment. This is currently necessary because tox
uses these requirements files and it needs to test against multiple
versions of Django. Resolve this issue by adding a 'requirements-test'
file, thus allowing for Django-ful and Django-less scenarios.
This also allows us to delete 'requirements-base', which was a good
idea but alas contained too few options to really be viable. A little
duplication is better here.
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
| Stephen Finucane | 2015-11-21 |