This release is a pre-release and may not be stable for production use.
Papyrus
Geospatial Extensions for the Pyramid web framework.
The Papyrus doc is hosted by Read the Docs.
The doc for the latest release is available at http://papyrus.rtfd.org (which is shortlink for http://readthedocs.org/docs/papyrus/en/latest/).
TODO
Changes
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)
0.5
JSONP support in the GeoJSON renderer (patch from @sbrunner)
New GeoJSON renderer implementation and API. The papyrus.renderers.geojson_renderer_factory function is replaced by the papyrus.renderers.GeoJSON class. The new usage is:
from papyrus.renderers import GeoJSON config.add_renderer('geojson', GeoJSON(jsonp_param_name='cb'))Pyramid 1.1 compliance
0.4
Improved GeoJSON renderer: deal with decimal.Decimal, datetime.date, and datetime.datetime values.
No longer use <= when defining requirements (only >= is used).
Correctly spell the names of requirements, using capital letters where needed.
0.3.1
Add MANIFEST.in file
0.3
Papyrus can now be used without pyramid_handlers
add a config method to add routes, pyramid.add_papyrus_routes
do not rely on environ['CONTENT_LENGTH'] to read the contents of requests, this doesn’t work with WebOb 1.0.4 and higher
minor change in the tests to use with_statement for Python 2.5
0.2
Add the papyrus.geo_inteface.GeoInterface mixin
Add the papyrus.add_papyrus_handler configurator directive
0.1
Initial version
5 maintainers
Metadata
5 maintainers
Release files for papyrus 0.10dev1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| papyrus-0.10dev1.tar.gz | 20.9 kB | Without provenance | Details |
Release files / papyrus-0.10dev1.tar.gz
| Download URL | papyrus-0.10dev1.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45afff79993e68b386bf5a715696ad97fbea57a1280e87378efa102a1519c158
|
|
BLAKE2b-256 checksum How to use checksums |
01ea2304c6ac48907b8eb7dfc1f962e494113a509012985d71d9d97e8276d3da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for papyrus 0.10dev1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
