pythonjupyter/jupyter_events #62Not a task: already works

pyyaml dependency

envgap__jupyter__jupyter_events-62

Original GitHub issue ↗Dated source checkout ↗Opened 2023-01-10

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 56cee1c6bb74196e20d04373af30a5475b9bdf00
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

jupyter/jupyter_events #62 · read the original issue

After completing the effort for #58 (via #59), this now exposes another issue with `kfp`'s capping policy.  In this case, they are capping `pyyaml<6` (with a floor `>=5.3`).  For applications using both Jupyter Server (which pulls in jupyter_events) and KFP, this generates an impossible resolution.



Similar to #59, is it possible to decrease the floor of `pyyaml` to `>=5.3`?



After doing so in my env (i.e., `pip install pyyaml==5.3`), both pytests and pre-commit succeed.



I'll go ahead and submit a PR and we can discuss it further.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]