We just need to mirror the change in the MySQL/default
docker-compose.yml file.
Fixes: b4f4c8554c11 ("docker: Require GID also")
Signed-off-by: Daniel Axtens
---
v2: an object lesson in why you should test before emailing
---
docker-compose-pg.yml | 2 ++
1 file changed, 2 insertions(+)
diff
We just need to mirror the change in the MySQL/default
docker-compose.yml file.
Fixes: b4f4c8554c11 ("docker: Require GID also")
Signed-off-by: Daniel Axtens
---
docker-compose-pg.yml | 1 +
1 file changed, 1 insertion(+)
diff --git docker-compose-pg.yml docker-compose-pg.yml
index 7bb579c3279f
Applied to master, thanks.
Andrew Donnellan writes:
> Enable Python 3.8 in our tests and list it as a supported version.
>
> Signed-off-by: Andrew Donnellan
>
> ---
>
> v1->v2:
> - Add release note that I forgot to git add
> ---
> README.rst | 2
Django 3.0 switches to using Python 3's built-in HTML escaper, which
prefers to escape entities using hex rather than decimal.
Some of our tests check rendered HTML output against pre-escaped strings,
and fail because ''' is now '''.
Fix this by using the escape function so we get consistent esca
Now that we've dropped Python 2, we can get ready for Django 3.0, which is
still in beta.
Add Django 3.0b1 as a tox environment. Add a release note for Django 3.0
support, as it will be released by the time Patchwork 3.0 is out.
Closes: #311 ("Django 3.0 support")
Signed-off-by: Andrew Donnellan
Currently Travis calls `tox -e coverage` unconditionally. However,
the environment has py27 basepython, so all the runs only generate
py27 coverage!
Rather than try to untangle that, just run the coverage when run
in a py27 travis environment. This makes things faster for no
loss of coverage. It m
Enable Python 3.8 in our tests and list it as a supported version.
Signed-off-by: Andrew Donnellan
---
v1->v2:
- Add release note that I forgot to git add
---
README.rst | 2 +-
releasenotes/notes/python-3-8-support-59150fb6391f9b73.yaml | 5 +++
Enable Python 3.8 in our tests and list it as a supported version.
Signed-off-by: Andrew Donnellan
---
README.rst | 2 +-
tools/docker/Dockerfile | 3 ++-
tox.ini | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/README.rst b/README.rst
index 01d
Konstantin Ryabitsev writes:
> On Wed, Oct 09, 2019 at 05:35:03PM +1100, Daniel Axtens wrote:
>> Hi sfr, jk, Konstantin and any other admins lurking,
>>
>> I'm in the process of reworking the patchwork db schema to avoid one of
>> our very big and very annoying (and slow) JOINs.
>>
>> While I'm
Andrew Donnellan writes:
> Now that we've dropped Python 2, we can get ready for Django 3.0.
>
> Add Django 3.0b1 as a tox environment.
>
> Closes: #311 ("Django 3.0 support")
> Signed-off-by: Andrew Donnellan
>
> ---
>
> Not adding upper bounds on the version numbers until 3.0 actually drops.
>
landsape.io is down and seems to have been for some time.
The issue tracker [1] doesn't seem to have anything since April.
Pull out the broken badge. If landscape.io returns we can add it
back later.
[1]
https://github.com/landscapeio/landscape-issues/issues?q=is%3Aopen+is%3Aissue
Signed-off-by
In e017f69376da ("travis: run pep8/flake8 tests"), codecov
was removed from the install step, on the basis that tox-travis
would pull it in automatically.
This, it turns out, isn't entirely true: it is pulled in to the
tox environment, but the data is actually sent in an after_success
step. That i
On Wed, Oct 09, 2019 at 05:35:03PM +1100, Daniel Axtens wrote:
> Hi sfr, jk, Konstantin and any other admins lurking,
>
> I'm in the process of reworking the patchwork db schema to avoid one of
> our very big and very annoying (and slow) JOINs.
>
> While I'm at it, it occurred to me that for both
On Thu, Oct 24, 2019 at 01:33:42AM +1100, Daniel Axtens wrote:
> This is a feature that the XML-RPC API has, and which is used in
> the wild [1], so support it in the REST API.
Nice! Thank you for this.
> I tried to version the new filter field, but it's not at all clear
> how to do this with dja
This is a feature that the XML-RPC API has, and which is used in
the wild [1], so support it in the REST API.
I tried to version the new filter field, but it's not at all clear
how to do this with django-filters. The best way I could find
requires manually manipulating request.GET, which seems to
15 matches
Mail list logo