A Discord/Xenforo bot!

Overview

telathbot

CI Coverage Status

A Discord/Xenforo bot!

Pre-requisites

Local development

  1. Create a .env file from .env-local that contains relevant variables. (Mainly this will be the Discord webhook for testign.)
  2. Run poetry install to create virtualenv and install dependencies.
  3. Run make local-dev-up to start mock Xenforo database and MongoDB. This can be used when testing.
  4. Run make test to get fresh environments, run linters and tests.
Comments
  • Update dependency discord-webhook to ^0.15.0

    Update dependency discord-webhook to ^0.15.0

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | discord-webhook | ^0.14.0 -> ^0.15.0 | age | adoption | passing | confidence |


    Release Notes

    lovvskillz/python-discord-webhook

    v0.15.0

    Compare Source

    Features
    • enable rate_limit_retry in webhook edit() function
    • add optional kwargs to edit function to specify fields that will be added or override existing fields in the webhook edit request. e.g. attachments

    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 3
  • Update dependency pytest-asyncio to ^0.18.0

    Update dependency pytest-asyncio to ^0.18.0

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pytest-asyncio | ^0.17.1 -> ^0.18.0 | age | adoption | passing | confidence |


    Release Notes

    pytest-dev/pytest-asyncio

    v0.18.2

    Compare Source

    =================

    • Fix asyncio auto mode not marking static methods. #&#8203;295 <https://github.com/pytest-dev/pytest-asyncio/issues/295>_
    • Fix a compatibility issue with Hypothesis 6.39.0. #&#8203;302 <https://github.com/pytest-dev/pytest-asyncio/issues/302>_

    v0.18.1

    Compare Source


    title: 'pytest-asyncio: pytest support for asyncio'

    image

    image

    image

    Supported Python versions

    image

    pytest-asyncio is an Apache2 licensed library, written in Python, for testing asyncio code with pytest.

    asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier.

    @&#8203;pytest.mark.asyncio
    async def test_some_asyncio_code():
        res = await library.do_something()
        assert b"expected result" == res
    

    pytest-asyncio has been strongly influenced by pytest-tornado.

    Features

    • fixtures for creating and injecting versions of the asyncio event loop
    • fixtures for injecting unused tcp/udp ports
    • pytest markers for treating tests as asyncio coroutines
    • easy testing with non-default event loops
    • support for [async def]{.title-ref} fixtures and async generator fixtures
    • support auto mode to handle all async fixtures and tests automatically by asyncio; provide strict mode if a test suite should work with different async frameworks simultaneously, e.g. asyncio and trio.

    Installation

    To install pytest-asyncio, simply:

    $ pip install pytest-asyncio
    

    This is enough for pytest to pick up pytest-asyncio.

    Modes

    Starting from pytest-asyncio>=0.17, three modes are provided: auto, strict and legacy (default).

    The mode can be set by asyncio_mode configuration option in configuration file:

    ### pytest.ini
    [pytest]
    asyncio_mode = auto
    

    The value can be overridden by command-line option for pytest invocation:

    $ pytest tests --asyncio-mode=strict
    

    Auto mode

    When the mode is auto, all discovered async tests are considered asyncio-driven even if they have no @pytest.mark.asyncio marker.

    All async fixtures are considered asyncio-driven as well, even if they are decorated with a regular @pytest.fixture decorator instead of dedicated @pytest_asyncio.fixture counterpart.

    asyncio-driven means that tests and fixtures are executed by pytest-asyncio plugin.

    This mode requires the simplest tests and fixtures configuration and is recommended for default usage unless the same project and its test suite should execute tests from different async frameworks, e.g. asyncio and trio. In this case, auto-handling can break tests designed for other framework; please use strict mode instead.

    Strict mode

    Strict mode enforces @pytest.mark.asyncio and @pytest_asyncio.fixture usage. Without these markers, tests and fixtures are not considered as asyncio-driven, other pytest plugin can handle them.

    Please use this mode if multiple async frameworks should be combined in the same test suite.

    Legacy mode

    This mode follows rules used by pytest-asyncio<0.17: tests are not auto-marked but fixtures are.

    This mode is used by default for the sake of backward compatibility, deprecation warnings are emitted with suggestion to either switching to auto mode or using strict mode with @pytest_asyncio.fixture decorators.

    In future, the default will be changed.

    Fixtures

    event_loop

    Creates and injects a new instance of the default asyncio event loop. By default, the loop will be closed at the end of the test (i.e. the default fixture scope is function).

    Note that just using the event_loop fixture won't make your test function a coroutine. You'll need to interact with the event loop directly, using methods like event_loop.run_until_complete. See the pytest.mark.asyncio marker for treating test functions like coroutines.

    Simply using this fixture will not set the generated event loop as the default asyncio event loop, or change the asyncio event loop policy in any way. Use pytest.mark.asyncio for this purpose.

    def test_http_client(event_loop):
        url = "http://httpbin.org/get"
        resp = event_loop.run_until_complete(http_client(url))
        assert b"HTTP/1.1 200 OK" in resp
    

    This fixture can be easily overridden in any of the standard pytest locations (e.g. directly in the test file, or in conftest.py) to use a non-default event loop. This will take effect even if you're using the pytest.mark.asyncio marker and not the event_loop fixture directly.

    @&#8203;pytest.fixture
    def event_loop():
        loop = MyCustomLoop()
        yield loop
        loop.close()
    

    If the pytest.mark.asyncio marker is applied, a pytest hook will ensure the produced loop is set as the default global loop. Fixtures depending on the event_loop fixture can expect the policy to be properly modified when they run.

    unused_tcp_port

    Finds and yields a single unused TCP port on the localhost interface. Useful for binding temporary test servers.

    unused_tcp_port_factory

    A callable which returns a different unused TCP port each invocation. Useful when several unused TCP ports are required in a test.

    def a_test(unused_tcp_port_factory):
        port1, port2 = unused_tcp_port_factory(), unused_tcp_port_factory()
        ...
    

    unused_udp_port and unused_udp_port_factory

    Work just like their TCP counterparts but return unused UDP ports.

    Async fixtures

    Asynchronous fixtures are defined just like ordinary pytest fixtures, except they should be decorated with @pytest_asyncio.fixture.

    import pytest_asyncio
    
    @&#8203;pytest_asyncio.fixture
    async def async_gen_fixture():
        await asyncio.sleep(0.1)
        yield "a value"
    
    @&#8203;pytest_asyncio.fixture(scope="module")
    async def async_fixture():
        return await asyncio.sleep(0.1)
    

    All scopes are supported, but if you use a non-function scope you will need to redefine the event_loop fixture to have the same or broader scope. Async fixtures need the event loop, and so must have the same or narrower scope than the event_loop fixture.

    auto and legacy mode automatically converts async fixtures declared with the standard @pytest.fixture decorator to asyncio-driven versions.

    Markers

    pytest.mark.asyncio

    Mark your test coroutine with this marker and pytest will execute it as an asyncio task using the event loop provided by the event_loop fixture. See the introductory section for an example.

    The event loop used can be overridden by overriding the event_loop fixture (see above).

    In order to make your test code a little more concise, the pytest pytestmark_ feature can be used to mark entire modules or classes with this marker. Only test coroutines will be affected (by default, coroutines prefixed by test_), so, for example, fixtures are safe to define.

    import asyncio
    
    import pytest
    ### All test coroutines will be treated as marked.
    pytestmark = pytest.mark.asyncio
    
    async def test_example(event_loop):
        """No marker!"""
        await asyncio.sleep(0, loop=event_loop)
    

    In auto mode, the pytest.mark.asyncio marker can be omitted, the marker is added automatically to async test functions.

    Note about unittest

    Test classes subclassing the standard unittest library are not supported, users are recommended to use unitest.IsolatedAsyncioTestCase or an async framework such as asynctest.

    Changelog

    0.18.1 (22-02-10)

    • Fixes a regression that prevented async fixtures from working in synchronous tests. #​286

    0.18.0 (22-02-07)

    • Raise a warning if @​pytest.mark.asyncio is applied to non-async function. #​275
    • Support parametrized event_loop fixture. #​278

    0.17.2 (22-01-17)

    • Require typing-extensions on Python<3.8 only. #​269
    • Fix a regression in tests collection introduced by 0.17.1, the plugin works fine with non-python tests again. #​267

    0.17.1 (22-01-16)

    • Fixes a bug that prevents async Hypothesis tests from working without explicit asyncio marker when --asyncio-mode=auto is set. #​258
    • Fixed a bug that closes the default event loop if the loop doesn't exist #​257
    • Added type annotations. #​198
    • Show asyncio mode in pytest report headers. #​266
    • Relax asyncio_mode type definition; it allows to support pytest 6.1+. #​262

    0.17.0 (22-01-13)

    • [pytest-asyncio]{.title-ref} no longer alters existing event loop policies. #​168, #​188
    • Drop support for Python 3.6
    • Fixed an issue when pytest-asyncio was used in combination with [flaky]{.title-ref} or inherited asynchronous Hypothesis tests. #​178 #​231
    • Added flaky to test dependencies
    • Added unused_udp_port and unused_udp_port_factory fixtures (similar to unused_tcp_port and unused_tcp_port_factory counterparts. #​99
    • Added the plugin modes: strict, auto, and legacy. See documentation for details. #​125
    • Correctly process KeyboardInterrupt during async fixture setup phase #​219

    0.16.0 (2021-10-16)

    • Add support for Python 3.10

    0.15.1 (2021-04-22)

    • Hotfix for errors while closing event loops while replacing them. #​209 #​210

    0.15.0 (2021-04-19)

    • Add support for Python 3.9
    • Abandon support for Python 3.5. If you still require support for Python 3.5, please use pytest-asyncio v0.14 or earlier.
    • Set unused_tcp_port_factory fixture scope to 'session'. #​163
    • Properly close event loops when replacing them. #​208

    0.14.0 (2020-06-24)

    • Fix #​162, and event_loop fixture behavior now is coherent on all scopes. #​164

    0.12.0 (2020-05-04)

    • Run the event loop fixture as soon as possible. This helps with fixtures that have an implicit dependency on the event loop. #​156

    0.11.0 (2020-04-20)

    • Test on 3.8, drop 3.3 and 3.4. Stick to 0.10 for these versions. #​152
    • Use the new Pytest 5.4.0 Function API. We therefore depend on pytest >= 5.4.0. #​142
    • Better pytest.skip support. #​126

    0.10.0 (2019-01-08)

    • pytest-asyncio integrates with Hypothesis to support @given on async test functions using asyncio. #​102
    • Pytest 4.1 support. #​105

    0.9.0 (2018-07-28)

    • Python 3.7 support.
    • Remove event_loop_process_pool fixture and pytest.mark.asyncio_process_pool marker (see https://bugs.python.org/issue34075 for deprecation and removal details)

    0.8.0 (2017-09-23)

    • Improve integration with other packages (like aiohttp) with more careful event loop handling. #​64

    0.7.0 (2017-09-08)

    0.6.0 (2017-05-28)

    • Support for Python versions pre-3.5 has been dropped.
    • pytestmark now works on both module and class level.
    • The forbid_global_loop parameter has been removed.
    • Support for async and async gen fixtures has been added. #​45
    • The deprecation warning regarding asyncio.async() has been fixed. #​51

    0.5.0 (2016-09-07)

    • Introduced a changelog. #​31
    • The event_loop fixture is again responsible for closing itself. This makes the fixture slightly harder to correctly override, but enables other fixtures to depend on it correctly. #​30
    • Deal with the event loop policy by wrapping a special pytest hook, pytest_fixture_setup. This allows setting the policy before fixtures dependent on the event_loop fixture run, thus allowing them to take advantage of the forbid_global_loop parameter. As a consequence of this, we now depend on pytest 3.0. #​29

    0.4.1 (2016-06-01)

    • Fix a bug preventing the propagation of exceptions from the plugin. #​25

    0.4.0 (2016-05-30)

    • Make event_loop fixtures simpler to override by closing them in the plugin, instead of directly in the fixture. #​21
    • Introduce the forbid_global_loop parameter. #​21

    0.3.0 (2015-12-19)

    • Support for Python 3.5 async/await syntax. #​17

    0.2.0 (2015-08-01)

    • unused_tcp_port_factory fixture. #​10

    0.1.1 (2015-04-23)

    Initial release.

    Contributing

    Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.

    v0.18.0

    Compare Source


    title: 'pytest-asyncio: pytest support for asyncio'

    image

    image

    image

    Supported Python versions

    image

    pytest-asyncio is an Apache2 licensed library, written in Python, for testing asyncio code with pytest.

    asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier.

    @&#8203;pytest.mark.asyncio
    async def test_some_asyncio_code():
        res = await library.do_something()
        assert b"expected result" == res
    

    pytest-asyncio has been strongly influenced by pytest-tornado.

    Features

    • fixtures for creating and injecting versions of the asyncio event loop
    • fixtures for injecting unused tcp/udp ports
    • pytest markers for treating tests as asyncio coroutines
    • easy testing with non-default event loops
    • support for [async def]{.title-ref} fixtures and async generator fixtures
    • support auto mode to handle all async fixtures and tests automatically by asyncio; provide strict mode if a test suite should work with different async frameworks simultaneously, e.g. asyncio and trio.

    Installation

    To install pytest-asyncio, simply:

    $ pip install pytest-asyncio
    

    This is enough for pytest to pick up pytest-asyncio.

    Modes

    Starting from pytest-asyncio>=0.17, three modes are provided: auto, strict and legacy (default).

    The mode can be set by asyncio_mode configuration option in configuration file:

    ### pytest.ini
    [pytest]
    asyncio_mode = auto
    

    The value can be overriden by command-line option for pytest invocation:

    $ pytest tests --asyncio-mode=strict
    

    Auto mode

    When the mode is auto, all discovered async tests are considered asyncio-driven even if they have no @pytest.mark.asyncio marker.

    All async fixtures are considered asyncio-driven as well, even if they are decorated with a regular @pytest.fixture decorator instead of dedicated @pytest_asyncio.fixture counterpart.

    asyncio-driven means that tests and fixtures are executed by pytest-asyncio plugin.

    This mode requires the simplest tests and fixtures configuration and is recommended for default usage unless the same project and its test suite should execute tests from different async frameworks, e.g. asyncio and trio. In this case, auto-handling can break tests designed for other framework; plase use strict mode instead.

    Strict mode

    Strict mode enforces @pytest.mark.asyncio and @pytest_asyncio.fixture usage. Without these markers, tests and fixtures are not considered as asyncio-driven, other pytest plugin can handle them.

    Please use this mode if multiple async frameworks should be combined in the same test suite.

    Legacy mode

    This mode follows rules used by pytest-asyncio<0.17: tests are not auto-marked but fixtures are.

    This mode is used by default for the sake of backward compatibility, deprecation warnings are emitted with suggestion to either switching to auto mode or using strict mode with @pytest_asyncio.fixture decorators.

    In future, the default will be changed.

    Fixtures

    event_loop

    Creates and injects a new instance of the default asyncio event loop. By default, the loop will be closed at the end of the test (i.e. the default fixture scope is function).

    Note that just using the event_loop fixture won't make your test function a coroutine. You'll need to interact with the event loop directly, using methods like event_loop.run_until_complete. See the pytest.mark.asyncio marker for treating test functions like coroutines.

    Simply using this fixture will not set the generated event loop as the default asyncio event loop, or change the asyncio event loop policy in any way. Use pytest.mark.asyncio for this purpose.

    def test_http_client(event_loop):
        url = "http://httpbin.org/get"
        resp = event_loop.run_until_complete(http_client(url))
        assert b"HTTP/1.1 200 OK" in resp
    

    This fixture can be easily overridden in any of the standard pytest locations (e.g. directly in the test file, or in conftest.py) to use a non-default event loop. This will take effect even if you're using the pytest.mark.asyncio marker and not the event_loop fixture directly.

    @&#8203;pytest.fixture
    def event_loop():
        loop = MyCustomLoop()
        yield loop
        loop.close()
    

    If the pytest.mark.asyncio marker is applied, a pytest hook will ensure the produced loop is set as the default global loop. Fixtures depending on the event_loop fixture can expect the policy to be properly modified when they run.

    unused_tcp_port

    Finds and yields a single unused TCP port on the localhost interface. Useful for binding temporary test servers.

    unused_tcp_port_factory

    A callable which returns a different unused TCP port each invocation. Useful when several unused TCP ports are required in a test.

    def a_test(unused_tcp_port_factory):
        port1, port2 = unused_tcp_port_factory(), unused_tcp_port_factory()
        ...
    

    unused_udp_port and unused_udp_port_factory

    Work just like their TCP counterparts but return unused UDP ports.

    Async fixtures

    Asynchronous fixtures are defined just like ordinary pytest fixtures, except they should be decorated with @pytest_asyncio.fixture.

    import pytest_asyncio
    
    @&#8203;pytest_asyncio.fixture
    async def async_gen_fixture():
        await asyncio.sleep(0.1)
        yield "a value"
    
    @&#8203;pytest_asyncio.fixture(scope="module")
    async def async_fixture():
        return await asyncio.sleep(0.1)
    

    All scopes are supported, but if you use a non-function scope you will need to redefine the event_loop fixture to have the same or broader scope. Async fixtures need the event loop, and so must have the same or narrower scope than the event_loop fixture.

    auto and legacy mode automatically converts async fixtures declared with the standard @pytest.fixture decorator to asyncio-driven versions.

    Markers

    pytest.mark.asyncio

    Mark your test coroutine with this marker and pytest will execute it as an asyncio task using the event loop provided by the event_loop fixture. See the introductory section for an example.

    The event loop used can be overridden by overriding the event_loop fixture (see above).

    In order to make your test code a little more concise, the pytest pytestmark_ feature can be used to mark entire modules or classes with this marker. Only test coroutines will be affected (by default, coroutines prefixed by test_), so, for example, fixtures are safe to define.

    import asyncio
    
    import pytest
    ### All test coroutines will be treated as marked.
    pytestmark = pytest.mark.asyncio
    
    async def test_example(event_loop):
        """No marker!"""
        await asyncio.sleep(0, loop=event_loop)
    

    In auto mode, the pytest.mark.asyncio marker can be omitted, the marker is added automatically to async test functions.

    Note about unittest

    Test classes subclassing the standard unittest library are not supported, users are recommended to use unitest.IsolatedAsyncioTestCase or an async framework such as asynctest.

    Changelog

    0.18.0 (22-02-07)

    • Raise a warning if @​pytest.mark.asyncio is applied to non-async function. #​275
    • Support parametrized event_loop fixture. #​278

    0.17.2 (22-01-17)

    • Require typing-extensions on Python<3.8 only. #​269
    • Fix a regression in tests collection introduced by 0.17.1, the plugin works fine with non-python tests again. #​267

    0.17.1 (22-01-16)

    • Fixes a bug that prevents async Hypothesis tests from working without explicit asyncio marker when --asyncio-mode=auto is set. #​258
    • Fixed a bug that closes the default event loop if the loop doesn't exist #​257
    • Added type annotations. #​198
    • Show asyncio mode in pytest report headers. #​266
    • Relax asyncio_mode type definition; it allows to support pytest 6.1+. #​262

    0.17.0 (22-01-13)

    • [pytest-asyncio]{.title-ref} no longer alters existing event loop policies. #​168, #​188
    • Drop support for Python 3.6
    • Fixed an issue when pytest-asyncio was used in combination with [flaky]{.title-ref} or inherited asynchronous Hypothesis tests. #​178 #​231
    • Added flaky to test dependencies
    • Added unused_udp_port and unused_udp_port_factory fixtures (similar to unused_tcp_port and unused_tcp_port_factory counterparts. #​99
    • Added the plugin modes: strict, auto, and legacy. See documentation for details. #​125
    • Correctly process KeyboardInterrupt during async fixture setup phase #​219

    0.16.0 (2021-10-16)

    • Add support for Python 3.10

    0.15.1 (2021-04-22)

    • Hotfix for errors while closing event loops while replacing them. #​209 #​210

    0.15.0 (2021-04-19)

    • Add support for Python 3.9
    • Abandon support for Python 3.5. If you still require support for Python 3.5, please use pytest-asyncio v0.14 or earlier.
    • Set unused_tcp_port_factory fixture scope to 'session'. #​163
    • Properly close event loops when replacing them. #​208

    0.14.0 (2020-06-24)

    • Fix #​162, and event_loop fixture behavior now is coherent on all scopes. #​164

    0.12.0 (2020-05-04)

    • Run the event loop fixture as soon as possible. This helps with fixtures that have an implicit dependency on the event loop. #​156

    0.11.0 (2020-04-20)

    • Test on 3.8, drop 3.3 and 3.4. Stick to 0.10 for these versions. #​152
    • Use the new Pytest 5.4.0 Function API. We therefore depend on pytest >= 5.4.0. #​142
    • Better pytest.skip support. #​126

    0.10.0 (2019-01-08)

    • pytest-asyncio integrates with Hypothesis to support @given on async test functions using asyncio. #​102
    • Pytest 4.1 support. #​105

    0.9.0 (2018-07-28)

    • Python 3.7 support.
    • Remove event_loop_process_pool fixture and pytest.mark.asyncio_process_pool marker (see https://bugs.python.org/issue34075 for deprecation and removal details)

    0.8.0 (2017-09-23)

    • Improve integration with other packages (like aiohttp) with more careful event loop handling. #​64

    0.7.0 (2017-09-08)

    0.6.0 (2017-05-28)

    • Support for Python versions pre-3.5 has been dropped.
    • pytestmark now works on both module and class level.
    • The forbid_global_loop parameter has been removed.
    • Support for async and async gen fixtures has been added. #​45
    • The deprecation warning regarding asyncio.async() has been fixed. #​51

    0.5.0 (2016-09-07)

    • Introduced a changelog. #​31
    • The event_loop fixture is again responsible for closing itself. This makes the fixture slightly harder to correctly override, but enables other fixtures to depend on it correctly. #​30
    • Deal with the event loop policy by wrapping a special pytest hook, pytest_fixture_setup. This allows setting the policy before fixtures dependent on the event_loop fixture run, thus allowing them to take advantage of the forbid_global_loop parameter. As a consequence of this, we now depend on pytest 3.0. #​29

    0.4.1 (2016-06-01)

    • Fix a bug preventing the propagation of exceptions from the plugin. #​25

    0.4.0 (2016-05-30)

    • Make event_loop fixtures simpler to override by closing them in the plugin, instead of directly in the fixture. #​21
    • Introduce the forbid_global_loop parameter. #​21

    0.3.0 (2015-12-19)

    • Support for Python 3.5 async/await syntax. #​17

    0.2.0 (2015-08-01)

    • unused_tcp_port_factory fixture. #​10

    0.1.1 (2015-04-23)

    Initial release.

    Contributing

    Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.

    v0.17.2

    Compare Source


    title: 'pytest-asyncio: pytest support for asyncio'

    image

    image

    image

    Supported Python versions

    image

    pytest-asyncio is an Apache2 licensed library, written in Python, for testing asyncio code with pytest.

    asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier.

    @&#8203;pytest.mark.asyncio
    async def test_some_asyncio_code():
        res = await library.do_something()
        assert b"expected result" == res
    

    pytest-asyncio has been strongly influenced by pytest-tornado.

    Features

    • fixtures for creating and injecting versions of the asyncio event loop
    • fixtures for injecting unused tcp/udp ports
    • pytest markers for treating tests as asyncio coroutines
    • easy testing with non-default event loops
    • support for [async def]{.title-ref} fixtures and async generator fixtures
    • support auto mode to handle all async fixtures and tests automatically by asyncio; provide strict mode if a test suite should work with different async frameworks simultaneously, e.g. asyncio and trio.

    Installation

    To install pytest-asyncio, simply:

    $ pip install pytest-asyncio
    

    This is enough for pytest to pick up pytest-asyncio.

    Modes

    Starting from pytest-asyncio>=0.17, three modes are provided: auto, strict and legacy (default).

    The mode can be set by asyncio_mode configuration option in configuration file:

    ### pytest.ini
    [pytest]
    asyncio_mode = auto
    

    The value can be overriden by command-line option for pytest invocation:

    $ pytest tests --asyncio-mode=strict
    

    Auto mode

    When the mode is auto, all discovered async tests are considered asyncio-driven even if they have no @pytest.mark.asyncio marker.

    All async fixtures are considered asyncio-driven as well, even if they are decorated with a regular @pytest.fixture decorator instead of dedicated @pytest_asyncio.fixture counterpart.

    asyncio-driven means that tests and fixtures are executed by pytest-asyncio plugin.

    This mode requires the simplest tests and fixtures configuration and is recommended for default usage unless the same project and its test suite should execute tests from different async frameworks, e.g. asyncio and trio. In this case, auto-handling can break tests designed for other framework; plase use strict mode instead.

    Strict mode

    Strict mode enforces @pytest.mark.asyncio and @pytest_asyncio.fixture usage. Without these markers, tests and fixtures are not considered as asyncio-driven, other pytest plugin can handle them.

    Please use this mode if multiple async frameworks should be combined in the same test suite.

    Legacy mode

    This mode follows rules used by pytest-asyncio<0.17: tests are not auto-marked but fixtures are.

    This mode is used by default for the sake of backward compatibility, deprecation warnings are emitted with suggestion to either switching to auto mode or using strict mode with @pytest_asyncio.fixture decorators.

    In future, the default will be changed.

    Fixtures

    event_loop

    Creates and injects a new instance of the default asyncio event loop. By default, the loop will be closed at the end of the test (i.e. the default fixture scope is function).

    Note that just using the event_loop fixture won't make your test function a coroutine. You'll need to interact with the event loop directly, using methods like event_loop.run_until_complete. See the pytest.mark.asyncio marker for treating test functions like coroutines.

    Simply using this fixture will not set the generated event loop as the default asyncio event loop, or change the asyncio event loop policy in any way. Use pytest.mark.asyncio for this purpose.

    def test_http_client(event_loop):
        url = "http://httpbin.org/get"
        resp = event_loop.run_until_complete(http_client(url))
        assert b"HTTP/1.1 200 OK" in resp
    

    This fixture can be easily overridden in any of the standard pytest locations (e.g. directly in the test file, or in conftest.py) to use a non-default event loop. This will take effect even if you're using the pytest.mark.asyncio marker and not the event_loop fixture directly.

    @&#8203;pytest.fixture
    def event_loop():
        loop = MyCustomLoop()
        yield loop
        loop.close()
    

    If the pytest.mark.asyncio marker is applied, a pytest hook will ensure the produced loop is set as the default global loop. Fixtures depending on the event_loop fixture can expect the policy to be properly modified when they run.

    unused_tcp_port

    Finds and yields a single unused TCP port on the localhost interface. Useful for binding temporary test servers.

    unused_tcp_port_factory

    A callable which returns a different unused TCP port each invocation. Useful when several unused TCP ports are required in a test.

    def a_test(unused_tcp_port_factory):
        port1, port2 = unused_tcp_port_factory(), unused_tcp_port_factory()
        ...
    

    unused_udp_port and unused_udp_port_factory

    Work just like their TCP counterparts but return unused UDP ports.

    Async fixtures

    Asynchronous fixtures are defined just like ordinary pytest fixtures, except they should be decorated with @pytest_asyncio.fixture.

    import pytest_asyncio
    
    @&#8203;pytest_asyncio.fixture
    async def async_gen_fixture():
        await asyncio.sleep(0.1)
        yield "a value"
    
    @&#8203;pytest_asyncio.fixture(scope="module")
    async def async_fixture():
        return await asyncio.sleep(0.1)
    

    All scopes are supported, but if you use a non-function scope you will need to redefine the event_loop fixture to have the same or broader scope. Async fixtures need the event loop, and so must have the same or narrower scope than the event_loop fixture.

    auto and legacy mode automatically converts async fixtures declared with the standard @pytest.fixture decorator to asyncio-driven versions.

    Markers

    pytest.mark.asyncio

    Mark your test coroutine with this marker and pytest will execute it as an asyncio task using the event loop provided by the event_loop fixture. See the introductory section for an example.

    The event loop used can be overridden by overriding the event_loop fixture (see above).

    In order to make your test code a little more concise, the pytest pytestmark_ feature can be used to mark entire modules or classes with this marker. Only test coroutines will be affected (by default, coroutines prefixed by test_), so, for example, fixtures are safe to define.

    import asyncio
    
    import pytest
    ### All test coroutines will be treated as marked.
    pytestmark = pytest.mark.asyncio
    
    async def test_example(event_loop):
        """No marker!"""
        await asyncio.sleep(0, loop=event_loop)
    

    In auto mode, the pytest.mark.asyncio marker can be omitted, the marker is added automatically to async test functions.

    Note about unittest

    Test classes subclassing the standard unittest library are not supported, users are recommended to use unitest.IsolatedAsyncioTestCase or an async framework such as asynctest.

    Changelog

    0.17.2 (22-01-17)

    • Require typing-extensions on Python<3.8 only. #​269
    • Fix a regression in tests collection introduced by 0.17.1, the plugin works fine with non-python tests again. #​267

    0.17.1 (22-01-16)

    • Fixes a bug that prevents async Hypothesis tests from working without explicit asyncio marker when --asyncio-mode=auto is set. #​258
    • Fixed a bug that closes the default event loop if the loop doesn't exist #​257
    • Added type annotations. #​198
    • Show asyncio mode in pytest report headers. #​266
    • Relax asyncio_mode type definition; it allows to support pytest 6.1+. #​262

    0.17.0 (22-01-13)

    • [pytest-asyncio]{.title-ref} no longer alters existing event loop policies. #​168, #​188
    • Drop support for Python 3.6
    • Fixed an issue when pytest-asyncio was used in combination with [flaky]{.title-ref} or inherited asynchronous Hypothesis tests. #​178 #​231
    • Added flaky to test dependencies
    • Added unused_udp_port and unused_udp_port_factory fixtures (similar to unused_tcp_port and unused_tcp_port_factory counterparts. #​99
    • Added the plugin modes: strict, auto, and legacy. See documentation for details. #​125
    • Correctly process KeyboardInterrupt during async fixture setup phase #​219

    0.16.0 (2021-10-16)

    • Add support for Python 3.10

    0.15.1 (2021-04-22)

    • Hotfix for errors while closing event loops while replacing them. #​209 #​210

    0.15.0 (2021-04-19)

    • Add support for Python 3.9
    • Abandon support for Python 3.5. If you still require support for Python 3.5, please use pytest-asyncio v0.14 or earlier.
    • Set unused_tcp_port_factory fixture scope to 'session'. #​163
    • Properly close event loops when replacing them. #​208

    0.14.0 (2020-06-24)

    • Fix #​162, and event_loop fixture behavior now is coherent on all scopes. #​164

    0.12.0 (2020-05-04)

    • Run the event loop fixture as soon as possible. This helps with fixtures that have an implicit dependency on the event loop. #​156

    0.11.0 (2020-04-20)

    • Test on 3.8, drop 3.3 and 3.4. Stick to 0.10 for these versions. #​152
    • Use the new Pytest 5.4.0 Function API. We therefore depend on pytest >= 5.4.0. #​142
    • Better pytest.skip support. #​126

    0.10.0 (2019-01-08)

    • pytest-asyncio integrates with Hypothesis to support @given on async test functions using asyncio. #​102
    • Pytest 4.1 support. #​105

    0.9.0 (2018-07-28)

    • Python 3.7 support.
    • Remove event_loop_process_pool fixture and pytest.mark.asyncio_process_pool marker (see https://bugs.python.org/issue34075 for deprecation and removal details)

    0.8.0 (2017-09-23)

    • Improve integration with other packages (like aiohttp) with more careful event loop handling. #​64

    0.7.0 (2017-09-08)

    0.6.0 (2017-05-28)

    • Support for Python versions pre-3.5 has been dropped.
    • pytestmark now works on both module and class level.
    • The forbid_global_loop parameter has been removed.
    • Support for async and async gen fixtures has been added. #​45
    • The deprecation warning regarding asyncio.async() has been fixed. #​51

    0.5.0 (2016-09-07)

    • Introduced a changelog. #​31
    • The event_loop fixture is again responsible for closing itself. This makes the fixture slightly harder to correctly override, but enables other fixtures to depend on it correctly. #​30
    • Deal with the event loop policy by wrapping a special pytest hook, pytest_fixture_setup. This allows setting the policy before fixtures dependent on the event_loop fixture run, thus allowing them to take advantage of the forbid_global_loop parameter. As a consequence of this, we now depend on pytest 3.0. #​29

    0.4.1 (2016-06-01)

    • Fix a bug preventing the propagation of exceptions from the plugin. #​25

    0.4.0 (2016-05-30)

    • Make event_loop fixtures simpler to override by closing them in the plugin, instead of directly in the fixture. #​21
    • Introduce the forbid_global_loop parameter. #​21

    0.3.0 (2015-12-19)

    • Support for Python 3.5 async/await syntax. #​17

    0.2.0 (2015-08-01)

    • unused_tcp_port_factory fixture. #​10

    0.1.1 (2015-04-23)

    Initial release.

    Contributing

    Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.


    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 3
  • Update dependency pytest to v7

    Update dependency pytest to v7

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | pytest (source, changelog) | ^6.2.5 -> ^7.0.0 | age | adoption | passing | confidence |


    Release Notes

    pytest-dev/pytest

    v7.0.1

    Compare Source

    pytest 7.0.1 (2022-02-11)

    Bug Fixes

    • #​9608: Fix invalid importing of importlib.readers in Python 3.9.
    • #​9610: Restore [UnitTestFunction.obj]{.title-ref} to return unbound rather than bound method. Fixes a crash during a failed teardown in unittest TestCases with non-default [__init__]{.title-ref}. Regressed in pytest 7.0.0.
    • #​9636: The pythonpath plugin was renamed to python_path. This avoids a conflict with the pytest-pythonpath plugin.
    • #​9642: Fix running tests by id with :: in the parametrize portion.
    • #​9643: Delay issuing a ~pytest.PytestWarning{.interpreted-text role="class"} about diamond inheritance involving ~pytest.Item{.interpreted-text role="class"} and ~pytest.Collector{.interpreted-text role="class"} so it can be filtered using standard warning filters <warnings>{.interpreted-text role="ref"}.

    v7.0.0

    Compare Source

    pytest 7.0.0 (2022-02-03)

    (Please see the full set of changes for this release also in the 7.0.0rc1 notes below)

    Deprecations

    • #​9488: If custom subclasses of nodes like pytest.Item{.interpreted-text role="class"} override the __init__ method, they should take **kwargs. See uncooperative-constructors-deprecated{.interpreted-text role="ref"} for details.

      Note that a deprection warning is only emitted when there is a conflict in the arguments pytest expected to pass. This deprecation was already part of pytest 7.0.0rc1 but wasn't documented.

    Bug Fixes

    • #​9355: Fixed error message prints function decorators when using assert in Python 3.8 and above.
    • #​9396: Ensure pytest.Config.inifile{.interpreted-text role="attr"} is available during the pytest_cmdline_main <_pytest.hookspec.pytest_cmdline_main>{.interpreted-text role="func"} hook (regression during 7.0.0rc1).

    Improved Documentation

    • #​9404: Added extra documentation on alternatives to common misuses of [pytest.warns(None)]{.title-ref} ahead of its deprecation.
    • #​9505: Clarify where the configuration files are located. To avoid confusions documentation mentions that configuration file is located in the root of the repository.

    Trivial/Internal Changes

    • #​9521: Add test coverage to assertion rewrite path.

    pytest 7.0.0rc1 (2021-12-06)

    Breaking Changes

    • #​7259: The Node.reportinfo() <non-python tests>{.interpreted-text role="ref"} function first return value type has been expanded from [py.path.local | str]{.title-ref} to [os.PathLike[str] | str]{.title-ref}.

      Most plugins which refer to [reportinfo()]{.title-ref} only define it as part of a custom pytest.Item{.interpreted-text role="class"} implementation. Since [py.path.local]{.title-ref} is a [os.PathLike[str]]{.title-ref}, these plugins are unaffacted.

      Plugins and users which call [reportinfo()]{.title-ref}, use the first return value and interact with it as a [py.path.local]{.title-ref}, would need to adjust by calling [py.path.local(fspath)]{.title-ref}. Although preferably, avoid the legacy [py.path.local]{.title-ref} and use [pathlib.Path]{.title-ref}, or use [item.location]{.title-ref} or [item.path]{.title-ref}, instead.

      Note: pytest was not able to provide a deprecation period for this change.

    • #​8246: --version now writes version information to stdout rather than stderr.

    • #​8733: Drop a workaround for pyreadline that made it work with --pdb.

      The workaround was introduced in #​1281 in 2015, however since then pyreadline seems to have gone unmaintained, is generating warnings, and will stop working on Python 3.10.

    • #​9061: Using pytest.approx{.interpreted-text role="func"} in a boolean context now raises an error hinting at the proper usage.

      It is apparently common for users to mistakenly use pytest.approx like this:

      assert pytest.approx(actual, expected)
      

      While the correct usage is:

      assert actual == pytest.approx(expected)
      

      The new error message helps catch those mistakes.

    • #​9277: The pytest.Instance collector type has been removed. Importing pytest.Instance or _pytest.python.Instance returns a dummy type and emits a deprecation warning. See instance-collector-deprecation{.interpreted-text role="ref"} for details.

    • #​9308: PytestRemovedIn7Warning deprecation warnings are now errors by default.

      Following our plan to remove deprecated features with as little disruption as possible, all warnings of type PytestRemovedIn7Warning now generate errors instead of warning messages by default.

      The affected features will be effectively removed in pytest 7.1, so please consult the deprecations{.interpreted-text role="ref"} section in the docs for directions on how to update existing code.

      In the pytest 7.0.X series, it is possible to change the errors back into warnings as a stopgap measure by adding this to your pytest.ini file:

      [pytest]
      filterwarnings =
          ignore::pytest.PytestRemovedIn7Warning
      

      But this will stop working when pytest 7.1 is released.

      If you have concerns about the removal of a specific feature, please add a comment to 9308{.interpreted-text role="issue"}.

    Deprecations

    • #​7259: py.path.local arguments for hooks have been deprecated. See the deprecation note <legacy-path-hooks-deprecated>{.interpreted-text role="ref"} for full details.

      py.path.local arguments to Node constructors have been deprecated. See the deprecation note <node-ctor-fspath-deprecation>{.interpreted-text role="ref"} for full details.

      ::: {.note} ::: {.admonition-title} Note :::

      The name of the ~_pytest.nodes.Node{.interpreted-text role="class"} arguments and attributes (the new attribute being path) is the opposite of the situation for hooks (the old argument being path).

      This is an unfortunate artifact due to historical reasons, which should be resolved in future versions as we slowly get rid of the py{.interpreted-text role="pypi"} dependency (see 9283{.interpreted-text role="issue"} for a longer discussion). :::

    • #​7469: Directly constructing the following classes is now deprecated:

      • _pytest.mark.structures.Mark
      • _pytest.mark.structures.MarkDecorator
      • _pytest.mark.structures.MarkGenerator
      • _pytest.python.Metafunc
      • _pytest.runner.CallInfo
      • _pytest._code.ExceptionInfo
      • _pytest.config.argparsing.Parser
      • _pytest.config.argparsing.OptionGroup
      • _pytest.pytester.HookRecorder

      These constructors have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 8.

    • #​8242: Raising unittest.SkipTest{.interpreted-text role="class"} to skip collection of tests during the pytest collection phase is deprecated. Use pytest.skip{.interpreted-text role="func"} instead.

      Note: This deprecation only relates to using unittest.SkipTest{.interpreted-text role="class"} during test collection. You are probably not doing that. Ordinary usage of unittest.SkipTest{.interpreted-text role="class"} / unittest.TestCase.skipTest{.interpreted-text role="meth"} / unittest.skip{.interpreted-text role="func"} in unittest test cases is fully supported.

    • #​8315: Several behaviors of Parser.addoption <pytest.Parser.addoption>{.interpreted-text role="meth"} are now scheduled for removal in pytest 8 (deprecated since pytest 2.4.0):

      • parser.addoption(..., help=".. %default ..") - use %(default)s instead.
      • parser.addoption(..., type="int/string/float/complex") - use type=int etc. instead.
    • #​8447: Defining a custom pytest node type which is both an pytest.Item <Item>{.interpreted-text role="class"} and a pytest.Collector <Collector>{.interpreted-text role="class"} (e.g. pytest.File <File>{.interpreted-text role="class"}) now issues a warning. It was never sanely supported and triggers hard to debug errors.

      See the deprecation note <diamond-inheritance-deprecated>{.interpreted-text role="ref"} for full details.

    • #​8592: pytest_cmdline_preparse{.interpreted-text role="hook"} has been officially deprecated. It will be removed in a future release. Use pytest_load_initial_conftests{.interpreted-text role="hook"} instead.

      See the deprecation note <cmdline-preparse-deprecated>{.interpreted-text role="ref"} for full details.

    • #​8645: pytest.warns(None) <pytest.warns>{.interpreted-text role="func"} is now deprecated because many people used it to mean "this code does not emit warnings", but it actually had the effect of checking that the code emits at least one warning of any type - like pytest.warns() or pytest.warns(Warning).

    • #​8948: pytest.skip(msg=...) <pytest.skip>{.interpreted-text role="func"}, pytest.fail(msg=...) <pytest.fail>{.interpreted-text role="func"} and pytest.exit(msg=...) <pytest.exit>{.interpreted-text role="func"} signatures now accept a reason argument instead of msg. Using msg still works, but is deprecated and will be removed in a future release.

      This was changed for consistency with pytest.mark.skip <pytest.mark.skip>{.interpreted-text role="func"} and pytest.mark.xfail <pytest.mark.xfail>{.interpreted-text role="func"} which both accept reason as an argument.

    • #​8174: The following changes have been made to types reachable through pytest.ExceptionInfo.traceback{.interpreted-text role="attr"}:

      • The path property of _pytest.code.Code returns Path instead of py.path.local.
      • The path property of _pytest.code.TracebackEntry returns Path instead of py.path.local.

      There was no deprecation period for this change (sorry!).

    Features

    • #​5196: Tests are now ordered by definition order in more cases.

      In a class hierarchy, tests from base classes are now consistently ordered before tests defined on their subclasses (reverse MRO order).

    • #​7132: Added two environment variables PYTEST_THEME{.interpreted-text role="envvar"} and PYTEST_THEME_MODE{.interpreted-text role="envvar"} to let the users customize the pygments theme used.

    • #​7259: Added cache.mkdir() <pytest.Cache.mkdir>{.interpreted-text role="meth"}, which is similar to the existing cache.makedir() <pytest.Cache.makedir>{.interpreted-text role="meth"}, but returns a pathlib.Path{.interpreted-text role="class"} instead of a legacy py.path.local.

      Added a paths type to parser.addini() <pytest.Parser.addini>{.interpreted-text role="meth"}, as in parser.addini("mypaths", "my paths", type="paths"), which is similar to the existing pathlist, but returns a list of pathlib.Path{.interpreted-text role="class"} instead of legacy py.path.local.

    • #​7469: The types of objects used in pytest's API are now exported so they may be used in type annotations.

      The newly-exported types are:

      • pytest.Config for Config <pytest.Config>{.interpreted-text role="class"}.
      • pytest.Mark for marks <pytest.Mark>{.interpreted-text role="class"}.
      • pytest.MarkDecorator for mark decorators <pytest.MarkDecorator>{.interpreted-text role="class"}.
      • pytest.MarkGenerator for the pytest.mark <pytest.MarkGenerator>{.interpreted-text role="class"} singleton.
      • pytest.Metafunc for the metafunc <pytest.MarkGenerator>{.interpreted-text role="class"} argument to the pytest_generate_tests{.interpreted-text role="hook"} hook.
      • pytest.CallInfo for the CallInfo <pytest.CallInfo>{.interpreted-text role="class"} type passed to various hooks.
      • pytest.PytestPluginManager for PytestPluginManager <pytest.PytestPluginManager>{.interpreted-text role="class"}.
      • pytest.ExceptionInfo for the ExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"} type returned from pytest.raises{.interpreted-text role="func"} and passed to various hooks.
      • pytest.Parser for the Parser <pytest.Parser>{.interpreted-text role="class"} type passed to the pytest_addoption{.interpreted-text role="hook"} hook.
      • pytest.OptionGroup for the OptionGroup <pytest.OptionGroup>{.interpreted-text role="class"} type returned from the parser.addgroup <pytest.Parser.getgroup>{.interpreted-text role="func"} method.
      • pytest.HookRecorder for the HookRecorder <pytest.HookRecorder>{.interpreted-text role="class"} type returned from ~pytest.Pytester{.interpreted-text role="class"}.
      • pytest.RecordedHookCall for the RecordedHookCall <pytest.HookRecorder>{.interpreted-text role="class"} type returned from ~pytest.HookRecorder{.interpreted-text role="class"}.
      • pytest.RunResult for the RunResult <pytest.RunResult>{.interpreted-text role="class"} type returned from ~pytest.Pytester{.interpreted-text role="class"}.
      • pytest.LineMatcher for the LineMatcher <pytest.RunResult>{.interpreted-text role="class"} type used in ~pytest.RunResult{.interpreted-text role="class"} and others.
      • pytest.TestReport for the TestReport <pytest.TestReport>{.interpreted-text role="class"} type used in various hooks.
      • pytest.CollectReport for the CollectReport <pytest.CollectReport>{.interpreted-text role="class"} type used in various hooks.

      Constructing most of them directly is not supported; they are only meant for use in type annotations. Doing so will emit a deprecation warning, and may become a hard-error in pytest 8.0.

      Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.

    • #​7856: --import-mode=importlib <import-modes>{.interpreted-text role="ref"} now works with features that depend on modules being on :pysys.modules{.interpreted-text role="data"}, such as pickle{.interpreted-text role="mod"} and dataclasses{.interpreted-text role="mod"}.

    • #​8144: The following hooks now receive an additional pathlib.Path argument, equivalent to an existing py.path.local argument:

      • pytest_ignore_collect{.interpreted-text role="hook"} - The collection_path parameter (equivalent to existing path parameter).
      • pytest_collect_file{.interpreted-text role="hook"} - The file_path parameter (equivalent to existing path parameter).
      • pytest_pycollect_makemodule{.interpreted-text role="hook"} - The module_path parameter (equivalent to existing path parameter).
      • pytest_report_header{.interpreted-text role="hook"} - The start_path parameter (equivalent to existing startdir parameter).
      • pytest_report_collectionfinish{.interpreted-text role="hook"} - The start_path parameter (equivalent to existing startdir parameter).

      ::: {.note} ::: {.admonition-title} Note :::

      The name of the ~_pytest.nodes.Node{.interpreted-text role="class"} arguments and attributes (the new attribute being path) is the opposite of the situation for hooks (the old argument being path).

      This is an unfortunate artifact due to historical reasons, which should be resolved in future versions as we slowly get rid of the py{.interpreted-text role="pypi"} dependency (see 9283{.interpreted-text role="issue"} for a longer discussion). :::

    • #​8251: Implement Node.path as a pathlib.Path. Both the old fspath and this new attribute gets set no matter whether path or fspath (deprecated) is passed to the constructor. It is a replacement for the fspath attribute (which represents the same path as py.path.local). While fspath is not deprecated yet due to the ongoing migration of methods like ~_pytest.Item.reportinfo{.interpreted-text role="meth"}, we expect to deprecate it in a future release.

      ::: {.note} ::: {.admonition-title} Note :::

      The name of the ~_pytest.nodes.Node{.interpreted-text role="class"} arguments and attributes (the new attribute being path) is the opposite of the situation for hooks (the old argument being path).

      This is an unfortunate artifact due to historical reasons, which should be resolved in future versions as we slowly get rid of the py{.interpreted-text role="pypi"} dependency (see 9283{.interpreted-text role="issue"} for a longer discussion). :::

    • #​8421: pytest.approx{.interpreted-text role="func"} now works on ~decimal.Decimal{.interpreted-text role="class"} within mappings/dicts and sequences/lists.

    • #​8606: pytest invocations with --fixtures-per-test and --fixtures have been enriched with:

      • Fixture location path printed with the fixture name.
      • First section of the fixture's docstring printed under the fixture name.
      • Whole of fixture's docstring printed under the fixture name using --verbose option.
    • #​8761: New version-tuple{.interpreted-text role="ref"} attribute, which makes it simpler for users to do something depending on the pytest version (such as declaring hooks which are introduced in later versions).

    • #​8789: Switch TOML parser from toml to tomli for TOML v1.0.0 support in pyproject.toml.

    • #​8920: Added pytest.Stash{.interpreted-text role="class"}, a facility for plugins to store their data on ~pytest.Config{.interpreted-text role="class"} and ~_pytest.nodes.Node{.interpreted-text role="class"}s in a type-safe and conflict-free manner. See plugin-stash{.interpreted-text role="ref"} for details.

    • #​8953: RunResult <_pytest.pytester.RunResult>{.interpreted-text role="class"} method assert_outcomes <_pytest.pytester.RunResult.assert_outcomes>{.interpreted-text role="meth"} now accepts a warnings argument to assert the total number of warnings captured.

    • #​8954: --debug flag now accepts a str{.interpreted-text role="class"} file to route debug logs into, remains defaulted to [pytestdebug.log]{.title-ref}.

    • #​9023: Full diffs are now always shown for equality assertions of iterables when [CI]{.title-ref} or BUILD_NUMBER is found in the environment, even when -v isn't used.

    • #​9113: RunResult <_pytest.pytester.RunResult>{.interpreted-text role="class"} method assert_outcomes <_pytest.pytester.RunResult.assert_outcomes>{.interpreted-text role="meth"} now accepts a deselected argument to assert the total number of deselected tests.

    • #​9114: Added pythonpath{.interpreted-text role="confval"} setting that adds listed paths to sys.path{.interpreted-text role="data"} for the duration of the test session. If you currently use the pytest-pythonpath or pytest-srcpaths plugins, you should be able to replace them with built-in [pythonpath]{.title-ref} setting.

    Improvements

    • #​7480: A deprecation scheduled to be removed in a major version X (e.g. pytest 7, 8, 9, ...) now uses warning category [PytestRemovedInXWarning]{.title-ref}, a subclass of ~pytest.PytestDeprecationWarning{.interpreted-text role="class"}, instead of PytestDeprecationWarning{.interpreted-text role="class"} directly.

      See backwards-compatibility{.interpreted-text role="ref"} for more details.

    • #​7864: Improved error messages when parsing warning filters.

      Previously pytest would show an internal traceback, which besides being ugly sometimes would hide the cause of the problem (for example an ImportError while importing a specific warning type).

    • #​8335: Improved pytest.approx{.interpreted-text role="func"} assertion messages for sequences of numbers.

      The assertion messages now dumps a table with the index and the error of each diff. Example:

      >       assert [1, 2, 3, 4] == pytest.approx([1, 3, 3, 5])
      E       assert comparison failed for 2 values:
      E         Index | Obtained | Expected
      E         1     | 2        | 3 +- 3.0e-06
      E         3     | 4        | 5 +- 5.0e-06
      
    • #​8403: By default, pytest will truncate long strings in assert errors so they don't clutter the output too much, currently at 240 characters by default.

      However, in some cases the longer output helps, or is even crucial, to diagnose a failure. Using -v will now increase the truncation threshold to 2400 characters, and -vv or higher will disable truncation entirely.

    • #​8509: Fixed issue where unittest.TestCase.setUpClass{.interpreted-text role="meth"} is not called when a test has [/]{.title-ref} in its name since pytest 6.2.0.

      This refers to the path part in pytest node IDs, e.g. TestClass::test_it in the node ID tests/test_file.py::TestClass::test_it.

      Now, instead of assuming that the test name does not contain /, it is assumed that test path does not contain ::. We plan to hopefully make both of these work in the future.

    • #​8803: It is now possible to add colors to custom log levels on cli log.

      By using add_color_level <_pytest.logging.add_color_level>{.interpreted-text role="func"} from a pytest_configure hook, colors can be added:

      logging_plugin = config.pluginmanager.get_plugin('logging-plugin')
      logging_plugin.log_cli_handler.formatter.add_color_level(logging.INFO, 'cyan')
      logging_plugin.log_cli_handler.formatter.add_color_level(logging.SPAM, 'blue')
      

      See log_colors{.interpreted-text role="ref"} for more information.

    • #​8822: When showing fixture paths in [--fixtures]{.title-ref} or [--fixtures-by-test]{.title-ref}, fixtures coming from pytest itself now display an elided path, rather than the full path to the file in the [site-packages]{.title-ref} directory.

    • #​8898: Complex numbers are now treated like floats and integers when generating parameterization IDs.

    • #​9062: --stepwise-skip now implicitly enables --stepwise and can be used on its own.

    • #​9205: pytest.Cache.set{.interpreted-text role="meth"} now preserves key order when saving dicts.

    Bug Fixes

    • #​7124: Fixed an issue where __main__.py would raise an ImportError when --doctest-modules was provided.

    • #​8061: Fixed failing staticmethod test cases if they are inherited from a parent test class.

    • #​8192: testdir.makefile now silently accepts values which don't start with . to maintain backward compatibility with older pytest versions.

      pytester.makefile now issues a clearer error if the . is missing in the ext argument.

    • #​8258: Fixed issue where pytest's faulthandler support would not dump traceback on crashes if the faulthandler{.interpreted-text role="mod"} module was already enabled during pytest startup (using python -X dev -m pytest for example).

    • #​8317: Fixed an issue where illegal directory characters derived from getpass.getuser() raised an OSError.

    • #​8367: Fix Class.from_parent so it forwards extra keyword arguments to the constructor.

    • #​8377: The test selection options pytest -k and pytest -m now support matching names containing forward slash (/) characters.

    • #​8384: The @pytest.mark.skip decorator now correctly handles its arguments. When the reason argument is accidentally given both positional and as a keyword (e.g. because it was confused with skipif), a TypeError now occurs. Before, such tests were silently skipped, and the positional argument ignored. Additionally, reason is now documented correctly as positional or keyword (rather than keyword-only).

    • #​8394: Use private names for internal fixtures that handle classic setup/teardown so that they don't show up with the default --fixtures invocation (but they still show up with --fixtures -v).

    • #​8456: The required_plugins{.interpreted-text role="confval"} config option now works correctly when pre-releases of plugins are installed, rather than falsely claiming that those plugins aren't installed at all.

    • #​8464: -c <config file> now also properly defines rootdir as the directory that contains <config file>.

    • #​8503: pytest.MonkeyPatch.syspath_prepend{.interpreted-text role="meth"} no longer fails when setuptools is not installed. It now only calls pkg_resources.fixup_namespace_packages{.interpreted-text role="func"} if pkg_resources was previously imported, because it is not needed otherwise.

    • #​8548: Introduce fix to handle precision width in log-cli-format in turn to fix output coloring for certain formats.

    • #​8796: Fixed internal error when skipping doctests.

    • #​8983: The test selection options pytest -k and pytest -m now support matching names containing backslash ([\]{.title-ref}) characters. Backslashes are treated literally, not as escape characters (the values being matched against are already escaped).

    • #​8990: Fix [pytest -vv]{.title-ref} crashing with an internal exception [AttributeError: 'str' object has no attribute 'relative_to']{.title-ref} in some cases.

    • #​9077: Fixed confusing error message when request.fspath / request.path was accessed from a session-scoped fixture.

    • #​9131: Fixed the URL used by --pastebin to use bpa.st.

    • #​9163: The end line number and end column offset are now properly set for rewritten assert statements.

    • #​9169: Support for the files API from importlib.resources within rewritten files.

    • #​9272: The nose compatibility module-level fixtures [setup()]{.title-ref} and [teardown()]{.title-ref} are now only called once per module, instead of for each test function. They are now called even if object-level [setup]{.title-ref}/[teardown]{.title-ref} is defined.

    Improved Documentation

    • #​4320: Improved docs for [pytester.copy_example]{.title-ref}.
    • #​5105: Add automatically generated plugin-list{.interpreted-text role="ref"}. The list is updated on a periodic schedule.
    • #​8337: Recommend numpy.testing module on pytest.approx{.interpreted-text role="func"} documentation.
    • #​8655: Help text for --pdbcls more accurately reflects the option's behavior.
    • #​9210: Remove incorrect docs about confcutdir being a configuration option: it can only be set through the --confcutdir command-line option.
    • #​9242: Upgrade readthedocs configuration to use a newer Ubuntu version` with better unicode support for PDF docs.
    • #​9341: Various methods commonly used for non-python tests{.interpreted-text role="ref"} are now correctly documented in the reference docs. They were undocumented previously.

    Trivial/Internal Changes

    • #​8133: Migrate to setuptools_scm 6.x to use SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST for more robust release tooling.
    • #​8174: The following changes have been made to internal pytest types/functions:
      • The _pytest.code.getfslineno() function returns Path instead of py.path.local.
      • The _pytest.python.path_matches_patterns() function takes Path instead of py.path.local.
      • The _pytest._code.Traceback.cut() function accepts any os.PathLike[str], not just py.path.local.
    • #​8248: Internal Restructure: let python.PyObjMixin inherit from nodes.Node to carry over typing information.
    • #​8432: Improve error message when pytest.skip{.interpreted-text role="func"} is used at module level without passing [allow_module_level=True]{.title-ref}.
    • #​8818: Ensure regendoc opts out of TOX_ENV cachedir selection to ensure independent example test runs.
    • #​8913: The private CallSpec2._arg2scopenum attribute has been removed after an internal refactoring.
    • #​8967: pytest_assertion_pass{.interpreted-text role="hook"} is no longer considered experimental and future changes to it will be considered more carefully.
    • #​9202: Add github action to upload coverage report to codecov instead of bash uploader.
    • #​9225: Changed the command used to create sdist and wheel artifacts: using the build package instead of setup.py.
    • #​9351: Correct minor typos in doc/en/example/special.rst.

    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 3
  • Update actions/upload-artifact action to v3

    Update actions/upload-artifact action to v3

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Type | Update | Change | |---|---|---|---| | actions/upload-artifact | action | major | v2 -> v3 |


    Release Notes

    actions/upload-artifact

    v3

    Compare Source


    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update actions/setup-python action to v3 - autoclosed

    Update actions/setup-python action to v3 - autoclosed

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Type | Update | Change | |---|---|---|---| | actions/setup-python | action | major | v2 -> v3 |


    Release Notes

    actions/setup-python

    v3

    Compare Source


    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update dependency httpx to ^0.22.0

    Update dependency httpx to ^0.22.0

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | httpx (changelog) | ^0.21.3 -> ^0.22.0 | age | adoption | passing | confidence |


    Release Notes

    encode/httpx

    v0.22.0

    Compare Source

    Added
    Fixed
    • Don't perform unreliable close/warning on __del__ with unclosed clients. (#​2026)
    • Fix Headers.update(...) to correctly handle repeated headers (#​2038)

    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update dependency fastapi to ^0.73.0

    Update dependency fastapi to ^0.73.0

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | fastapi | ^0.72.0 -> ^0.73.0 | age | adoption | passing | confidence |


    Release Notes

    tiangolo/fastapi

    v0.73.0

    Compare Source

    Features
    Docs
    Fixes
    Internal

    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update python Docker tag to v3.10.2

    Update python Docker tag to v3.10.2

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Type | Update | Change | |---|---|---|---| | python | final | patch | 3.10.1 -> 3.10.2 |


    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update actions/checkout action to v2

    Update actions/checkout action to v2

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Type | Update | Change | |---|---|---|---| | actions/checkout | action | major | v1 -> v2 |


    Release Notes

    actions/checkout

    v2

    Compare Source


    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 1
  • Update dependency fastapi to ^0.72.0

    Update dependency fastapi to ^0.72.0

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | fastapi | ^0.71.0 -> ^0.72.0 | age | adoption | passing | confidence |


    Release Notes

    tiangolo/fastapi

    v0.72.0

    Compare Source

    Features
    Docs
    Translations
    Internal

    Configuration

    📅 Schedule: At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 1
  • Add ddns functionality.

    Add ddns functionality.

    • Use Ipify to get public IP.
    • Adds /metadata and /metadata/check/ip endpoints.
    • Sends notification via Webhook to Discord if detecting public IP changes.
    • Under the covers:
      • Use uMongo for ORM.
    opened by ivanklee86 0
  • Update dependency discord-webhook to ^0.17.0

    Update dependency discord-webhook to ^0.17.0

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | discord-webhook | ^0.15.0 -> ^0.17.0 | age | adoption | passing | confidence |


    Release Notes

    lovvskillz/python-discord-webhook

    v0.17.0

    Compare Source

    🛠 Breaking Changes
    • ColourNotInRangeException was renamed to ColorNotInRangeException
    🩹 Fixes
    • fix async file attachments

    v0.16.3

    Compare Source

    🩹 Fixes
    • only check if color is in range if color was set

    v0.16.2

    Compare Source

    🩹 Fixes
    • fix support for using a list of webhook URLs

    v0.16.1

    Compare Source

    🩹 Fixes
    • fix hex to int color conversion

    v0.16.0

    Compare Source

    🎉 Features
    • add async support

    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box

    This PR has been generated by Mend Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update docker/metadata-action action to v4

    Update docker/metadata-action action to v4

    Mend Renovate

    This PR contains the following updates:

    | Package | Type | Update | Change | |---|---|---|---| | docker/metadata-action | action | major | v3 -> v4 |


    Release Notes

    docker/metadata-action

    v4

    Compare Source


    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box

    This PR has been generated by Mend Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update dependency motor to v3

    Update dependency motor to v3

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | motor | ^2.5.1 -> ^3.0.0 | age | adoption | passing | confidence |


    Release Notes

    mongodb/motor

    v3.1.1: Motor 3.1.1

    Compare Source

    Release notes: https://www.mongodb.com/community/forums/t/mongodb-motor-3-1-1-released/195738

    v3.0.0: Motor 3.0.0

    Compare Source

    Release notes: https://www.mongodb.com/community/forums/t/mongodb-motor-3-0-0-released/160708


    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box

    This PR has been generated by Mend Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update github/codeql-action action to v2

    Update github/codeql-action action to v2

    Mend Renovate

    This PR contains the following updates:

    | Package | Type | Update | Change | |---|---|---|---| | github/codeql-action | action | major | v1 -> v2 |


    Release Notes

    github/codeql-action

    v2

    Compare Source


    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box

    This PR has been generated by Mend Renovate. View repository job log here.

    opened by renovate[bot] 3
  • Update dependency aiomysql to ^0.1.0

    Update dependency aiomysql to ^0.1.0

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | aiomysql | ^0.0.22 -> ^0.1.0 | age | adoption | passing | confidence |


    Release Notes

    aio-libs/aiomysql

    v0.1.1

    Compare Source

    Changes

    0.1.1 (2022-05-08) ^^^^^^^^^^^^^^^^^^

    • Fix SSL connection handshake charset not respecting client configuration #​776

    0.1.0 (2022-04-11) ^^^^^^^^^^^^^^^^^^

    • Don't send sys.argv[0] as program_name to MySQL server by default #​620

    • Allow running process as anonymous uid #​587

    • Fix timed out MySQL 8.0 connections raising InternalError rather than OperationalError #​660

    • Fix timed out MySQL 8.0 connections being returned from Pool #​660

    • Ensure connections are properly closed before raising an OperationalError when the server connection is lost #​660

    • Ensure connections are properly closed before raising an InternalError when packet sequence numbers are out of sync #​660

    • Unix sockets are now internally considered secure, allowing sha256_password and caching_sha2_password auth methods to be used #​695

    • Test suite now also tests unix socket connections #​696

    • Fix SSCursor raising InternalError when last result was not fully retrieved #​635

    • Remove deprecated no_delay argument #​702

    • Support PyMySQL up to version 1.0.2 #​643

    • Bump minimal PyMySQL version to 1.0.0 #​713

    • Align % formatting in Cursor.executemany() with Cursor.execute(), literal % now need to be doubled in Cursor.executemany() #​714

    • Fixed unlimited Pool size not working, this is now working as documented by passing maxsize=0 to create_pool #​119

    • Added Pool.closed property as present in aiopg #​463

    • Fixed SQLAlchemy connection context iterator #​410

    • Fix error packet handling for SSCursor #​428

    • Required python version is now properly documented in python_requires instead of failing on setup.py execution #​731

    • Add rsa extras_require depending on PyMySQL[rsa] #​557

    • Migrate to PEP 517 build system #​746

    • Self-reported __version__ now returns version generated by setuptools-scm during build, otherwise 'unknown' #​748

    • Fix SSCursor raising query timeout error on wrong query #​428

    0.0.22 (2021-11-14) ^^^^^^^^^^^^^^^^^^^

    0.0.21 (2020-11-26) ^^^^^^^^^^^^^^^^^^^

    • Allow to use custom Cursor subclasses #​374

    • Fill Connection class with actual client version #​388

    • Fix legacy aiter methods #​403

    • Fix & update docs #​418 #​437

    • Ignore pyenv's .python-version file #​424

    • Replace asyncio.streams.IncompleteReadError with asyncio.IncompleteReadError #​460 #​454

    • Add support for SQLAlchemy default parameters #​455 #​466

    • Update dependencies #​485

    • Support Python 3.7 & 3.8 #​493

    0.0.20 (2018-12-19) ^^^^^^^^^^^^^^^^^^^

    • Fixed connect_timeout #​360

    • Fixed support for SQLA executemany #​324

    • Fix the python 3.7 compatibility #​357

    • Fixed reuse connections when StreamReader has an exception #​339

    • Fixes warning when inserting binary strings #​326

    0.0.19 (2018-07-12) ^^^^^^^^^^^^^^^^^^^

    • See v0.0.18

    0.0.18 (2018-07-09) ^^^^^^^^^^^^^^^^^^^

    • Updated to support latest PyMySQL changes.

    • aiomysql now sends client connection info.

    • MySQL8+ Support including sha256_password and cached_sha2_password authentication plugins.

    • Default max packet length sent to the server is no longer 1.

    • Fixes issue where cursor.nextset can hang on query sets that raise errors.

    0.0.17 (2018-07-06) ^^^^^^^^^^^^^^^^^^^

    • Pinned version of PyMySQL

    0.0.16 (2018-06-03) ^^^^^^^^^^^^^^^^^^^

    • Added ability to execute precompiled sqlalchemy queries #​294 (Thanks @​vlanse)

    0.0.15 (2018-05-20) ^^^^^^^^^^^^^^^^^^^

    • Fixed handling of user-defined types for sqlalchemy #​290

    • Fix KeyError when server reports unknown collation #​289

    0.0.14 (2018-04-22) ^^^^^^^^^^^^^^^^^^^

    • Fixed SSL connection finalization #​282

    0.0.13 (2018-04-19) ^^^^^^^^^^^^^^^^^^^

    0.0.12 (2018-01-18) ^^^^^^^^^^^^^^^^^^^

    • Fixed support for SQLAlchemy 1.2.0

    • Fixed argument for cursor.execute in sa engine #​239 (Thanks @​NotSoSuper)

    0.0.11 (2017-12-06) ^^^^^^^^^^^^^^^^^^^

    • Fixed README formatting on pypi

    0.0.10 (2017-12-06) ^^^^^^^^^^^^^^^^^^^

    0.0.9 (2016-09-14) ^^^^^^^^^^^^^^^^^^

    0.0.8 (2016-08-24) ^^^^^^^^^^^^^^^^^^

    0.0.7 (2016-01-27) ^^^^^^^^^^^^^^^^^^

    • Fix for multiple results issue, ported from pymysql #​52

    • Fixed useless warning with no_delay option #​55

    • Added async/await support for Engine, SAConnection, Transaction #​57

    • pool.release returns future so we can wait on it in aexit #​60

    • Update to PyMySQL 0.6.7

    0.0.6 (2015-12-11) ^^^^^^^^^^^^^^^^^^

    0.0.5 (2015-10-28) ^^^^^^^^^^^^^^^^^^

    • no_delay option is deprecated and True by default

    • Add Cursor.mogrify() method

    • Support for "LOAD LOCAL INFILE" query.

    • Check connection inside pool, in case of timeout drop it, fixes #​25

    • Add support of python 3.5 features to pool, connection and cursor

    0.0.4 (2015-05-23) ^^^^^^^^^^^^^^^^^^

    • Allow to call connection.wait_closed twice.

    • Fixed sqlalchemy 1.0.0 support.

    • Fix #​11: Rename Connection.wait_closed() to .ensure_closed()

    • Raise ResourceWarning on non-closed Connection

    • Rename Connection.connect to _connect

    0.0.3 (2015-03-10) ^^^^^^^^^^^^^^^^^^

    • Added support for PyMySQL up to 0.6.6.

    • Ported improvements from PyMySQL.

    • Added basic documentation.

    • Fixed and added more examples.

    0.0.2 (2015-02-17) ^^^^^^^^^^^^^^^^^^

    • Added MANIFEST.in.

    0.0.1 (2015-02-17) ^^^^^^^^^^^^^^^^^^

    • Initial release.

    • Implemented plain connections: connect, Connection, Cursor.

    • Implemented database pools.

    • Ported sqlalchemy optional support.

    v0.1.0

    Compare Source

    Changes

    0.1.0 (2022-04-11) ^^^^^^^^^^^^^^^^^^

    • Don't send sys.argv[0] as program_name to MySQL server by default #​620

    • Allow running process as anonymous uid #​587

    • Fix timed out MySQL 8.0 connections raising InternalError rather than OperationalError #​660

    • Fix timed out MySQL 8.0 connections being returned from Pool #​660

    • Ensure connections are properly closed before raising an OperationalError when the server connection is lost #​660

    • Ensure connections are properly closed before raising an InternalError when packet sequence numbers are out of sync #​660

    • Unix sockets are now internally considered secure, allowing sha256_password and caching_sha2_password auth methods to be used #​695

    • Test suite now also tests unix socket connections #​696

    • Fix SSCursor raising InternalError when last result was not fully retrieved #​635

    • Remove deprecated no_delay argument #​702

    • Support PyMySQL up to version 1.0.2 #​643

    • Bump minimal PyMySQL version to 1.0.0 #​713

    • Align % formatting in Cursor.executemany() with Cursor.execute(), literal % now need to be doubled in Cursor.executemany() #​714

    • Fixed unlimited Pool size not working, this is now working as documented by passing maxsize=0 to create_pool #​119

    • Added Pool.closed property as present in aiopg #​463

    • Fixed SQLAlchemy connection context iterator #​410

    • Fix error packet handling for SSCursor #​428

    • Required python version is now properly documented in python_requires instead of failing on setup.py execution #​731

    • Add rsa extras_require depending on PyMySQL[rsa] #​557

    • Migrate to PEP 517 build system #​746

    • Self-reported __version__ now returns version generated by setuptools-scm during build, otherwise 'unknown' #​748

    • Fix SSCursor raising query timeout error on wrong query #​428

    0.0.22 (2021-11-14) ^^^^^^^^^^^^^^^^^^^

    0.0.21 (2020-11-26) ^^^^^^^^^^^^^^^^^^^

    • Allow to use custom Cursor subclasses #​374

    • Fill Connection class with actual client version #​388

    • Fix legacy aiter methods #​403

    • Fix & update docs #​418 #​437

    • Ignore pyenv's .python-version file #​424

    • Replace asyncio.streams.IncompleteReadError with asyncio.IncompleteReadError #​460 #​454

    • Add support for SQLAlchemy default parameters #​455 #​466

    • Update dependencies #​485

    • Support Python 3.7 & 3.8 #​493

    0.0.20 (2018-12-19) ^^^^^^^^^^^^^^^^^^^

    • Fixed connect_timeout #​360

    • Fixed support for SQLA executemany #​324

    • Fix the python 3.7 compatibility #​357

    • Fixed reuse connections when StreamReader has an exception #​339

    • Fixes warning when inserting binary strings #​326

    0.0.19 (2018-07-12) ^^^^^^^^^^^^^^^^^^^

    • See v0.0.18

    0.0.18 (2018-07-09) ^^^^^^^^^^^^^^^^^^^

    • Updated to support latest PyMySQL changes.

    • aiomysql now sends client connection info.

    • MySQL8+ Support including sha256_password and cached_sha2_password authentication plugins.

    • Default max packet length sent to the server is no longer 1.

    • Fixes issue where cursor.nextset can hang on query sets that raise errors.

    0.0.17 (2018-07-06) ^^^^^^^^^^^^^^^^^^^

    • Pinned version of PyMySQL

    0.0.16 (2018-06-03) ^^^^^^^^^^^^^^^^^^^

    • Added ability to execute precompiled sqlalchemy queries #​294 (Thanks @​vlanse)

    0.0.15 (2018-05-20) ^^^^^^^^^^^^^^^^^^^

    • Fixed handling of user-defined types for sqlalchemy #​290

    • Fix KeyError when server reports unknown collation #​289

    0.0.14 (2018-04-22) ^^^^^^^^^^^^^^^^^^^

    • Fixed SSL connection finalization #​282

    0.0.13 (2018-04-19) ^^^^^^^^^^^^^^^^^^^

    0.0.12 (2018-01-18) ^^^^^^^^^^^^^^^^^^^

    • Fixed support for SQLAlchemy 1.2.0

    • Fixed argument for cursor.execute in sa engine #​239 (Thanks @​NotSoSuper)

    0.0.11 (2017-12-06) ^^^^^^^^^^^^^^^^^^^

    • Fixed README formatting on pypi

    0.0.10 (2017-12-06) ^^^^^^^^^^^^^^^^^^^

    0.0.9 (2016-09-14) ^^^^^^^^^^^^^^^^^^

    0.0.8 (2016-08-24) ^^^^^^^^^^^^^^^^^^

    0.0.7 (2016-01-27) ^^^^^^^^^^^^^^^^^^

    • Fix for multiple results issue, ported from pymysql #​52

    • Fixed useless warning with no_delay option #​55

    • Added async/await support for Engine, SAConnection, Transaction #​57

    • pool.release returns future so we can wait on it in aexit #​60

    • Update to PyMySQL 0.6.7

    0.0.6 (2015-12-11) ^^^^^^^^^^^^^^^^^^

    0.0.5 (2015-10-28) ^^^^^^^^^^^^^^^^^^

    • no_delay option is deprecated and True by default

    • Add Cursor.mogrify() method

    • Support for "LOAD LOCAL INFILE" query.

    • Check connection inside pool, in case of timeout drop it, fixes #​25

    • Add support of python 3.5 features to pool, connection and cursor

    0.0.4 (2015-05-23) ^^^^^^^^^^^^^^^^^^

    • Allow to call connection.wait_closed twice.

    • Fixed sqlalchemy 1.0.0 support.

    • Fix #​11: Rename Connection.wait_closed() to .ensure_closed()

    • Raise ResourceWarning on non-closed Connection

    • Rename Connection.connect to _connect

    0.0.3 (2015-03-10) ^^^^^^^^^^^^^^^^^^

    • Added support for PyMySQL up to 0.6.6.

    • Ported improvements from PyMySQL.

    • Added basic documentation.

    • Fixed and added more examples.

    0.0.2 (2015-02-17) ^^^^^^^^^^^^^^^^^^

    • Added MANIFEST.in.

    0.0.1 (2015-02-17) ^^^^^^^^^^^^^^^^^^

    • Initial release.

    • Implemented plain connections: connect, Connection, Cursor.

    • Implemented database pools.

    • Ported sqlalchemy optional support.


    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box

    This PR has been generated by Mend Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Update dependency python-dotenv to ^0.21.0

    Update dependency python-dotenv to ^0.21.0

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | python-dotenv | ^0.19.2 -> ^0.21.0 | age | adoption | passing | confidence |


    Release Notes

    theskumar/python-dotenv

    v0.21.0

    Compare Source

    Added
    Fixed

    v0.20.0

    Compare Source

    Added
    • Add encoding (Optional[str]) parameter to get_key, set_key and unset_key. (#​379 by [@​bbc2])
    Fixed

    Configuration

    📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box

    This PR has been generated by Mend Renovate. View repository job log here.

    opened by renovate[bot] 2
Releases(v0.5.1)
Owner
Telath
Code and themes for telath.com
Telath
It's a Discord bot to control your PC using your Discord Channel or using Reco: Discord PC Remote Controller App.

Reco PC Server Reco PC Server is a cross platform PC Controller Discord Bot which is a modified and improved version of Chimera for Reco-Discord PC Re

Arvinth Krishna 12 Aug 31, 2022
A small and fun Discord Bot that is written in Python and discord-interactions (with discord.py)

Articuno (discord-interactions) A small and fun Discord Bot that is written in Python and discord-interactions (with discord.py) Get started If you wa

Blue 8 Dec 26, 2022
Discord bot script for sending multiple media files to a discord channel according to discord limitations.

Discord Bulk Image Sending Bot Send bulk images to Discord channel. This is a bot script that will allow you to send multiple images to Discord channe

Nikola Arbov 1 Jan 13, 2022
An Open-Source Discord bot created to provide basic functionality which should be in every discord guild. We use this same bot with additional configurations for our guilds.

A Discord bot completely written to be taken from the source and built according to your own custom needs. This bot supports some core features and is

Tesseract Coding 14 Jan 11, 2022
Discord ToolBox is a discord bot developed by DJD320 created for the purpose of having some convenient tools in the form of a single bot.

Discord ToolBox Discord ToolBox is a discord bot developed by DJD320 created for the purpose of having some convenient tools in the form of a single b

null 3 Aug 7, 2021
Linky bot, A open-source discord bot that allows you to add links to ur website, youtube url, etc for the people all around discord to see!

LinkyBot Linky bot, An open-source discord bot that allows you to add links to ur website, youtube url, etc for the people all around discord to see!

AlexyDaCoder 1 Sep 20, 2022
Image-Bot-Discord - This Is a discord bot that shows the specific image you search from Google

Advanced Discord.py Image Bot CREDITS Made by RLX and Mathiscool README by Milrato Installation Guide in .env Adjust the TOKEN python main.py to start

RLX 3 Jan 16, 2022
Discord.py-Bot-Template - Discord Bot Template with Python 3.x

Discord Bot Template with Python 3.x This is a template for creating a custom Di

Keagan Landfried 3 Jul 17, 2022
Example-bot-discord - Example bot discord xD

example-python-bot-discord Clone this repository Grab a token on Discord's devel

Amitminer 1 Mar 14, 2022
YouTube-Discord-Bot - Discord Bot to Search YouTube

YouTube Bot Info YouTube Bot is a discord bot where you can search for anything

Riceblades11 10 Mar 5, 2022
SongLink Discord Bot - Discord bot to share music links easily

SongLink_Discord_Bot Discord bot to share music links easily. Take a link from y

Edgar Lefevre 4 Feb 18, 2022
Kevin L. 3 Jul 14, 2022
VoiceMaster-Discord-Bot - Fork from original Discord bot with max channel limit, staff role and more

VoiceMaster VoiceMaster is a discord bot created to change the way servers work,

null 2 Feb 28, 2022
A discord Server Bot made with Python, This bot helps people feel better by inspiring them with motivational quotes or by responding with a great message, also the users of the server can create custom messages by telling the bot with Commands.

A discord Server Bot made with Python, This bot helps people feel better by inspiring them with motivational quotes or by responding with a great message, also the users of the server can create custom messages by telling the bot with Commands.

Aran 1 Oct 13, 2021
Aqui está disponível GRATUITAMENTE, um bot de discord feito em python, saiba que, terá que criar seu bot como aplicação, e utilizar seu próprio token, e lembrando, é um bot básico, não se utiliza Cogs nem slash commands nele!

BotDiscordPython Aqui está disponível GRATUITAMENTE, um bot de discord feito em python, saiba que, terá que criar seu bot como aplicação, e utilizar s

Matheus Muguet 4 Feb 5, 2022
DeKrypt 24 Sep 21, 2022
Automate TikTok follower bot, like bot, share bot, view bot and more using selenium

Zefoy TikTok Automator Automate TikTok follower bot, like bot, share bot, view bot and more using selenium. Click here to report bugs. Usage Download

null 555 Dec 30, 2022
A Discord BOT that uses Google Sheets for storing the roles and permissions of a discord server.

Discord Role Manager Bot Role Manager is a discord BOT that utilizes Google Sheets for the organization of a server's hierarchy and permissions. Detai

Dion Rigatos 17 Oct 13, 2022
MusicBot is the original Discord music bot written for Python 3.5+, using the discord.py library

The original MusicBot for Discord (formerly SexualRhinoceros/MusicBot)

Just Some Bots 2.9k Jan 2, 2023