Closed kloczek closed 1 year ago
I could be wrong, but I believe this is because this library has introduced a dependency on jsonschema>=4.3
but this is not pinned. There is a similar but different bug report over on the conda-forge feedstock which has made Jupyterlab unusable.
The source package has the minimum bound, but not yet the conda package. I'll update the conda recipe.
Sorry it's early here, I looked at that and completely missed it. 🤦♂️
I believe this should be resolved by #59 since the test failures imply (and the package list confirms) that the additional validators are not installed.
Hi @kloczek - could you please retry the rpm package build such that it includes jupyter_events >= 0.6.2
? I suspect this issue should be resolved. If not resolved, please provide the current output information you included in the original description.
I just tested 0.6.3 and unit still are failing
This implies that neither of the validators are installed (rfc3339-validator
and rfc3986-validator
) that are supposed to come with the jsonschema[format-nongpl]
dependency and which we added as explicit dependencies in 0.6.1
due to normalization issues with jsonschema <= 4.9
(where the optional dependency was named format_nongpl
).
As it is listed on top I'm using jsonschema
4.17.3.
Yes .. reported result is without installed rfc3339-validator
and rfc3986-validator
.
Should I add those modules to my build env? 🤔
As it is listed on top I'm using jsonschema 4.17.3.
Sorry, I missed that.
I don't know how these "build env" are seeded, but jupyter_events
depends on jsonschema[format-nongpl]
, so the equivalent of pip install "jsonschema[format-nongpl]"
is required (and is the mechanism by which those validators get installed).
Looks like 0.9.0 is OK now
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-jupyter-events-0.9.0-2.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-jupyter-events-0.9.0-2.fc35.x86_64/usr/lib/python3.8/site-packages
+ /usr/bin/pytest -ra -m 'not network'
============================= test session starts ==============================
platform linux -- Python 3.8.18, pytest-7.4.3, pluggy-1.3.0
rootdir: /home/tkloczko/rpmbuild/BUILD/jupyter_events-0.9.0
configfile: pyproject.toml
testpaths: tests/
plugins: anyio-4.0.0, asyncio-0.21.1, console-scripts-1.4.1
asyncio: mode=auto
collected 48 items
tests/test_cli.py ....... [ 14%]
tests/test_listeners.py ..... [ 25%]
tests/test_logger.py ............... [ 56%]
tests/test_modifiers.py ... [ 62%]
tests/test_schema.py ............... [ 93%]
tests/test_traits.py ... [100%]
============================= slowest 10 durations =============================
0.31s call tests/test_cli.py::test_cli_version[subprocess]
0.30s call tests/test_cli.py::test_cli_good_raw[subprocess]
0.30s call tests/test_cli.py::test_cli_invalid[subprocess]
0.30s call tests/test_cli.py::test_cli_good[subprocess]
0.29s call tests/test_cli.py::test_cli_malformed[subprocess]
0.29s call tests/test_cli.py::test_cli_missing[subprocess]
0.29s call tests/test_cli.py::test_cli_help[subprocess]
0.01s setup tests/test_listeners.py::test_listener_function
0.01s setup tests/test_listeners.py::test_listener_function_str_annotations
0.01s setup tests/test_listeners.py::test_remove_listener_function
============================== 48 passed in 2.44s ==============================
Thank you 👍 Closing.
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesHere is pytest output:
Here is list of installed modules in build env