A Discord/Xenforo bot!
.env file from .env-local that contains relevant variables. (Mainly this will be the Discord webhook for testign.)poetry install to create virtualenv and install dependencies.make local-dev-up to start mock Xenforo database and MongoDB. This can be used when testing.make test to get fresh environments, run linters and tests.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| discord-webhook | ^0.14.0 -> ^0.15.0 | |
|
|
|
v0.15.0rate_limit_retry in webhook edit() functionedit function to specify fields that will be added or override existing fields in the webhook edit request. e.g. attachmentsπ 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| pytest-asyncio | ^0.17.1 -> ^0.18.0 | |
|
|
|
v0.18.2=================
#​295 <https://github.com/pytest-dev/pytest-asyncio/issues/295>_#​302 <https://github.com/pytest-dev/pytest-asyncio/issues/302>_v0.18.1
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.
@​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.
asyncio and trio.To install pytest-asyncio, simply:
$ pip install pytest-asyncio
This is enough for pytest to pick up pytest-asyncio.
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
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 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.
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.
event_loopCreates 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.
@​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_portFinds and yields a single unused TCP port on the localhost interface. Useful for binding temporary test servers.
unused_tcp_port_factoryA 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_factoryWork just like their TCP counterparts but return unused UDP ports.
Asynchronous fixtures are defined just like ordinary pytest fixtures,
except they should be decorated with @pytest_asyncio.fixture.
import pytest_asyncio
@​pytest_asyncio.fixture
async def async_gen_fixture():
await asyncio.sleep(0.1)
yield "a value"
@​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.
pytest.mark.asyncioMark 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.
Test classes subclassing the standard unittest library are not supported, users are recommended to use unitest.IsolatedAsyncioTestCase or an async framework such as asynctest.
event_loop fixture.
#β278typing-extensions on Python<3.8 only.
#β269asyncio marker when --asyncio-mode=auto is set.
#β258asyncio_mode type definition; it allows to support pytest
6.1+.
#β262unused_udp_port and unused_udp_port_factory fixtures
(similar to unused_tcp_port and unused_tcp_port_factory
counterparts.
#β99KeyboardInterrupt during async fixture setup
phase
#β219unused_tcp_port_factory fixture scope to 'session'.
#β163pytest.skip support.
#β126pytest-asyncio integrates with
Hypothesis to support @given
on async test functions using asyncio.
#β102event_loop_process_pool fixture and
pytest.mark.asyncio_process_pool marker (see
https://bugs.python.org/issue34075 for deprecation and removal
details)pytestmark now works on both module and class level.forbid_global_loop parameter has been removed.asyncio.async() has been fixed.
#β51event_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.
#β30pytest_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.
#β29event_loop fixtures simpler to override by closing them in
the plugin, instead of directly in the fixture.
#β21forbid_global_loop parameter.
#β21async/await syntax.
#β17unused_tcp_port_factory fixture.
#β10Initial release.
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
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.
@​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.
asyncio and trio.To install pytest-asyncio, simply:
$ pip install pytest-asyncio
This is enough for pytest to pick up pytest-asyncio.
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
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 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.
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.
event_loopCreates 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.
@​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_portFinds and yields a single unused TCP port on the localhost interface. Useful for binding temporary test servers.
unused_tcp_port_factoryA 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_factoryWork just like their TCP counterparts but return unused UDP ports.
Asynchronous fixtures are defined just like ordinary pytest fixtures,
except they should be decorated with @pytest_asyncio.fixture.
import pytest_asyncio
@​pytest_asyncio.fixture
async def async_gen_fixture():
await asyncio.sleep(0.1)
yield "a value"
@​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.
pytest.mark.asyncioMark 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.
Test classes subclassing the standard unittest library are not supported, users are recommended to use unitest.IsolatedAsyncioTestCase or an async framework such as asynctest.
event_loop fixture.
#β278typing-extensions on Python<3.8 only.
#β269asyncio marker when --asyncio-mode=auto is set.
#β258asyncio_mode type definition; it allows to support pytest
6.1+.
#β262unused_udp_port and unused_udp_port_factory fixtures
(similar to unused_tcp_port and unused_tcp_port_factory
counterparts.
#β99KeyboardInterrupt during async fixture setup
phase
#β219unused_tcp_port_factory fixture scope to 'session'.
#β163pytest.skip support.
#β126pytest-asyncio integrates with
Hypothesis to support @given
on async test functions using asyncio.
#β102event_loop_process_pool fixture and
pytest.mark.asyncio_process_pool marker (see
https://bugs.python.org/issue34075 for deprecation and removal
details)pytestmark now works on both module and class level.forbid_global_loop parameter has been removed.asyncio.async() has been fixed.
#β51event_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.
#β30pytest_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.
#β29event_loop fixtures simpler to override by closing them in
the plugin, instead of directly in the fixture.
#β21forbid_global_loop parameter.
#β21async/await syntax.
#β17unused_tcp_port_factory fixture.
#β10Initial release.
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
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.
@​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.
asyncio and trio.To install pytest-asyncio, simply:
$ pip install pytest-asyncio
This is enough for pytest to pick up pytest-asyncio.
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
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 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.
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.
event_loopCreates 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.
@​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_portFinds and yields a single unused TCP port on the localhost interface. Useful for binding temporary test servers.
unused_tcp_port_factoryA 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_factoryWork just like their TCP counterparts but return unused UDP ports.
Asynchronous fixtures are defined just like ordinary pytest fixtures,
except they should be decorated with @pytest_asyncio.fixture.
import pytest_asyncio
@​pytest_asyncio.fixture
async def async_gen_fixture():
await asyncio.sleep(0.1)
yield "a value"
@​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.
pytest.mark.asyncioMark 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.
Test classes subclassing the standard unittest library are not supported, users are recommended to use unitest.IsolatedAsyncioTestCase or an async framework such as asynctest.
typing-extensions on Python<3.8 only.
#β269asyncio marker when --asyncio-mode=auto is set.
#β258asyncio_mode type definition; it allows to support pytest
6.1+.
#β262unused_udp_port and unused_udp_port_factory fixtures
(similar to unused_tcp_port and unused_tcp_port_factory
counterparts.
#β99KeyboardInterrupt during async fixture setup
phase
#β219unused_tcp_port_factory fixture scope to 'session'.
#β163pytest.skip support.
#β126pytest-asyncio integrates with
Hypothesis to support @given
on async test functions using asyncio.
#β102event_loop_process_pool fixture and
pytest.mark.asyncio_process_pool marker (see
https://bugs.python.org/issue34075 for deprecation and removal
details)pytestmark now works on both module and class level.forbid_global_loop parameter has been removed.asyncio.async() has been fixed.
#β51event_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.
#β30pytest_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.
#β29event_loop fixtures simpler to override by closing them in
the plugin, instead of directly in the fixture.
#β21forbid_global_loop parameter.
#β21async/await syntax.
#β17unused_tcp_port_factory fixture.
#β10Initial release.
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.
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| pytest (source, changelog) | ^6.2.5 -> ^7.0.0 | |
|
|
|
v7.0.1importlib.readers in Python 3.9.pythonpath plugin was renamed to python_path. This avoids a conflict with the pytest-pythonpath plugin.:: in the parametrize portion.~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(Please see the full set of changes for this release also in the 7.0.0rc1 notes below)
#β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.
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).#β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"}.
#β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.HookRecorderThese 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"}:
path property of _pytest.code.Code returns Path instead of py.path.local.path property of _pytest.code.TracebackEntry returns Path instead of py.path.local.There was no deprecation period for this change (sorry!).
#β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:
--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.
#β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.
#β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.
#β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.
plugin-list{.interpreted-text role="ref"}. The list is updated on a periodic schedule.pytest.approx{.interpreted-text role="func"} documentation.--pdbcls more accurately reflects the option's behavior.confcutdir being a configuration option: it can only be set through the --confcutdir command-line option.non-python tests{.interpreted-text role="ref"} are now correctly documented in the reference docs. They were undocumented previously.setuptools_scm 6.x to use SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST for more robust release tooling._pytest.code.getfslineno() function returns Path instead of py.path.local._pytest.python.path_matches_patterns() function takes Path instead of py.path.local._pytest._code.Traceback.cut() function accepts any os.PathLike[str], not just py.path.local.python.PyObjMixin inherit from nodes.Node to carry over typing information.pytest.skip{.interpreted-text role="func"} is used at module level without passing [allow_module_level=True]{.title-ref}.regendoc opts out of TOX_ENV cachedir selection to ensure independent example test runs.CallSpec2._arg2scopenum attribute has been removed after an internal refactoring.pytest_assertion_pass{.interpreted-text role="hook"} is no longer considered experimental and
future changes to it will be considered more carefully.π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| actions/upload-artifact | action | major | v2 -> v3 |
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| actions/setup-python | action | major | v2 -> v3 |
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| httpx (changelog) | ^0.21.3 -> ^0.22.0 | |
|
|
|
v0.22.0socksio package. (#β2034)π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| fastapi | ^0.72.0 -> ^0.73.0 | |
|
|
|
v0.73.0UploadFile parameters without explicit File(). PR #β4469 by @βtiangolo. New docs: Request Files - File Parameters with UploadFile.Query, Cookie, Header, and Path parameters. PR #β3144 by @βastraldawn. New docs: Query Parameters and String Validations - Exclude from OpenAPI.jsonable_encoder. PR #β2061 by @βviveksunder.
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| python | final | patch | 3.10.1 -> 3.10.2 |
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| actions/checkout | action | major | v1 -> v2 |
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| fastapi | ^0.71.0 -> ^0.72.0 | |
|
|
|
v0.72.0docs/help-fastapi.md. PR #β3847 by @βjaystone776.docs/ko/docs/index.md. PR #β4195 by @βkty4119.docs/pl/docs/index.md. PR #β4245 by @βMicroPanda123.docs\tutorial\path-operation-configuration.md. PR #β3312 by @βjaystone776.content.tabs.link. PR #β4399 by @βtiangolo.π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
/metadata and /metadata/check/ip endpoints.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| discord-webhook | ^0.15.0 -> ^0.17.0 | |
|
|
|
v0.17.0ColourNotInRangeException was renamed to ColorNotInRangeExceptionv0.16.3v0.16.2v0.16.1v0.16.0π 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.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| docker/metadata-action | action | major | v3 -> v4 |
π 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.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| motor | ^2.5.1 -> ^3.0.0 | |
|
|
|
v3.1.1: Motor 3.1.1Release notes: https://www.mongodb.com/community/forums/t/mongodb-motor-3-1-1-released/195738
v3.0.0: Motor 3.0.0Release notes: https://www.mongodb.com/community/forums/t/mongodb-motor-3-0-0-released/160708
π 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.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| github/codeql-action | action | major | v1 -> v2 |
π 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.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| aiomysql | ^0.0.22 -> ^0.1.0 | |
|
|
|
v0.1.10.1.1 (2022-05-08) ^^^^^^^^^^^^^^^^^^
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
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) ^^^^^^^^^^^^^^^^^^^
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) ^^^^^^^^^^^^^^^^^^^
0.0.16 (2018-06-03) ^^^^^^^^^^^^^^^^^^^
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) ^^^^^^^^^^^^^^^^^^^
0.0.13 (2018-04-19) ^^^^^^^^^^^^^^^^^^^
Added SSL support #β280 (Thanks @βterrycain)
Fixed all in aiomysql/init #β270 (Thanks @βmatianjun1)
Added docker fixtures #β275 (Thanks @βterrycain)
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) ^^^^^^^^^^^^^^^^^^^
0.0.10 (2017-12-06) ^^^^^^^^^^^^^^^^^^^
Updated regular expressions to be compatible with pymysql #β167 (Thanks @βAlexLisovoy)
Added connection recycling in the pool #β216
0.0.9 (2016-09-14) ^^^^^^^^^^^^^^^^^^
Fixed AttributeError in _request_authentication function #β104 (Thanks @βttlttl)
Fixed legacy auth #β105
uvloop added to test suite #β106
Fixed bug with unicode in json field #β107 (Thanks @βmethane)
0.0.8 (2016-08-24) ^^^^^^^^^^^^^^^^^^
Default min pool size reduced to 1 #β80 (Thanks @βDrizzt1991)
Update to PyMySQL 0.7.5 #β89
Fixed connection cancellation in process of executing a query #β79 (Thanks @βDrizzt1991)
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) ^^^^^^^^^^^^^^^^^^
Fixed bug with SA rollback (Thanks @βkhlyestovillarion!)
Fixed issue with default no_delay option (Thanks @βkhlyestovillarion!)
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) ^^^^^^^^^^^^^^^^^^
0.0.1 (2015-02-17) ^^^^^^^^^^^^^^^^^^
Initial release.
Implemented plain connections: connect, Connection, Cursor.
Implemented database pools.
Ported sqlalchemy optional support.
v0.1.00.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
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) ^^^^^^^^^^^^^^^^^^^
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) ^^^^^^^^^^^^^^^^^^^
0.0.16 (2018-06-03) ^^^^^^^^^^^^^^^^^^^
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) ^^^^^^^^^^^^^^^^^^^
0.0.13 (2018-04-19) ^^^^^^^^^^^^^^^^^^^
Added SSL support #β280 (Thanks @βterrycain)
Fixed all in aiomysql/init #β270 (Thanks @βmatianjun1)
Added docker fixtures #β275 (Thanks @βterrycain)
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) ^^^^^^^^^^^^^^^^^^^
0.0.10 (2017-12-06) ^^^^^^^^^^^^^^^^^^^
Updated regular expressions to be compatible with pymysql #β167 (Thanks @βAlexLisovoy)
Added connection recycling in the pool #β216
0.0.9 (2016-09-14) ^^^^^^^^^^^^^^^^^^
Fixed AttributeError in _request_authentication function #β104 (Thanks @βttlttl)
Fixed legacy auth #β105
uvloop added to test suite #β106
Fixed bug with unicode in json field #β107 (Thanks @βmethane)
0.0.8 (2016-08-24) ^^^^^^^^^^^^^^^^^^
Default min pool size reduced to 1 #β80 (Thanks @βDrizzt1991)
Update to PyMySQL 0.7.5 #β89
Fixed connection cancellation in process of executing a query #β79 (Thanks @βDrizzt1991)
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) ^^^^^^^^^^^^^^^^^^
Fixed bug with SA rollback (Thanks @βkhlyestovillarion!)
Fixed issue with default no_delay option (Thanks @βkhlyestovillarion!)
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) ^^^^^^^^^^^^^^^^^^
0.0.1 (2015-02-17) ^^^^^^^^^^^^^^^^^^
Initial release.
Implemented plain connections: connect, Connection, Cursor.
Implemented database pools.
Ported sqlalchemy optional support.
π 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.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| python-dotenv | ^0.19.2 -> ^0.21.0 | |
|
|
|
v0.21.0load_dotenv function now returns False. (#β388 by @βlarsks)open instead of io.open. (#β389 by @βrabinadk1)parse_it to Related Projects by (#β410 by @βnaorlivne)v0.20.0entry_points parameter of setuptools.setup (#β376 by
[@βmgorny]).π 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.
This PR has been generated by Mend Renovate. View repository job log here.
Random-backlog-tweet - Pick a page from a sitemap at random and prep a tweet button for it
Discord Bot that leverages the idea of nested containers using podman, runs untrusted user input, executes Quantum Circuits, allows users to refer to the Qiskit Documentation, and provides the abilit
Hsea Robot A modular Telegram Python bot running on python3 with a sqlalchemy database and an entirely themed persona to make Cutiepii suitable for An
GitHub User Search Created using Python3 and git_api, coded by JBYT27. About This is a project I decided to make for Kajam, but I decided to choose a
Telegram Movie Bot Features Auto Filter Manuel Filter IMDB Admin Commands Broadcast Index IMDB search Inline Search Random pics ids and User info Stat
Discord-Servercount With this script you can check the amount of servers you are in, along with statistics of how many servers you are owner in and in
Telegram Bot Repo Capable of fetching the following Info via Anilist API inspired from AniFluid and Nepgear Anime Airing Manga Character Scheduled Top
Lyra - rapidly and painlessly deploy Minecraft servers from Discord Lyra lets you deploy Minecraft server instances via Docker with control through a
World_weather_analysis Overview Using multiple API sources, create an app that allows users to filter through random locations based on their temperat
Jesse Jesse is an advanced crypto trading framework which aims to simplify researching and defining trading strategies. Why Jesse? In short, Jesse is
String-session-Bot Telegram Bot to generate Pyrogram and Telethon String Session. A star β from you means a lot to us! Usage Deploy to Heroku Tap on a
π Morpheus is a telegram bot that helps to simplify the process of making custom telegram stickers. As you may know, Telegram's official Sti
ππ π¦π©π ππ₯ π¦π₯πππ½Β° β’οΈ π±π° πππ π©π¨π₯ππ¦ Auto Filter IMDB Admin Commands Broadcast Index IMDB Search Inline Search Random Pics Ids & User I
Spacebot - Discord Bot Music, Moderation, Fun, Utilities, Games and Fully Configurable. Overview β’ Contributing β’ Self hosting β’ Documentation (not re
psse-decrypt Decrypt PSSE layer of PSM Games (on PC) Works on Unity and PSM games, and meets all requirements of: https://github.com/vita-nuova/bounti
telathbot A Discord/Xenforo bot! Pre-requisites pyenv (via installer) poetry Docker (with Go version of docker compose enabled) Local development Crea
pcs-toolbox Prisma Cloud utility scripts, and a Python SDK for Prisma Cloud APIs. Table of Contents Support Setup Configuration Script Usage CSPM Scri
TG_Bot A modular telegram Python bot running on python3 with an sqlalchemy database. Originally a simple group management bot with multiple admin feat
GoFile-Bot A telegram media to gofile bot Made with Python3 (C) @FayasNoushad Copyright permission under MIT License License - https://github.com/Fay
Pycordia β οΈ Note! As of now, this package is under early development so functionalities are bound to change drastically. We don't recommend you curren
0 Dec 01, 2022
23 Oct 18, 2022
1 Dec 29, 2021
4 May 11, 2022
1 Dec 03, 2021
1 Feb 12, 2022
2 Apr 01, 2022
1 Dec 23, 2021
2 Sep 16, 2022
4.4k Jan 09, 2023
1 Dec 14, 2022
13 Jun 21, 2022
41 Dec 10, 2022
32 Oct 11, 2022
34 Dec 15, 2022
1 Nov 02, 2021
37 Nov 14, 2022
24 Jan 01, 2023