Source

py-pushnotify /

Filename Size Date modified Message
docs
examples
pushnotify
209 B
Fixed some typos in the docs.
456 B
Added tag 0.5.1 for changeset a0a017ea4267
240 B
Updated AUTHORS file.
1.0 KB
Added Sphinx docs in place of epydoc docs.
35.6 KB
Applied the GNU Free Documentation License to the docs.
350 B
Added Sphinx docs in place of epydoc docs.
287 B
Renamed LICENSE.rst to COPYING.rst.
263 B
Removed docs and upload_docs targets from Makefile.
2.0 KB
Fixed some typos in the docs.
145 B
Renamed all .txt files to .rst files (they are reStructuredText after all).
74 B
Added Sphinx docs in place of epydoc docs.
124 B
0.5.1
2.7 KB
Now requires requests>=2.0 for better compatibility moving forward. Closes #14.

pushnotify is a package for sending push notifications. It currently supports Android devices running Notify My Android and Pushover, and iOS devices running Pushover and Prowl.

See

for more details about these applications.

Development

All development for pushnotify takes place on bitbucket:

You can follow this project on Twitter:

To get started you can do the following:

$ hg clone https://bitbucket.org/jgoettsch/py-pushnotify/
$ cd py-pushnotify
$ pip install -r requirements_dev.txt
$ python setup.py develop

If you discover a bug, please create an issue ticket:

To run the test suite, you will have to create three modules:

  • pushnotify/tests/nmakeys.py:

    This file must contain two global variables: API_KEYS and DEVELOPER_KEY. API_KEYS is a list containing at least one valid API key as a string. DEVELOPER_KEY is a string containing a valid developer key.

  • pushnotify/tests/prowlkeys.py:

    This file must contain two global variables: API_KEYS and PROVIDER_KEY. API_KEYS is a list containing at least one valid API key as a string. PROVIDER_KEY is a string containing a valid provider key. REG_TOKEN is a valid registration token that has already been validated through the retrieve_token/retrieve_apikey process.

  • pushnotify/tests/pushoverkeys.py:

    This file must contain two global variables: TOKEN and USER. TOKEN is a string containing a valid API token. USER is a dictionary whose keys are strings containing valid user identifiers. The key values are lists containing strings, where each string contains a valid device identifier for the given API token. There must be one API token, and it must have one device identifier.