This release is a pre-release and may not be stable for production use.
in your `Django <https://www.djangoproject.com>`_ projects.
This is just packaging work for the great opengeo suite client sdk.
The releases will be done based on the suite releases or a git hash will be appended to the package name before publishing to pypi in the following way:
3.0.1.devXXXXX where XXXXX is the git hash and the url to the source code can be constructed as follows:
https://github.com/opengeo/suite/tree/XXXXX
=======
INSTALL
=======
::
pip install django-geoexplorer
=====
USAGE
=====
* Add ``geoexplorer`` to your ``INSTALLED_APPS``
=======
AUTHORS
=======
* Ariel Núñez <http://ingenieroariel.com>
=======
LICENSE
=======
* Lesser GNU Public License
* OpenGeo Suite License - GPL
=========
CHANGELOG
=========
3.0.1.dev84743c7 (2013-01-10)
==================
* Initial working version, forked django-leaflet and made the appropriate changes.
5 maintainers
Metadata
5 maintainers
Release files for django-geoexplorer 3.0.1.dev57bb2fdd
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 | Actions |
|---|---|---|---|---|
| django-geoexplorer-3.0.1.dev57bb2fdd.tar.gz | 913.3 kB | Without provenance | Details for django-geoexplorer-3.0.1.dev57bb2fdd.tar.gz |
Release files / django-geoexplorer-3.0.1.dev57bb2fdd.tar.gz
| Download URL | django-geoexplorer-3.0.1.dev57bb2fdd.tar.gz |
|---|---|
| Size | 913.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e54de19ad539484a592f61e7bd3531f9528ff3f8455bf2d7d9873945e8f26ad9
|
|
BLAKE2b-256 checksum How to use checksums |
6e5208e153c21bd39c1f6d042580548db70278e34c156d540a0b938f15ce098b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-geoexplorer 3.0.1.dev57bb2fdd
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
