aboutsummaryrefslogtreecommitdiff
path: root/requirements-prod.txt
Commit message (Collapse)AuthorAge
* requirements: Use compatible MINOR releasesStephen Finucane2019-09-10
| | | | | | | | '~= 2.2' will match '2.2.N', '2.3.N', etc. but not '3.0.N'. What we want in most cases is to match '2.2.N' only. Ensure this is the case. Signed-off-by: Stephen Finucane <stephen@that.guru> Fixes: c90473ea ("requirements: Switch to compatible releases")
* requirements: Switch to compatible releasesStephen Finucane2019-09-10
| | | | | | | | | | | | | | | | In commit ab0c443691, we switched from using commit ranges to fixed ranges. This was a good idea in so far as it ensures we're providing an application with dependencies that are guaranteed to work. However, Patchwork as a project isn't active enough to warrant the continued busy work effort necessary to keep bumping these versions and it's probably about time to abandon the experiment. However, rather than switching back to version ranges, use the compatible releases feature introduced in PEP 440 [1]. This gives us most of the benefits of ranges but with a nicer syntax. [1] https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Stephen Finucane <stephen@that.guru>
* Add support for djangorestframework 3.10Stephen Finucane2019-09-09
| | | | | | | This is necessary for proper Django 2.2 support. We retain support for older versions since 3.10 is Python 3-only. Signed-off-by: Stephen Finucane <stephen@that.guru>
* Update psycopg2-binary from 2.8.2 to 2.8.3pyup-bot2019-09-09
|
* Update django-filter from 2.1.0 to 2.2.0pyup-bot2019-09-08
|
* Update django from 1.11.22 to 1.11.24Stephen Finucane2019-09-08
| | | | Signed-off-by: Stephen Finucane <stephen@that.guru>
* Drop support for Python 3.4, add Python 3.7Stephen Finucane2019-09-08
| | | | | | | It's no longer supported upstream and the *second* last Ubuntu LTS release provides something newer. Time to move on. Signed-off-by: Stephen Finucane <stephen@that.guru>
* Update django from 2.2.3 to 2.2.5pyup-bot2019-09-03
|
* Update django from 2.2.2 to 2.2.3pyup-bot2019-07-06
|
* Update django from 1.11.21 to 1.11.22Stephen Finucane2019-07-06
|
* Update django from 1.11.20 to 1.11.21Stephen Finucane2019-06-17
|
* Add support for Django 2.2Stephen Finucane2019-06-05
| | | | Signed-off-by: Stephen Finucane <stephen@that.guru>
* Update psycopg2-binary from 2.8.1 to 2.8.2pyup-bot2019-04-17
|
* Update psycopg2-binary from 2.7.7 to 2.8.1pyup-bot2019-04-07
|
* Update sqlparse from 0.2.4 to 0.3.0pyup-bot2019-03-12
|
* Update django from 1.11.18 to 1.11.20Stephen Finucane2019-03-07
|
* Update djangorestframework from 3.9.1 to 3.9.2pyup-bot2019-03-03
|
* Update django from 2.1.5 to 2.1.7pyup-bot2019-02-12
|
* Update psycopg2-binary from 2.7.6.1 to 2.7.7pyup-bot2019-01-28
|
* Update django (Py2) from 1.11.15 to 1.11.18Stephen Finucane2019-01-28
| | | | Signed-off-by: Stephen Finucane <stephen@that.guru>
* Update django-filter from 2.0.0 to 2.1.0pyup-bot2019-01-22
|
* Update djangorestframework from 3.9.0 to 3.9.1pyup-bot2019-01-17
|
* Update django from 2.1.4 to 2.1.5pyup-bot2019-01-05
|
* Update psycopg2-binary from 2.7.6 to 2.7.6.1pyup-bot2018-12-22
|
* Update django from 2.1.3 to 2.1.4pyup-bot2018-12-22
|
* Update psycopg2-binary from 2.7.5 to 2.7.6pyup-bot2018-11-09
|
* Update django from 2.1.2 to 2.1.3pyup-bot2018-11-02
|
* Add support for Django REST Framework 3.9Stephen Finucane2018-10-18
| | | | | | | As with 3.7 and 3.8, there are no breaking changes we need to be concerned with here. Signed-off-by: Stephen Finucane <stephen@that.guru>
* Add support for Django 2.1Stephen Finucane2018-10-06
| | | | | | For once, this just works. Yay! Signed-off-by: Stephen Finucane <stephen@that.guru>
* Add support for django-filter 2.0Stephen Finucane2018-10-06
| | | | | | | | This is necessary for Django 2.1 support. We retain support for django-filter 1.0 and 1.1 as 2.0 is Python 3-only. Thankfully there is essentially zero cost in doing so for now. Signed-off-by: Stephen Finucane <stephen@that.guru>
* requirements: Start using fixed versionsStephen Finucane2018-09-22
| | | | | | | | | | | | | | Given that 'tox' doesn't actually read any of these, there's no reason to use ranges of requirements. Instead, use the latest and greatest for live instances and rely on tox to validate behavior with older versions. The selenium dependency, which is no longer required since commit bab2895f, is removed. The psycopg2 dependency is updated to use psycopg2-binary, as this avoids the need for the libpg library and removes a deprecation warning. Signed-off-by: Stephen Finucane <stephen@that.guru> Signed-off-by: Daniel Axtens <dja@axtens.net>
* Add support for Django 2.0Stephen Finucane2018-08-26
| | | | | | | | | | | | | | | | | | | | | | | | Nothing too complicated here except for the addition of a new compat wrapper, which will be removed again shortly. According to the Django release notes, Django should function with Python 3.4. However, it was not possible to get this functioning due to the below error: Traceback (most recent call last): File ".../patchwork/manage.py", line 11, in <module> ... File ".../django/db/models/fields/related.py", line 313, in contribute_to_class 'app_label': cls._meta.app_label.lower(), TypeError: unsupported operand type(s) for %: 'bytes' and 'dict' This does not appear to be an issue with Patchwork but the exact root cause has not been identified. As a result, only Python 3.5 and 3.6 are marked as supported for this Django version. As this is the first Python 3-only dependency we have, we need to start making use of the 'python_version' environment marker. Signed-off-by: Stephen Finucane <stephen@that.guru> Signed-off-by: Daniel Axtens <dja@axtens.net>
* Remove support for Django 1.8, 1.9, 1.10Stephen Finucane2018-08-26
| | | | | | | | | | | | | | These are now all EOL and Debian Testing supports Django 1.11 (LTS). We can and should drop them. This change does not remove the many compat wrappers. These will be removed separately (there are a lot of them). This leaves 1.11 as the only supported version. This will be remedied shortly with the inclusion of Django 2.0 support. Signed-off-by: Stephen Finucane <stephen@that.guru> Signed-off-by: Daniel Axtens <dja@axtens.net>
* Add support for django-filter 1.1Stephen Finucane2018-08-26
| | | | | | | There's one warning to handle here. Signed-off-by: Stephen Finucane <stephen@that.guru> Signed-off-by: Daniel Axtens <dja@axtens.net>
* Add support for Django REST Framework 3.7, 3.8Stephen Finucane2018-08-26
| | | | | | | | No breaking changes that concern us here. Signed-off-by: Stephen Finucane <stephen@that.guru> Reviewed-by: Daniel Axtens <dja@axtens.net> Signed-off-by: Daniel Axtens <dja@axtens.net>
* Update sqlparse from 0.2.3 to 0.2.4pyup-bot2018-04-25
|
* requirements: Enable Django 1.11Stephen Finucane2017-12-03
| | | | | | | This is now completely supported. Let's enable it. Signed-off-by: Stephen Finucane <stephen@that.guru> Tested-by: Daniel Axtens <dja@axtens.net>
* Update djangorestframework from 3.5 to 3.6pyup-bot2017-04-14
|
* Update psycopg2 from 2.7 to 2.7.xpyup-bot2017-03-13
|
* Update sqlparse from 0.2.2 to 0.2.3pyup-bot2017-03-04
|
* Pin psycopg2 to latest version 2.7pyup-bot2017-03-01
|
* REST: Integrate django-filter supportStephen Finucane2017-01-22
| | | | | | | | 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>
* Pin sqlparse to latest version 0.2.2pyup-bot2017-01-04
|
* REST: Use generic views instead of ViewSetsStephen Finucane2016-12-23
| | | | | | | | | | | | | | | | | | | | ViewSet provide an easy way to define an API, but they don't offer much flexibility. To get them to work as expected, a lot of hacks were required. Generic views provide a more verbose, but ultimately easier to understand, version. Using generic views lets us remove the dependency of drf-nested-routers, bringing us back down to two main dependencies. It also lets us remove the AuthenticatedReadOnly permission class, as the DRF provides a similar permission class that can be used with generic views. The main user facing change is that invalid methods, such as POST on an endpoint that doesn't allow object creation, will now return a HTTP 405 (Method Not Allowed) error code rather than the HTTP 403 (Forbidden) error code previously returned. This is the semantically correct option and should have been used all along. Signed-off-by: Stephen Finucane <stephen@that.guru> Reviewed-by: Daniel Axtens <dja@axtens.net>
* requirements: Test older versions of DRFStephen Finucane2016-11-18
| | | | | | | | 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>
* requirements: Loosen requirements for RDBMS libsStephen Finucane2016-11-18
| | | | Signed-off-by: Stephen Finucane <stephen@that.guru>
* requirements: Add support for Django 1.10Stephen Finucane2016-10-10
| | | | | | | | All issues around 1.10 support have been resolved. Add tox targets and extend the range of supported versions to include this release. Signed-off-by: Stephen Finucane <stephen@that.guru> Reviewed-by: Daniel Axtens <dja@axtens.net>
* Add sqlparse to production requirementsDaniel Axtens2016-09-25
| | | | | | | | | It's required for migration #10 (w/ RunSQL), per upstream docs: https://docs.djangoproject.com/en/1.8/ref/migration-operations/#runsql Signed-off-by: Daniel Axtens <dja@axtens.net> Reviewed-by: Stephen Finucane <stephenfinucane@hotmail.com>
* requirements: Use any supported Django versionStephen Finucane2016-03-25
| | | | | | | | | | Patchwork now supports Django 1.9. It continues to support Django 1.8, 1.7 and 1.6, though the latter two are not supported upstream and are therefore not recommended. Update development requirements to reflect this. Signed-off-by: Stephen Finucane <stephen.finucane@intel.com> Reviewed-by: Andy Doan <andy.doan@linaro.org>
* requirements: Use PostgreSQL in productionStephen Finucane2016-02-08
| | | | | | | | The example "production" settings expect a PostgreSQL database backend, yet the requirements file for the same scenario install MySQL dependencies. Correct this mismatch. Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
generated by cgit v1.2.3 (git 2.45.0) at 2024-11-22 07:58:23 +0000