%global _empty_manifest_terminate_build 0 Name: python-desktop-notifier Version: 3.5.3 Release: 1 Summary: Python library for cross-platform desktop notifications License: MIT URL: https://github.com/samschott/desktop-notifier Source0: https://mirrors.nju.edu.cn/pypi/web/packages/1d/c3/f78ac7f1a3a40572f0c97725ac50a5e2d0679f118b015d416186de87286c/desktop-notifier-3.5.3.tar.gz BuildArch: noarch Requires: python3-packaging Requires: python3-importlib-resources Requires: python3-rubicon-objc Requires: python3-dbus-next Requires: python3-winsdk Requires: python3-black Requires: python3-bump2version Requires: python3-flake8 Requires: python3-flake8-pyproject Requires: python3-mypy Requires: python3-pre-commit Requires: python3-pytest Requires: python3-pytest-cov Requires: python3-sphinx Requires: python3-sphinx-autoapi Requires: python3-sphinx-mdinclude Requires: python3-sphinx-rtd-theme %description [![PyPi Release](https://img.shields.io/pypi/v/desktop-notifier.svg)](https://pypi.org/project/desktop-notifier/) [![Pyversions](https://img.shields.io/pypi/pyversions/desktop-notifier.svg)](https://pypi.org/pypi/desktop-notifier/) [![Documentation Status](https://readthedocs.org/projects/desktop-notifier/badge/?version=latest)](https://desktop-notifier.readthedocs.io/en/latest/?badge=latest) # Desktop Notifier `desktop-notifier` is a Python library for cross-platform desktop notifications. Currently supported platforms are: * Linux via the dbus service org.freedesktop.Notifications * macOS and iOS via the Notification Center framework * [**exprimental**] Windows via the WinRT / Python bridge. ![gif](screenshots/macOS.gif) ## Features `desktop-notifier` aims to be a good citizen of the platforms which it supports. It therefore stays within the limits of the native platform APIs and does not try to work around limitations which are often deliberate UI choices. For example, on macOS and iOS, it is not possible to change the app icon which is shown on notifications. There are possible workarounds - that would likely be rejected by an App Store review. Where supported by the native platform APIs, `desktop-notifier` allows for: * Clickable notifications with callbacks on user interaction * Multiple action buttons * A single reply field (e.g., for chat notifications) * Notification sounds * Notification threads (grouping notifications by topic) * Limiting maximum number of notifications shown in the notification center An exhaustive list of features and their platform support is provided in the [documentation](https://desktop-notifier.readthedocs.io/en/latest/background/platform_support.html). Design choices by `desktop-notifier`: * Asyncio API: The main API consists of async methods and a running event loop is required to respond to user interactions with a notification. * Pure Python dependencies only, no extension modules (with the exception of of the Windows backend). ## Installation From PyPI: ``` pip3 install -U desktop-notifier ``` ## Usage The main API consists of asynchronous methods which need to be awaited. Basic usage only requires the user to specify a notification title and message. For instance: ```Python import asyncio from desktop_notifier import DesktopNotifier notifier = DesktopNotifier() async def main(): n = await notifier.send(title="Hello world!", message="Sent from Python") await asyncio.sleep(5) # wait a bit before clearing notification await notifier.clear(n) # removes the notification await notifier.clear_all() # removes all notifications for this app asyncio.run(main()) ``` For convenience, the is also a synchronous method ``send_sync()`` to send notifications which does not require a running asyncio loop: ```Python notifier.send_sync(title="Hello world!", message="Sent from Python") ``` By default, "Python" will be used as the app name for all notifications, but you can manually specify an app name and icon in the ``DesktopNotifier`` constructor. Advanced usage also allows setting different notification options such as urgency, buttons, callbacks, etc. The following code will generate the notification shown in the gif at the top of the page: ```Python import asyncio from desktop_notifier import DesktopNotifier, Urgency, Button, ReplyField notifier = DesktopNotifier() async def main(): await notifier.send( title="Julius Caesar", message="Et tu, Brute?", urgency=Urgency.Critical, buttons=[ Button( title="Mark as read", on_pressed=lambda: print("Marked as read")), ], reply_field=ReplyField( title="Reply", button_title="Send", on_replied=lambda text: print("Brutus replied:", text), ), on_clicked=lambda: print("Notification clicked"), on_dismissed=lambda: print("Notification dismissed"), sound=True, ) loop = asyncio.get_event_loop() loop.create_task(main()) loop.run_forever() ``` Note that some platforms may not support all options. For instance, some Linux desktop environments may not support notifications with buttons. macOS does not support manually setting the app icon or name. Instead, both are always determined by the application which uses the Library. This can be Python itself, when used interactively, or a frozen app bundle when packaged with PyInstaller or similar solutions. Please refer to the [Platform Support](https://desktop-notifier.readthedocs.io/en/latest/background/platform_support.html) chapter of the documentation for more information on limitations for certain platforms. Any options or configurations which are not supported by the platform will be silently ignored. Please refer to the documentation on [Read the Docs](https://desktop-notifier.readthedocs.io) for more information on platform support. ## Event loop integration Using the asynchronous API is highly recommended to prevent multiple milliseconds of blocking IO from DBus or Cocoa APIs. In addition, execution of callbacks requires a running event loop. On Linux, an asyncio event loop will be sufficient but macOS requires a running [CFRunLoop](https://developer.apple.com/documentation/corefoundation/cfrunloop-rht). You can use [rubicon-objc](https://github.com/beeware/rubicon-objc) to integrate a Core Foundation CFRunLoop with asyncio: ```Python import asyncio from rubicon.objc.eventloop import EventLoopPolicy # Install the event loop policy asyncio.set_event_loop_policy(EventLoopPolicy()) # Get an event loop, and run it! loop = asyncio.get_event_loop() loop.run_forever() ``` Desktop-notifier itself uses Rubicon Objective-C to interface with Cocoa APIs so you will not be adding a new dependency. A full example integrating with the CFRunLoop is given in [examples/eventloop.py](examples/eventloop.py). Please refer to the [Rubicon Objective-C docs](https://rubicon-objc.readthedocs.io/en/latest/how-to/async.html) for more information. Likewise, you can integrate the asyncio event loop with a Gtk main loop on Gnome using [gbulb](https://pypi.org/project/gbulb). This is not required for full functionality but may be convenient when developing a Gtk app. ## Notes on macOS On macOS 10.14 and higher, the implementation uses the `UNUserNotificationCenter` instead of the deprecated `NSUserNotificationCenter`. `UNUserNotificationCenter` only allows signed executables to send desktop notifications. This means that notifications will only work if the Python executable or bundled app has been signed. Note that the installer from [python.org](https://python.org) provides a properly signed Python framework but **homebrew does not** (manually signing the executable installed by homebrew _should_ work as well). If you freeze your code with PyInstaller or a similar packaging solution, you must sign the resulting app bundle for notifications to work. An ad-hoc signature will be sufficient but signing with an Apple developer certificate is recommended for distribution and may be required on future releases of macOS. ## Requirements * macOS 10.13 or higher * Linux desktop environment providing a dbus desktop notifications service ## Dependencies * [dbus-next](https://github.com/altdesktop/python-dbus-next) on Linux * [rubicon-objc](https://github.com/beeware/rubicon-objc) on macOS %package -n python3-desktop-notifier Summary: Python library for cross-platform desktop notifications Provides: python-desktop-notifier BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-desktop-notifier [![PyPi Release](https://img.shields.io/pypi/v/desktop-notifier.svg)](https://pypi.org/project/desktop-notifier/) [![Pyversions](https://img.shields.io/pypi/pyversions/desktop-notifier.svg)](https://pypi.org/pypi/desktop-notifier/) [![Documentation Status](https://readthedocs.org/projects/desktop-notifier/badge/?version=latest)](https://desktop-notifier.readthedocs.io/en/latest/?badge=latest) # Desktop Notifier `desktop-notifier` is a Python library for cross-platform desktop notifications. Currently supported platforms are: * Linux via the dbus service org.freedesktop.Notifications * macOS and iOS via the Notification Center framework * [**exprimental**] Windows via the WinRT / Python bridge. ![gif](screenshots/macOS.gif) ## Features `desktop-notifier` aims to be a good citizen of the platforms which it supports. It therefore stays within the limits of the native platform APIs and does not try to work around limitations which are often deliberate UI choices. For example, on macOS and iOS, it is not possible to change the app icon which is shown on notifications. There are possible workarounds - that would likely be rejected by an App Store review. Where supported by the native platform APIs, `desktop-notifier` allows for: * Clickable notifications with callbacks on user interaction * Multiple action buttons * A single reply field (e.g., for chat notifications) * Notification sounds * Notification threads (grouping notifications by topic) * Limiting maximum number of notifications shown in the notification center An exhaustive list of features and their platform support is provided in the [documentation](https://desktop-notifier.readthedocs.io/en/latest/background/platform_support.html). Design choices by `desktop-notifier`: * Asyncio API: The main API consists of async methods and a running event loop is required to respond to user interactions with a notification. * Pure Python dependencies only, no extension modules (with the exception of of the Windows backend). ## Installation From PyPI: ``` pip3 install -U desktop-notifier ``` ## Usage The main API consists of asynchronous methods which need to be awaited. Basic usage only requires the user to specify a notification title and message. For instance: ```Python import asyncio from desktop_notifier import DesktopNotifier notifier = DesktopNotifier() async def main(): n = await notifier.send(title="Hello world!", message="Sent from Python") await asyncio.sleep(5) # wait a bit before clearing notification await notifier.clear(n) # removes the notification await notifier.clear_all() # removes all notifications for this app asyncio.run(main()) ``` For convenience, the is also a synchronous method ``send_sync()`` to send notifications which does not require a running asyncio loop: ```Python notifier.send_sync(title="Hello world!", message="Sent from Python") ``` By default, "Python" will be used as the app name for all notifications, but you can manually specify an app name and icon in the ``DesktopNotifier`` constructor. Advanced usage also allows setting different notification options such as urgency, buttons, callbacks, etc. The following code will generate the notification shown in the gif at the top of the page: ```Python import asyncio from desktop_notifier import DesktopNotifier, Urgency, Button, ReplyField notifier = DesktopNotifier() async def main(): await notifier.send( title="Julius Caesar", message="Et tu, Brute?", urgency=Urgency.Critical, buttons=[ Button( title="Mark as read", on_pressed=lambda: print("Marked as read")), ], reply_field=ReplyField( title="Reply", button_title="Send", on_replied=lambda text: print("Brutus replied:", text), ), on_clicked=lambda: print("Notification clicked"), on_dismissed=lambda: print("Notification dismissed"), sound=True, ) loop = asyncio.get_event_loop() loop.create_task(main()) loop.run_forever() ``` Note that some platforms may not support all options. For instance, some Linux desktop environments may not support notifications with buttons. macOS does not support manually setting the app icon or name. Instead, both are always determined by the application which uses the Library. This can be Python itself, when used interactively, or a frozen app bundle when packaged with PyInstaller or similar solutions. Please refer to the [Platform Support](https://desktop-notifier.readthedocs.io/en/latest/background/platform_support.html) chapter of the documentation for more information on limitations for certain platforms. Any options or configurations which are not supported by the platform will be silently ignored. Please refer to the documentation on [Read the Docs](https://desktop-notifier.readthedocs.io) for more information on platform support. ## Event loop integration Using the asynchronous API is highly recommended to prevent multiple milliseconds of blocking IO from DBus or Cocoa APIs. In addition, execution of callbacks requires a running event loop. On Linux, an asyncio event loop will be sufficient but macOS requires a running [CFRunLoop](https://developer.apple.com/documentation/corefoundation/cfrunloop-rht). You can use [rubicon-objc](https://github.com/beeware/rubicon-objc) to integrate a Core Foundation CFRunLoop with asyncio: ```Python import asyncio from rubicon.objc.eventloop import EventLoopPolicy # Install the event loop policy asyncio.set_event_loop_policy(EventLoopPolicy()) # Get an event loop, and run it! loop = asyncio.get_event_loop() loop.run_forever() ``` Desktop-notifier itself uses Rubicon Objective-C to interface with Cocoa APIs so you will not be adding a new dependency. A full example integrating with the CFRunLoop is given in [examples/eventloop.py](examples/eventloop.py). Please refer to the [Rubicon Objective-C docs](https://rubicon-objc.readthedocs.io/en/latest/how-to/async.html) for more information. Likewise, you can integrate the asyncio event loop with a Gtk main loop on Gnome using [gbulb](https://pypi.org/project/gbulb). This is not required for full functionality but may be convenient when developing a Gtk app. ## Notes on macOS On macOS 10.14 and higher, the implementation uses the `UNUserNotificationCenter` instead of the deprecated `NSUserNotificationCenter`. `UNUserNotificationCenter` only allows signed executables to send desktop notifications. This means that notifications will only work if the Python executable or bundled app has been signed. Note that the installer from [python.org](https://python.org) provides a properly signed Python framework but **homebrew does not** (manually signing the executable installed by homebrew _should_ work as well). If you freeze your code with PyInstaller or a similar packaging solution, you must sign the resulting app bundle for notifications to work. An ad-hoc signature will be sufficient but signing with an Apple developer certificate is recommended for distribution and may be required on future releases of macOS. ## Requirements * macOS 10.13 or higher * Linux desktop environment providing a dbus desktop notifications service ## Dependencies * [dbus-next](https://github.com/altdesktop/python-dbus-next) on Linux * [rubicon-objc](https://github.com/beeware/rubicon-objc) on macOS %package help Summary: Development documents and examples for desktop-notifier Provides: python3-desktop-notifier-doc %description help [![PyPi Release](https://img.shields.io/pypi/v/desktop-notifier.svg)](https://pypi.org/project/desktop-notifier/) [![Pyversions](https://img.shields.io/pypi/pyversions/desktop-notifier.svg)](https://pypi.org/pypi/desktop-notifier/) [![Documentation Status](https://readthedocs.org/projects/desktop-notifier/badge/?version=latest)](https://desktop-notifier.readthedocs.io/en/latest/?badge=latest) # Desktop Notifier `desktop-notifier` is a Python library for cross-platform desktop notifications. Currently supported platforms are: * Linux via the dbus service org.freedesktop.Notifications * macOS and iOS via the Notification Center framework * [**exprimental**] Windows via the WinRT / Python bridge. ![gif](screenshots/macOS.gif) ## Features `desktop-notifier` aims to be a good citizen of the platforms which it supports. It therefore stays within the limits of the native platform APIs and does not try to work around limitations which are often deliberate UI choices. For example, on macOS and iOS, it is not possible to change the app icon which is shown on notifications. There are possible workarounds - that would likely be rejected by an App Store review. Where supported by the native platform APIs, `desktop-notifier` allows for: * Clickable notifications with callbacks on user interaction * Multiple action buttons * A single reply field (e.g., for chat notifications) * Notification sounds * Notification threads (grouping notifications by topic) * Limiting maximum number of notifications shown in the notification center An exhaustive list of features and their platform support is provided in the [documentation](https://desktop-notifier.readthedocs.io/en/latest/background/platform_support.html). Design choices by `desktop-notifier`: * Asyncio API: The main API consists of async methods and a running event loop is required to respond to user interactions with a notification. * Pure Python dependencies only, no extension modules (with the exception of of the Windows backend). ## Installation From PyPI: ``` pip3 install -U desktop-notifier ``` ## Usage The main API consists of asynchronous methods which need to be awaited. Basic usage only requires the user to specify a notification title and message. For instance: ```Python import asyncio from desktop_notifier import DesktopNotifier notifier = DesktopNotifier() async def main(): n = await notifier.send(title="Hello world!", message="Sent from Python") await asyncio.sleep(5) # wait a bit before clearing notification await notifier.clear(n) # removes the notification await notifier.clear_all() # removes all notifications for this app asyncio.run(main()) ``` For convenience, the is also a synchronous method ``send_sync()`` to send notifications which does not require a running asyncio loop: ```Python notifier.send_sync(title="Hello world!", message="Sent from Python") ``` By default, "Python" will be used as the app name for all notifications, but you can manually specify an app name and icon in the ``DesktopNotifier`` constructor. Advanced usage also allows setting different notification options such as urgency, buttons, callbacks, etc. The following code will generate the notification shown in the gif at the top of the page: ```Python import asyncio from desktop_notifier import DesktopNotifier, Urgency, Button, ReplyField notifier = DesktopNotifier() async def main(): await notifier.send( title="Julius Caesar", message="Et tu, Brute?", urgency=Urgency.Critical, buttons=[ Button( title="Mark as read", on_pressed=lambda: print("Marked as read")), ], reply_field=ReplyField( title="Reply", button_title="Send", on_replied=lambda text: print("Brutus replied:", text), ), on_clicked=lambda: print("Notification clicked"), on_dismissed=lambda: print("Notification dismissed"), sound=True, ) loop = asyncio.get_event_loop() loop.create_task(main()) loop.run_forever() ``` Note that some platforms may not support all options. For instance, some Linux desktop environments may not support notifications with buttons. macOS does not support manually setting the app icon or name. Instead, both are always determined by the application which uses the Library. This can be Python itself, when used interactively, or a frozen app bundle when packaged with PyInstaller or similar solutions. Please refer to the [Platform Support](https://desktop-notifier.readthedocs.io/en/latest/background/platform_support.html) chapter of the documentation for more information on limitations for certain platforms. Any options or configurations which are not supported by the platform will be silently ignored. Please refer to the documentation on [Read the Docs](https://desktop-notifier.readthedocs.io) for more information on platform support. ## Event loop integration Using the asynchronous API is highly recommended to prevent multiple milliseconds of blocking IO from DBus or Cocoa APIs. In addition, execution of callbacks requires a running event loop. On Linux, an asyncio event loop will be sufficient but macOS requires a running [CFRunLoop](https://developer.apple.com/documentation/corefoundation/cfrunloop-rht). You can use [rubicon-objc](https://github.com/beeware/rubicon-objc) to integrate a Core Foundation CFRunLoop with asyncio: ```Python import asyncio from rubicon.objc.eventloop import EventLoopPolicy # Install the event loop policy asyncio.set_event_loop_policy(EventLoopPolicy()) # Get an event loop, and run it! loop = asyncio.get_event_loop() loop.run_forever() ``` Desktop-notifier itself uses Rubicon Objective-C to interface with Cocoa APIs so you will not be adding a new dependency. A full example integrating with the CFRunLoop is given in [examples/eventloop.py](examples/eventloop.py). Please refer to the [Rubicon Objective-C docs](https://rubicon-objc.readthedocs.io/en/latest/how-to/async.html) for more information. Likewise, you can integrate the asyncio event loop with a Gtk main loop on Gnome using [gbulb](https://pypi.org/project/gbulb). This is not required for full functionality but may be convenient when developing a Gtk app. ## Notes on macOS On macOS 10.14 and higher, the implementation uses the `UNUserNotificationCenter` instead of the deprecated `NSUserNotificationCenter`. `UNUserNotificationCenter` only allows signed executables to send desktop notifications. This means that notifications will only work if the Python executable or bundled app has been signed. Note that the installer from [python.org](https://python.org) provides a properly signed Python framework but **homebrew does not** (manually signing the executable installed by homebrew _should_ work as well). If you freeze your code with PyInstaller or a similar packaging solution, you must sign the resulting app bundle for notifications to work. An ad-hoc signature will be sufficient but signing with an Apple developer certificate is recommended for distribution and may be required on future releases of macOS. ## Requirements * macOS 10.13 or higher * Linux desktop environment providing a dbus desktop notifications service ## Dependencies * [dbus-next](https://github.com/altdesktop/python-dbus-next) on Linux * [rubicon-objc](https://github.com/beeware/rubicon-objc) on macOS %prep %autosetup -n desktop-notifier-3.5.3 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-desktop-notifier -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Mon May 29 2023 Python_Bot - 3.5.3-1 - Package Spec generated