Package: jmespath-community
JMESPath CommunityJMESPath (pronounced “james path”) allows you to declaratively specify how to
extract elements from a JSON document.JMESPath Community is an unofficial community effort to promote improvements
and updates to the JMESPath language specification.For example, given this document:{"foo": {"bar": "baz"}}The jmespath expressionfoo.barwill return “baz”.JMESPath also supports:Referencing elements in a list.  Given the data:{"foo": {"bar": ["one", "two"]}}The expression:foo.bar[0]will return “one”.
You can also reference all the items in a list using the*syntax:{"foo": {"bar": [{"name": "one"}, {"name": "two"}]}}The expression:foo.bar[*].namewill return [“one”, “two”].
Negative indexing is also supported (-1 refers to the last element
in the list).  Given the data above, the expressionfoo.bar[-1].namewill return “two”.The*can also be used for hash types:{"foo": {"bar": {"name": "one"}, "baz": {"name": "two"}}}The expression:foo.*.namewill return [“one”, “two”].InstallationYou can install JMESPath Community from PyPI with:pipinstalljmespath-communityAPIThejmespath.pylibrary has two functions
that operate on python data structures.  You can usesearchand give it the jmespath expression and the data:>>>importjmespath>>>path=jmespath.search('foo.bar',{'foo':{'bar':'baz'}})'baz'Similar to theremodule, you can use thecompilefunction
to compile the JMESPath expression and use this parsed expression
to perform repeated searches:>>>importjmespath>>>expression=jmespath.compile('foo.bar')>>>expression.search({'foo':{'bar':'baz'}})'baz'>>>expression.search({'foo':{'bar':'other'}})'other'This is useful if you’re going to use the same jmespath expression to
search multiple documents.  This avoids having to reparse the
JMESPath expression each time you search a new document.OptionsYou can provide an instance ofjmespath.Optionsto control how
a JMESPath expression is evaluated.  The most common scenario for
using anOptionsinstance is if you want to have ordered output
of your dict keys.  To do this you can use either of these options:>>>importjmespath>>>jmespath.search('{a: a, b: b}',...mydata,...jmespath.Options(dict_cls=collections.OrderedDict))>>>importjmespath>>>parsed=jmespath.compile('{a: a, b: b}')>>>parsed.search(mydata,...jmespath.Options(dict_cls=collections.OrderedDict))JMESPath used to support a special casejson-valuesyntax to represent a
JSON string literal, but this was being deprecated followingJEP-12and itsraw-stringliteral syntax.>>>importjmespath>>>jmespath.search("`foo`"',{})jmespath.exceptions.LexerError:Badjmespathexpression:Badtoken%s`foo`:`foo`^While JMESPath Community now fully deprecates this legacy syntax of providing
a JSON literal string with elided double quotes, you can still opt-in to parse
legacy syntax, by specifying theenable_legacy_literalsflag to theOptionsobject.>>>importjmespath>>>jmespath.search("`foo`"',...mydata,...jmespath.Options(enable_legacy_literals=True))'foo'>>>importjmespath>>>parsed=jmespath.compile("`foo`",...jmespath.Options(enable_legacy_literals=True))>>>parsed.search(mydata)'foo'Custom FunctionsThe JMESPath language has numerousbuilt-in functions, but it is
also possible to add your own custom functions.  Keep in mind that
custom function support in jmespath.py is experimental and the API may
change based on feedback.If you have a custom function that you’ve found useful, consider submitting
it to jmespath.site and propose that it be added to the JMESPath language.You can submit proposalshere.To create custom functions:Create a subclass ofjmespath.functions.Functions.Create a method with the name_func_<your function name>.Apply thejmespath.functions.signaturedecorator that indicates
the expected types of the function arguments.Provide an instance of your subclass in ajmespath.Optionsobject.Below are a few examples:importjmespathfromjmespathimportfunctions# 1. Create a subclass of functions.Functions.#    The function.Functions base class has logic#    that introspects all of its methods and automatically#    registers your custom functions in its function table.classCustomFunctions(functions.Functions):# 2 and 3.  Create a function that starts with _func_# and decorate it with @signature which indicates its# expected types.# In this example, we're creating a jmespath function# called "unique_letters" that accepts a single argument# with an expected type "string".@functions.signature({'types':['string']})def_func_unique_letters(self,s):# Given a string s, return a sorted# string of unique letters: 'ccbbadd' ->  'abcd'return''.join(sorted(set(s)))# Here's another example.  This is creating# a jmespath function called "my_add" that expects# two arguments, both of which should be of type number.@functions.signature({'types':['number']},{'types':['number']})def_func_my_add(self,x,y):returnx+y# 4. Provide an instance of your subclass in a Options object.options=jmespath.Options(custom_functions=CustomFunctions())# Provide this value to jmespath.search:# This will print 3print(jmespath.search('my_add(`1`, `2`)',{},options=options))# This will print "abcd"print(jmespath.search('foo.bar | unique_letters(@)',{'foo':{'bar':'ccbbadd'}},options=options))Again, if you come up with useful functions that you think make
sense in the JMESPath language (and make sense to implement in all
JMESPath libraries, not just python), please let us know atjmespath.site.SpecificationIf you’d like to learn more about the JMESPath language, you can check out
theJMESPath tutorial.  Also check
out theJMESPath examples pagefor
examples of more complex jmespath queries.The grammar is specified using ABNF, as described inRFC4234.
You can find the most up to dategrammar for JMESPath here.You can read the fullJMESPath specification here.TestingIn addition to the unit tests for the jmespath modules,
there is atests/compliancedirectory that contains
.json files with test cases.  This allows other implementations
to verify they are producing the correct output.  Each json
file is grouped by feature.DiscussJoin us on ourGitter channelif you want to chat or if you have any questions.