Papyrus

Latest version: v2.5

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

Scan your dependencies

Page 2 of 3

0.10

~~~~

* `GeoInterface.__update__`` changed not to set model object attributes
without corresponding feature properties.
https://github.com/elemoine/papyrus/pull/21

0.9

~~~

* Make the XSD renderer work with mapped classes instead of ``Table`` objects.
This change breaks the compatibility. With 0.9 XSD views must return mapped
classes instead of ``Table`` objects. 13 elemoine
* Make it easier to overload the behavior of ``GeoInterface``. 15 elemoine
* Make the XSD renderer ignore foreign keys by default. 18 elemoine
* Give the user an extension point for adding elements to the ``xsd:sequence``
element. 18 elemoine
* New class-level property ``__add_properties__`` for classes implementing
GeoInterface. This is to be able to have ``GeoInterface`` consider properties
that are not column properties. 20 elemoine
* Documentation is now on Read the Docs, at http://papyrus.rtfd.org. elemoine

0.8.1

~~~~~

* XSD renderer now uses ``application/xml`` instead of ``text/xml``. twpayne
* XSD renderer now skips primary keys by default, and it now has an
``include_primary_keys`` option which can be set to ``True`` to change
the behavior. twpayne

0.8

~~~

* Add a ``XSD`` renderer for WFS DescribeFeatureType-like responses. Thanks
twpayne.

0.7

~~~

* Make ``feature`` argument optional in the GeoInterface constructor. This
change allow better integration with FormAlchemy for classes that implement
the GeoInterface.

0.6

~~~

* When passed a list or a tuple the GeoJSON renderer produces
a ``FeatureCollection`` by default. This behavior can be changed
with the ``collection_type`` argument to GeoJSON (patch
from tonio).
* Pyramid 1.2 compliance (a change in the tests)

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.