| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 3c6500c2292869f94667520f16c8d6c6f1d2c530
Author: Barry Warsaw <barry@python.org>
Date: Tue Aug 29 22:51:18 2017 -0400
Close #383
Messages with badly encoded ``Subject`` headers no longer crash the message
moderation REST API.
commit f6040ec139bcccd48cfa9acc734cd528a8ede35c
Author: Aurélien Bompard <aurelien@bompard.org>
Date: Thu Jul 27 00:52:05 2017 +0200
Fix #383: email encoding errors can crash the REST API
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
If a message can't be parsed by Python due to bad structure, don't raise an
error but return a generic 'this message is defective' string instead.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
We now have an IAPI interface which defines methods to convert to/from
UUIDs to their REST representations, and to calculate the API-homed full
URL path to a resource. Add implementations API30 and API31 to handle
the two different implementations so far. This also simplifies the
various path_to() calls.
Also: Add support for diff_cover to tox.ini to check that all
differences against the master branch have full test coverage.
|
| |
|
|
|
|
| |
Rather than sprinkle API version string tests all over the place, create
an IAPI interface which encapsulates the differences between API 3.0 and
3.1, and arrange for this to be used to convert to and from UUIDs.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
use len() and slicing on SQLAlchemy query results. We also don't need to
list()-ify the results in the tests. This isn't perfect, but at least it
doesn't introduce yet another layer violation.
|
| | |
|
| | |
|
| |
|
|
| |
Add some assertions to prove this is always the case.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
3.0 except that UUIDs are represented as hex strings instead of 128-bit
integers, since the latter are not compatible with all versions of
JavaScript.
|
| |
|