Upgraded to Gremlin 3.5.1#196
Merged
Merged
Conversation
Closed
mergify Bot
added a commit
that referenced
this pull request
Apr 13, 2026
…in /e2e-python [skip ci] Updates the requirements on [pytest-check](https://github.com/okken/pytest-check) to permit the latest version. Release notes *Sourced from [pytest-check's releases](https://github.com/okken/pytest-check/releases).* > 2.8.0 > ----- > > * Support Request [#122: Feature proposal: Capability to mark checks as xfail](https://redirect.github.com/okken/pytest-check/issues/122) > * Allow check helper functions, including `raises()`, to accept an `xfail` reason. A failing check can now produce an xfailed test result, while a passing check does not produce xpass unless the test is already marked with `@pytest.mark.xfail`. > * (docs) Document `xfail` support for check helper functions in the README. Changelog *Sourced from [pytest-check's changelog](https://github.com/okken/pytest-check/blob/main/changelog.md).* > [2.8.0] - 2026-Mar-22 > --------------------- > > ### Added > > * Support Request [#122: Feature proposal: Capability to mark checks as xfail](https://redirect.github.com/okken/pytest-check/issues/122) > * Allow check helper functions, including `raises()`, to accept an `xfail` reason. A failing check can now produce an xfailed test result, while a passing check does not produce xpass unless the test is already marked with `@pytest.mark.xfail`. > * (docs) Document `xfail` support for check helper functions in the README. > > [2.7.7] - 2026-Mar-20 > --------------------- > > ### Fixed > > * Allow CheckContextManager to catch any exception, not just AssertionError ([#198](https://redirect.github.com/okken/pytest-check/issues/198)). > Non-assertion exceptions (IndexError, KeyError, AttributeError, etc.) are now properly caught and reported as check failures. > > [2.7.6] - 2026-Mar-04 > --------------------- > > ### Fixed > > * (typing) Set comparison function types such that None is not allowed > > [2.7.5] - 2026-Mar-04 > --------------------- > > ### Changed > > * Passing `None` to comparison functions like `greater()`, `less()`, etc. used to raise an exception, which caused a test failure and stopped the test. > * That's unexpected with a check function. > * So now the check fails with a meaningful error message and continues with the rest of the test. > * (typing) Allow numpy floats with comparison functions to pass mypy. > > [2.7.4] - 2026-Mar-03 > --------------------- > > ### Fixed > > * (typing) Allow mixed `int`/`float` arguments in strict mypy for comparison helpers by adding `float` numeric overloads for `greater()`, `greater_equal()`, `less()`, and `less_equal()` in `check_functions.py`. > > [2.7.3] - 2026-Mar-02 > --------------------- > > ### Added > > * Add `__init__.pyi` stub file for IDE intellisense (e.g. VSCode) and static type checkers. > * Add PEP 561 `py.typed` marker so the package is recognized as typed. > * (examples) Add `test_example_mypy.py` to validate `import pytest_check as check` with mypy. > > ### Fixed > > * Ignore dist-packages in pseudo stack trace - Fixes [#196](https://redirect.github.com/okken/pytest-check/issues/196) - Thanks [`@siferati`](https://github.com/siferati) > * (typing) Resolve remaining mypy errors for `import pytest_check as check` usage; internal adjustments in `check_functions.py`. ... (truncated) Commits * [`c356b52`](okken/pytest-check@c356b52) Add xfail support for check helper functions * [`1c5add3`](okken/pytest-check@1c5add3) 2.7.7 * [`60d87c4`](okken/pytest-check@60d87c4) fix mypy issue * [`b8ee598`](okken/pytest-check@b8ee598) fix [#198](https://redirect.github.com/okken/pytest-check/issues/198): Allow CheckContextManager to catch any exception * [`108f139`](okken/pytest-check@108f139) mypy tweak * [`16e79c9`](okken/pytest-check@16e79c9) don't allow None for comparisons * [`4f6d1ea`](okken/pytest-check@4f6d1ea) type safe optional import * [`9b0ec93`](okken/pytest-check@9b0ec93) allow type checking with numpy floats and comparision functions * [`de69ee8`](okken/pytest-check@de69ee8) appropriate check fails with None passed to order comparisons * [`0ce3cdb`](okken/pytest-check@0ce3cdb) one more mypy fix * Additional commits viewable in [compare view](okken/pytest-check@2.5.0...2.8.0)
tae898
pushed a commit
to humemai/arcadedb-embedded-python
that referenced
this pull request
Jun 28, 2026
tae898
pushed a commit
to humemai/arcadedb-embedded-python
that referenced
this pull request
Jun 28, 2026
…in /e2e-python [skip ci] Updates the requirements on [pytest-check](https://github.com/okken/pytest-check) to permit the latest version. Release notes *Sourced from [pytest-check's releases](https://github.com/okken/pytest-check/releases).* > 2.8.0 > ----- > > * Support Request [ArcadeData#122: Feature proposal: Capability to mark checks as xfail](https://redirect.github.com/okken/pytest-check/issues/122) > * Allow check helper functions, including `raises()`, to accept an `xfail` reason. A failing check can now produce an xfailed test result, while a passing check does not produce xpass unless the test is already marked with `@pytest.mark.xfail`. > * (docs) Document `xfail` support for check helper functions in the README. Changelog *Sourced from [pytest-check's changelog](https://github.com/okken/pytest-check/blob/main/changelog.md).* > [2.8.0] - 2026-Mar-22 > --------------------- > > ### Added > > * Support Request [ArcadeData#122: Feature proposal: Capability to mark checks as xfail](https://redirect.github.com/okken/pytest-check/issues/122) > * Allow check helper functions, including `raises()`, to accept an `xfail` reason. A failing check can now produce an xfailed test result, while a passing check does not produce xpass unless the test is already marked with `@pytest.mark.xfail`. > * (docs) Document `xfail` support for check helper functions in the README. > > [2.7.7] - 2026-Mar-20 > --------------------- > > ### Fixed > > * Allow CheckContextManager to catch any exception, not just AssertionError ([ArcadeData#198](https://redirect.github.com/okken/pytest-check/issues/198)). > Non-assertion exceptions (IndexError, KeyError, AttributeError, etc.) are now properly caught and reported as check failures. > > [2.7.6] - 2026-Mar-04 > --------------------- > > ### Fixed > > * (typing) Set comparison function types such that None is not allowed > > [2.7.5] - 2026-Mar-04 > --------------------- > > ### Changed > > * Passing `None` to comparison functions like `greater()`, `less()`, etc. used to raise an exception, which caused a test failure and stopped the test. > * That's unexpected with a check function. > * So now the check fails with a meaningful error message and continues with the rest of the test. > * (typing) Allow numpy floats with comparison functions to pass mypy. > > [2.7.4] - 2026-Mar-03 > --------------------- > > ### Fixed > > * (typing) Allow mixed `int`/`float` arguments in strict mypy for comparison helpers by adding `float` numeric overloads for `greater()`, `greater_equal()`, `less()`, and `less_equal()` in `check_functions.py`. > > [2.7.3] - 2026-Mar-02 > --------------------- > > ### Added > > * Add `__init__.pyi` stub file for IDE intellisense (e.g. VSCode) and static type checkers. > * Add PEP 561 `py.typed` marker so the package is recognized as typed. > * (examples) Add `test_example_mypy.py` to validate `import pytest_check as check` with mypy. > > ### Fixed > > * Ignore dist-packages in pseudo stack trace - Fixes [ArcadeData#196](https://redirect.github.com/okken/pytest-check/issues/196) - Thanks [`@siferati`](https://github.com/siferati) > * (typing) Resolve remaining mypy errors for `import pytest_check as check` usage; internal adjustments in `check_functions.py`. ... (truncated) Commits * [`c356b52`](okken/pytest-check@c356b52) Add xfail support for check helper functions * [`1c5add3`](okken/pytest-check@1c5add3) 2.7.7 * [`60d87c4`](okken/pytest-check@60d87c4) fix mypy issue * [`b8ee598`](okken/pytest-check@b8ee598) fix [ArcadeData#198](https://redirect.github.com/okken/pytest-check/issues/198): Allow CheckContextManager to catch any exception * [`108f139`](okken/pytest-check@108f139) mypy tweak * [`16e79c9`](okken/pytest-check@16e79c9) don't allow None for comparisons * [`4f6d1ea`](okken/pytest-check@4f6d1ea) type safe optional import * [`9b0ec93`](okken/pytest-check@9b0ec93) allow type checking with numpy floats and comparision functions * [`de69ee8`](okken/pytest-check@de69ee8) appropriate check fails with None passed to order comparisons * [`0ce3cdb`](okken/pytest-check@0ce3cdb) one more mypy fix * Additional commits viewable in [compare view](okken/pytest-check@2.5.0...2.8.0)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
#195