gbulb


Namegbulb JSON
Version 0.6.4 PyPI version JSON
download
home_pagehttps://github.com/beeware/gbulb
SummaryGLib event loop for tulip (PEP 3156)
upload_time2023-02-07 02:33:29
maintainerRussell Keith-Magee
docs_urlNone
authorRussell Keith-Magee
requires_python>=3.7
licenseApache 2.0
keywords gtk glib gnome asyncio tulip
VCS
bugtrack_url
requirements No requirements were recorded.
Travis-CI No Travis.
coveralls test coverage No coveralls.
            gbulb
=====

.. image:: https://img.shields.io/pypi/pyversions/gbulb.svg
   :target: https://pypi.python.org/pypi/gbulb
   :alt: Python Versions

.. image:: https://img.shields.io/pypi/v/gbulb.svg
   :target: https://pypi.python.org/pypi/gbulb
   :alt: PyPI Version

.. image:: https://img.shields.io/pypi/status/gbulb.svg
   :target: https://pypi.python.org/pypi/gbulb
   :alt: Maturity

.. image:: https://img.shields.io/pypi/l/gbulb.svg
   :target: https://github.com/beeware/gbulb/blob/main/LICENSE
   :alt: BSD License

.. image:: https://github.com/beeware/gbulb/workflows/CI/badge.svg?branch=main
   :target: https://github.com/beeware/gbulb/actions
   :alt: Build Status

.. image:: https://img.shields.io/discord/836455665257021440?label=Discord%20Chat&logo=discord&style=plastic
   :target: https://beeware.org/bee/chat/
   :alt: Discord server

Gbulb is a Python library that implements a `PEP 3156
<http://www.python.org/dev/peps/pep-3156/>`__ interface for the `GLib main event
loop <https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html>`__
under UNIX-like systems.

As much as possible, except where noted below, it mimics asyncio's interface.
If you notice any differences, please report them.

Requirements
------------

- python 3.7+
- pygobject
- glib
- gtk+3 (optional)

Usage
-----

GLib event loop
~~~~~~~~~~~~~~~

Example usage::

    import asyncio, gbulb
    gbulb.install()
    asyncio.get_event_loop().run_forever()

Gtk+ event loop *(suitable for GTK+ applications)*
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Example usage::

    import asyncio, gbulb
    gbulb.install(gtk=True)
    asyncio.get_event_loop().run_forever()

GApplication/GtkApplication event loop
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Example usage::

    import asyncio, gbulb
    gbulb.install(gtk=True)  # only necessary if you're using GtkApplication

    loop = asyncio.get_event_loop()
    loop.run_forever(application=my_gapplication_object)

Waiting on a signal asynchronously
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

See examples/wait_signal.py

Known issues
------------

- Windows is not supported, sorry. If you are interested in this, please help
  me get it working! I don't have Windows so I can't test it.

Divergences with PEP 3156
-------------------------

In GLib, the concept of event loop is split in two classes: GLib.MainContext
and GLib.MainLoop.

The event loop is mostly implemented by MainContext. MainLoop is just a wrapper
that implements the run() and quit() functions. MainLoop.run() atomically
acquires a MainContext and repeatedly calls MainContext.iteration() until
MainLoop.quit() is called.

A MainContext is not bound to a particular thread, however it cannot be used
by multiple threads concurrently. If the context is owned by another thread,
then MainLoop.run() will block until the context is released by the other
thread.

MainLoop.run() may be called recursively by the same thread (this is mainly
used for implementing modal dialogs in Gtk).

The issue: given a context, GLib provides no ways to know if there is an
existing event loop running for that context. It implies the following
divergences with PEP 3156:

- ``.run_forever()`` and ``.run_until_complete()`` are not guaranteed to run
  immediately. If the context is owned by another thread, then they will
  block until the context is released by the other thread.

- ``.stop()`` is relevant only when the currently running Glib.MainLoop object
  was created by this asyncio object (i.e. by calling ``.run_forever()`` or
  ``.run_until_complete()``). The event loop will quit only when it regains
  control of the context. This can happen in two cases:

  1. when multiple event loop are enclosed (by creating new ``MainLoop``
     objects and calling ``.run()`` recursively)
  2. when the event loop has not even yet started because it is still
     trying to acquire the context

It would be wiser not to use any recursion at all. ``GLibEventLoop`` will
actually prevent you from doing that (in accordance with PEP 3156), however
``GtkEventLoop`` will allow you to call ``run()`` recursively. You should also keep
in mind that enclosed loops may be started at any time by third-party code
calling GLib's primitives.

Community
---------

gbulb is part of the `BeeWare suite`_. You can talk to the community through:

* `@pybeeware on Twitter <https://twitter.com/pybeeware>`__

* `Discord <https://beeware.org/bee/chat/>`__

* The gbulb `Github Discussions forum <https://github.com/beeware/gbulb/discussions>`__

We foster a welcoming and respectful community as described in our
`BeeWare Community Code of Conduct`_.

Contributing
------------

If you experience problems with gbulb, `log them on GitHub`_. If you
want to contribute code, please `fork the code`_ and `submit a pull request`_.

.. _BeeWare suite: http://beeware.org
.. _BeeWare Community Code of Conduct: http://beeware.org/community/behavior/
.. _log them on Github: https://github.com/beeware/gbulb/issues
.. _fork the code: https://github.com/beeware/gbulb
.. _submit a pull request: https://github.com/beeware/gbulb/pulls

            

Raw data

            {
    "_id": null,
    "home_page": "https://github.com/beeware/gbulb",
    "name": "gbulb",
    "maintainer": "Russell Keith-Magee",
    "docs_url": null,
    "requires_python": ">=3.7",
    "maintainer_email": "russell@keith-magee.com",
    "keywords": "gtk,glib,gnome,asyncio,tulip",
    "author": "Russell Keith-Magee",
    "author_email": "russell@keith-magee.com",
    "download_url": "https://files.pythonhosted.org/packages/b1/cc/95e45476d07234172463d96bb6796b3fc486cbd121d869cc6ef2fe1c0e58/gbulb-0.6.4.tar.gz",
    "platform": "linux",
    "description": "gbulb\n=====\n\n.. image:: https://img.shields.io/pypi/pyversions/gbulb.svg\n   :target: https://pypi.python.org/pypi/gbulb\n   :alt: Python Versions\n\n.. image:: https://img.shields.io/pypi/v/gbulb.svg\n   :target: https://pypi.python.org/pypi/gbulb\n   :alt: PyPI Version\n\n.. image:: https://img.shields.io/pypi/status/gbulb.svg\n   :target: https://pypi.python.org/pypi/gbulb\n   :alt: Maturity\n\n.. image:: https://img.shields.io/pypi/l/gbulb.svg\n   :target: https://github.com/beeware/gbulb/blob/main/LICENSE\n   :alt: BSD License\n\n.. image:: https://github.com/beeware/gbulb/workflows/CI/badge.svg?branch=main\n   :target: https://github.com/beeware/gbulb/actions\n   :alt: Build Status\n\n.. image:: https://img.shields.io/discord/836455665257021440?label=Discord%20Chat&logo=discord&style=plastic\n   :target: https://beeware.org/bee/chat/\n   :alt: Discord server\n\nGbulb is a Python library that implements a `PEP 3156\n<http://www.python.org/dev/peps/pep-3156/>`__ interface for the `GLib main event\nloop <https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html>`__\nunder UNIX-like systems.\n\nAs much as possible, except where noted below, it mimics asyncio's interface.\nIf you notice any differences, please report them.\n\nRequirements\n------------\n\n- python 3.7+\n- pygobject\n- glib\n- gtk+3 (optional)\n\nUsage\n-----\n\nGLib event loop\n~~~~~~~~~~~~~~~\n\nExample usage::\n\n    import asyncio, gbulb\n    gbulb.install()\n    asyncio.get_event_loop().run_forever()\n\nGtk+ event loop *(suitable for GTK+ applications)*\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nExample usage::\n\n    import asyncio, gbulb\n    gbulb.install(gtk=True)\n    asyncio.get_event_loop().run_forever()\n\nGApplication/GtkApplication event loop\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nExample usage::\n\n    import asyncio, gbulb\n    gbulb.install(gtk=True)  # only necessary if you're using GtkApplication\n\n    loop = asyncio.get_event_loop()\n    loop.run_forever(application=my_gapplication_object)\n\nWaiting on a signal asynchronously\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nSee examples/wait_signal.py\n\nKnown issues\n------------\n\n- Windows is not supported, sorry. If you are interested in this, please help\n  me get it working! I don't have Windows so I can't test it.\n\nDivergences with PEP 3156\n-------------------------\n\nIn GLib, the concept of event loop is split in two classes: GLib.MainContext\nand GLib.MainLoop.\n\nThe event loop is mostly implemented by MainContext. MainLoop is just a wrapper\nthat implements the run() and quit() functions. MainLoop.run() atomically\nacquires a MainContext and repeatedly calls MainContext.iteration() until\nMainLoop.quit() is called.\n\nA MainContext is not bound to a particular thread, however it cannot be used\nby multiple threads concurrently. If the context is owned by another thread,\nthen MainLoop.run() will block until the context is released by the other\nthread.\n\nMainLoop.run() may be called recursively by the same thread (this is mainly\nused for implementing modal dialogs in Gtk).\n\nThe issue: given a context, GLib provides no ways to know if there is an\nexisting event loop running for that context. It implies the following\ndivergences with PEP 3156:\n\n- ``.run_forever()`` and ``.run_until_complete()`` are not guaranteed to run\n  immediately. If the context is owned by another thread, then they will\n  block until the context is released by the other thread.\n\n- ``.stop()`` is relevant only when the currently running Glib.MainLoop object\n  was created by this asyncio object (i.e. by calling ``.run_forever()`` or\n  ``.run_until_complete()``). The event loop will quit only when it regains\n  control of the context. This can happen in two cases:\n\n  1. when multiple event loop are enclosed (by creating new ``MainLoop``\n     objects and calling ``.run()`` recursively)\n  2. when the event loop has not even yet started because it is still\n     trying to acquire the context\n\nIt would be wiser not to use any recursion at all. ``GLibEventLoop`` will\nactually prevent you from doing that (in accordance with PEP 3156), however\n``GtkEventLoop`` will allow you to call ``run()`` recursively. You should also keep\nin mind that enclosed loops may be started at any time by third-party code\ncalling GLib's primitives.\n\nCommunity\n---------\n\ngbulb is part of the `BeeWare suite`_. You can talk to the community through:\n\n* `@pybeeware on Twitter <https://twitter.com/pybeeware>`__\n\n* `Discord <https://beeware.org/bee/chat/>`__\n\n* The gbulb `Github Discussions forum <https://github.com/beeware/gbulb/discussions>`__\n\nWe foster a welcoming and respectful community as described in our\n`BeeWare Community Code of Conduct`_.\n\nContributing\n------------\n\nIf you experience problems with gbulb, `log them on GitHub`_. If you\nwant to contribute code, please `fork the code`_ and `submit a pull request`_.\n\n.. _BeeWare suite: http://beeware.org\n.. _BeeWare Community Code of Conduct: http://beeware.org/community/behavior/\n.. _log them on Github: https://github.com/beeware/gbulb/issues\n.. _fork the code: https://github.com/beeware/gbulb\n.. _submit a pull request: https://github.com/beeware/gbulb/pulls\n",
    "bugtrack_url": null,
    "license": "Apache 2.0",
    "summary": "GLib event loop for tulip (PEP 3156)",
    "version": "0.6.4",
    "split_keywords": [
        "gtk",
        "glib",
        "gnome",
        "asyncio",
        "tulip"
    ],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "00706f880503df81dc6fca651146036297633ae9cd8e8424bc4f679bfc95ac7c",
                "md5": "14b3b9d0ddbf61694e8d8ea074bdd52d",
                "sha256": "31d64ede2e7aac8f871ce914f884b949e4891b1faa2ef45800db9eaa9c4b371b"
            },
            "downloads": -1,
            "filename": "gbulb-0.6.4-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "14b3b9d0ddbf61694e8d8ea074bdd52d",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": ">=3.7",
            "size": 17175,
            "upload_time": "2023-02-07T02:33:27",
            "upload_time_iso_8601": "2023-02-07T02:33:27.572317Z",
            "url": "https://files.pythonhosted.org/packages/00/70/6f880503df81dc6fca651146036297633ae9cd8e8424bc4f679bfc95ac7c/gbulb-0.6.4-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "b1cc95e45476d07234172463d96bb6796b3fc486cbd121d869cc6ef2fe1c0e58",
                "md5": "2823a0914036643284616cb796481645",
                "sha256": "4a6dddd9b8f958393e9ace60def7feacee6528136504bea3407e5ffe79f1a89f"
            },
            "downloads": -1,
            "filename": "gbulb-0.6.4.tar.gz",
            "has_sig": false,
            "md5_digest": "2823a0914036643284616cb796481645",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": ">=3.7",
            "size": 27662,
            "upload_time": "2023-02-07T02:33:29",
            "upload_time_iso_8601": "2023-02-07T02:33:29.272852Z",
            "url": "https://files.pythonhosted.org/packages/b1/cc/95e45476d07234172463d96bb6796b3fc486cbd121d869cc6ef2fe1c0e58/gbulb-0.6.4.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2023-02-07 02:33:29",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "github_user": "beeware",
    "github_project": "gbulb",
    "travis_ci": false,
    "coveralls": false,
    "github_actions": true,
    "tox": true,
    "lcname": "gbulb"
}
        
Elapsed time: 0.04834s