patchwork:pyup-pin-django-filter-2.3.0

Last commit made on 2020-06-05
Get this branch:
git clone -b pyup-pin-django-filter-2.3.0 https://git.launchpad.net/patchwork

Branch merges

Branch information

Name:
pyup-pin-django-filter-2.3.0
Repository:
lp:patchwork

Recent commits

5c3dde3... by pyup-bot <email address hidden> on 2020-06-05

Pin django-filter to latest version 2.3.0

2ea7f84... by pyup-bot <email address hidden> on 2020-06-05

Pin django-filter to latest version 2.3.0

7e5d2e6... by Jan Remmet <email address hidden> on 2020-05-25

admin: fix series query

remove typo from search_fields.

Signed-off-by: Jan Remmet <email address hidden>
Signed-off-by: Stephen Finucane <email address hidden>

31a6525... by Stephen Finucane <email address hidden> on 2020-05-08

docs: Bump sphinxcontrib-openapi to 0.7.0

This picks up an important fix [1] we want for our docs build.

[1] https://github.com/sphinx-contrib/openapi/pull/87

Signed-off-by: Stephen Finucane <email address hidden>

6841ba3... by Stephen Finucane <email address hidden> on 2020-05-01

Revert "tox: Add default Django version"

This reverts commit 029aff107ea9950418f9ad3cf44c3ba1ca3ea3ee. It appears
this isn't supported by tox either :(

Signed-off-by: Stephen Finucane <email address hidden>

029aff1... by Stephen Finucane <email address hidden> on 2020-04-30

tox: Add default Django version

I occasionally forget myself and run e.g. 'tox -e pyNN' when I want to
sanity check something instead of 'tox -e pyNN-djangoMM'. Add fallback
Django versions so that this doesn't crash and burn. It's less succict
than it could be since tox doesn't seem to support '!django{22,30}'
(yet!).

Signed-off-by: Stephen Finucane <email address hidden>

e5c5f8f... by Stephen Finucane <email address hidden> on 2020-04-26

migrations: Moved squashed migration

This should have been in the 'patchwork/migrations' directory, not
'migrations.

Signed-off-by: Stephen Finucane <email address hidden>
Fixes: 9bb5caec ("migrations: Squash 0001 to 0040")

c7d6e18... by Stephen Finucane <email address hidden> on 2020-04-26

migrations: Resolve issues with other DB backends for 0042, 0043

0042 was using MySQL-specific SQL to delete entries in the
'patchwork_comment' table that were associated with entries in the
'patchwork_coverletter' table, while 0043 only considered MySQL and
PostgrSQL when attempting to copy fields from 'patchwork_patch' to
'patchwork_submission'. Both issues are resolved.

Signed-off-by: Stephen Finucane <email address hidden>

10b6162... by Stephen Finucane <email address hidden> on 2020-04-26

docker: Ignore postgres data file

Signed-off-by: Stephen Finucane <email address hidden>

9bb5cae... by Stephen Finucane <email address hidden> on 2020-04-10

migrations: Squash 0001 to 0040

Now that we're moving a new major version, we can squash the migrations
we have to date. This coexists alongside the old migrations, which we
can remove and replace entirely when we release 4.0, per the advice of
the 'squashmigrations' tool.

  You should commit this migration but leave the old ones in place; the
  new migration will be used for new installs. Once you are sure all
  instances of the codebase have applied the migrations you squashed,
  you can delete them.

The 'squashmigrations' tool can't parse the output of 'RunPython' blocks
so the output of the tool was less optimized than it could be. As a
result, we've manually modified this change to remove the 'RunPython'
block and unnecessary 'AlterField' entries. This was done by removing
all migrations and generating a new "initial" migration, which was then
modified to mark all strings as byte strings (as they were when we were
using Python 2 to generate these migrations) so that 0041 would apply
cleanly.

The main benefit of this change is that it significantly reduces the
startup time for unit tests. Executed on my host, the run time for a
single test goes from ~ 22 seconds to ~ 14 seconds. This is obviously
reduced for additional tests.

Signed-off-by: Stephen Finucane <email address hidden>