Skip to content

[patch] use explicit import path for jsonpath_ng parse function - #2639

Merged
prveenkumr merged 1 commit into
masterfrom
cli-pk
Oct 8, 2026
Merged

prveenkumr merged 1 commit into
masterfrom
cli-pk

Conversation

@prveenkumr

Copy link
Copy Markdown
Contributor

basedpyright reports parse as not exported from jsonpath_ng.ext and requires importing from jsonpath_ng.ext.parser directly.

Tested:
$ python3 -c "from jsonpath_ng.ext.parser import parse;
expr = parse('$.items[*].metadata.name');
data = {'items': [{'metadata': {'name': 'test-crd'}}]};
print([m.value for m in expr.find(data)])"
['test-crd']

basedpyright reports `parse` as not exported from `jsonpath_ng.ext`
and requires importing from `jsonpath_ng.ext.parser` directly.

Tested:
  $ python3 -c "from jsonpath_ng.ext.parser import parse; \
      expr = parse('$.items[*].metadata.name'); \
      data = {'items': [{'metadata': {'name': 'test-crd'}}]}; \
      print([m.value for m in expr.find(data)])"
  ['test-crd']
@prveenkumr
prveenkumr requested a review from a team as a code owner October 8, 2026 15:35
@prveenkumr
prveenkumr merged commit a8567ae into master Oct 8, 2026
19 of 20 checks passed
@prveenkumr
prveenkumr deleted the cli-pk branch October 8, 2026 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants