pythonp1c2u/jsonschema-path #24Not a task: already works

Overly-tight pins on referencing

envgap__p1c2u__jsonschema-path-24

Original GitHub issue ↗Dated source checkout ↗Opened 2023-06-12

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: 9d3603309a5ff7920c12abbd76d308ea04350eb1
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

p1c2u/jsonschema-path #24 · read the original issue

Congratulations on the 0.2.0 release! :tada:



One concern noted [downstream](https://github.com/conda-forge/jsonschema-spec-feedstock/pull/6), the `^` specifiers act unpredictably, generating the following metadata in the wheel:



```

Requires-Dist: referencing (>=0.24.4,<0.25.0)

```



This may not have been the intended tightness of the spec, as the upstream package is already on `0.29.0`, and likely includes bug fixes, features, compatibility with its rust-based upstream, and performance benefits... and it seems unlikely that features would have been taken away already for such a relatively new package.



This is _not_ such a big issue with e.g. `jsonschema-specifications`, as the `^` works differently for non-`0.*` versions, and is probably closer to what is intended.



```

Requires-Dist: jsonschema-specifications (>=2023.3.4,<2024.0.0)

```

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

[]