caronc/apprise v1.4.0 on GitHub

Details

Apprise API apprise:// attachment support added! 🚀 . (#873 and #877)
- That's right, if you have an Apprise API instance running, you can now post attachments to it and it will store them and relay them along to the endpoints that support it.
```
apprise -vv -b "Test" "apprise://localhost/config_id" \
   --attach=/path/to/something.jpeg
```
Support custom field mappings for JSON, FORM and XML Services (#842)
- Up until now you could leverage :value=key and add data into the payload of the custom supported Apprise endpoints (JSON, FORM and XML). But now you can change the mapping of the fixed ones that were always present. Hence :message=body would cause the payload to no longer put the message passed by apprise in the hard-coded message field. In this example, the payload would appear under a new tag called body.
  
  You can also set the values to be empty if you want to strip them from the payload. For example :version= would eliminate the version (previously hard-coded) payload element from the response.
Apprise CLI Global Configuration Added (#875)
-/etc/apprise among other paths added to the default search for configuration files when the apprise CLI tool is used.
Telegram tgram:// Topic ID Support Added (#854)
Better slack:// Channel Support (#856)
- Supports <!channel|desc> & <!channel>

Return target count from len(Service) calls #874
- This under-the-hood fix is just good for developers who wish to see how many targets (or endpoints) have been associated with one Apprise URL.
More async re-factoring improvements; the overhead of creating a thread-pool is now bypassed if it is detected that only one (1) notification is required to be sent. (#846)

Windows notifications: Correct WM_DESTROY return value (#863)
Custom Plugins (.py files hand-written) handling improvements. No longer is every file found interpreted. It must be a .py file (#853)

Apprise is available on PyPI through pip:

# Install Apprise v1.4.0 from PyPI
pip install apprise==1.4.0