these badges work. The necessary Travis and Coverage config files have been
generated for you.
.. image:: https://travis-ci.org/josesalgado1024/ckanext-needupdate.svg?branch=master
:target: https://travis-ci.org/josesalgado1024/ckanext-needupdate
.. image:: https://coveralls.io/repos/josesalgado1024/ckanext-needupdate/badge.svg
:target: https://coveralls.io/r/josesalgado1024/ckanext-needupdate
.. image:: https://pypip.in/download/ckanext-needupdate/badge.svg
:target: https://pypi.python.org/pypi//ckanext-needupdate/
:alt: Downloads
.. image:: https://pypip.in/version/ckanext-needupdate/badge.svg
:target: https://pypi.python.org/pypi/ckanext-needupdate/
:alt: Latest Version
.. image:: https://pypip.in/py_versions/ckanext-needupdate/badge.svg
:target: https://pypi.python.org/pypi/ckanext-needupdate/
:alt: Supported Python versions
.. image:: https://pypip.in/status/ckanext-needupdate/badge.svg
:target: https://pypi.python.org/pypi/ckanext-needupdate/
:alt: Development Status
.. image:: https://pypip.in/license/ckanext-needupdate/badge.svg
:target: https://pypi.python.org/pypi/ckanext-needupdate/
:alt: License
=============
ckanext-needupdate
=============
.. Put a description of your extension here:
What does it do? What features does it have?
Consider including some screenshots or embedding a video!
------------
Requirements
------------
For example, you might want to mention here which versions of CKAN this
extension works with.
------------
Installation
------------
.. Add any additional install steps to the list below.
For example installing any non-Python dependencies or adding any required
config settings.
To install ckanext-needupdate:
1. Activate your CKAN virtual environment, for example::
. /usr/lib/ckan/default/bin/activate
2. Install the ckanext-needupdate Python package into your virtual environment::
pip install ckanext-needupdate
3. Add ``needupdate`` to the ``ckan.plugins`` setting in your CKAN
config file (by default the config file is located at
``/etc/ckan/default/production.ini``).
4. Restart CKAN. For example if you've deployed CKAN with Apache on Ubuntu::
sudo service apache2 reload
---------------
Config Settings
---------------
Document any optional config settings here. For example::
# The minimum number of hours to wait before re-checking a resource
# (optional, default: 24).
ckanext.needupdate.some_setting = some_default_value
------------------------
Development Installation
------------------------
To install ckanext-needupdate for development, activate your CKAN virtualenv and
do::
git clone https://github.com/josesalgado1024/ckanext-needupdate.git
cd ckanext-needupdate
python setup.py develop
pip install -r dev-requirements.txt
-----------------
Running the Tests
-----------------
To run the tests, do::
nosetests --nologcapture --with-pylons=test.ini
To run the tests and produce a coverage report, first make sure you have
coverage installed in your virtualenv (``pip install coverage``) then run::
nosetests --nologcapture --with-pylons=test.ini --with-coverage --cover-package=ckanext.needupdate --cover-inclusive --cover-erase --cover-tests
---------------------------------
Registering ckanext-needupdate on PyPI
---------------------------------
ckanext-needupdate should be availabe on PyPI as
https://pypi.python.org/pypi/ckanext-needupdate. If that link doesn't work, then
you can register the project on PyPI for the first time by following these
steps:
1. Create a source distribution of the project::
python setup.py sdist
2. Register the project::
python setup.py register
3. Upload the source distribution to PyPI::
python setup.py sdist upload
4. Tag the first release of the project on GitHub with the version number from
the ``setup.py`` file. For example if the version number in ``setup.py`` is
0.0.1 then do::
git tag 0.0.1
git push --tags
----------------------------------------
Releasing a New Version of ckanext-needupdate
----------------------------------------
ckanext-needupdate is availabe on PyPI as https://pypi.python.org/pypi/ckanext-needupdate.
To publish a new version to PyPI follow these steps:
1. Update the version number in the ``setup.py`` file.
See `PEP 440 <http://legacy.python.org/dev/peps/pep-0440/#public-version-identifiers>`_
for how to choose version numbers.
2. Create a source distribution of the new version::
python setup.py sdist
3. Upload the source distribution to PyPI::
python setup.py sdist upload
4. Tag the new release of the project on GitHub with the version number from
the ``setup.py`` file. For example if the version number in ``setup.py`` is
0.0.2 then do::
git tag 0.0.2
git push --tags
Metadata
Release files for ckanext-needupdate 0.0.1
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 |
|---|---|---|---|---|
| ckanext-needupdate-0.0.1.tar.gz | 7.7 kB | Without provenance | Details for ckanext-needupdate-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ckanext_needupdate-0.0.1-py2-none-any.whl | Python 2 | none | any | Details for ckanext_needupdate-0.0.1-py2-none-any.whl |
Total release size: 18.5 kB
Release files / ckanext-needupdate-0.0.1.tar.gz
| Download URL | ckanext-needupdate-0.0.1.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e54a23f262e21285ac84c6e761ab53e2573ecbdb15596abe8890fb4e5969daa
|
|
BLAKE2b-256 checksum How to use checksums |
30133c56d8be6fa5310cd0f112d921c7836afab3db03e3dda2ae55a16ad8fdde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / ckanext_needupdate-0.0.1-py2-none-any.whl
| Download URL | ckanext_needupdate-0.0.1-py2-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
38b195539e80556f71e5ad162529d3b6c84033fb62c6bbc04ab612668e8c58b4
|
|
BLAKE2b-256 checksum How to use checksums |
092b503fb8567b5c82000f6d666627a0b19e844cc31fcfb04f8721ee36af29bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ckanext-needupdate 0.0.1
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.