Tripoli

Latest version: v2.0.0

Safety actively analyzes 621239 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

2.0.0

to mirror the IIIF Presentation API version it supports. Tripoli v3 will only support Presentation
API v3.

1.2.1

++++++++++++++++++

**Improvements**

- Unit testing improvements and enhanced coverage
- Enhanced testing fixtures
- Travis-CI builds and Coveralls integration

**Bugfixes**

- Multiple sequences are now correctly validated.
- Canvas images are more thoroughly checked for their values.

NB: 1.2.2 is the same as 1.2.1, but incremented to try and address an issue with
distributing via PyPI.

1.2.0

++++++++++++++++++

**Improvements**

- Configuration arguments for the basic IIIFValidator can now be passed in via kwargs
on the `__init__` function. A validator can now be instantiated with all its settings
in one line.

**Bugfixes**

- Web interface now specifically mentions that tripoli is for validating IIIF Manifests.

1.1.4

++++++++++++++++++

**Bugfixes**

- Fixed an issue with the default values of REQUIRED_FIELDS (and other field sets)
being empty dicts instead of empty sets.

1.1.3

++++++++++++++++++

**Bugfixes**

- A warning message regarding uncertain HTML tags has been fixed to include the name
of the tag.

1.1.2

++++++++++++++++++

**Improvements**

- Added IIIF manifest test suite to tests, ensuring that each throws an error. A
number of new errors and warning have been added to this end.
- Faster hash algorithms for ValidatorLogEntries increasing overall performance.
- Added HISTORY.rst to track bugfixes and improvements.
- README.rst and HISTORY.rst will be automatically read into the setup.py long_description
field (idea taken from requests).

**Bugfixes**

- ``ViewingHint`` is now a common field which can be checked on any resource.
- ``startCanvas`` is now validated properly.
- ``Annotation`` no longer logs a warning if it has a ``context`` field.
- ``ImageResource`` now must have ``type`` 'dctypes:Image'.
- Presence of XML Comments or CDATA sections will cause an error to be logged.
- Fixed exception when ``IIIFValidator`` could not discern the ``type`` of a resource.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.