Ausgabe der neuen DB Einträge
This commit is contained in:
parent
bad48e1627
commit
cfbbb9ee3d
2399 changed files with 843193 additions and 43 deletions
|
|
@ -0,0 +1,224 @@
|
|||
JMESPath
|
||||
========
|
||||
|
||||
|
||||
.. image:: https://badges.gitter.im/Join Chat.svg
|
||||
:target: https://gitter.im/jmespath/chat
|
||||
|
||||
|
||||
.. image:: https://travis-ci.org/jmespath/jmespath.py.svg?branch=develop
|
||||
:target: https://travis-ci.org/jmespath/jmespath.py
|
||||
|
||||
|
||||
.. image:: https://codecov.io/github/jmespath/jmespath.py/coverage.svg?branch=develop
|
||||
:target: https://codecov.io/github/jmespath/jmespath.py?branch=develop
|
||||
|
||||
|
||||
JMESPath (pronounced "james path") allows you to declaratively specify how to
|
||||
extract elements from a JSON document.
|
||||
|
||||
For example, given this document::
|
||||
|
||||
{"foo": {"bar": "baz"}}
|
||||
|
||||
The jmespath expression ``foo.bar`` will 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[*].name`` will return ["one", "two"].
|
||||
Negative indexing is also supported (-1 refers to the last element
|
||||
in the list). Given the data above, the expression
|
||||
``foo.bar[-1].name`` will return "two".
|
||||
|
||||
The ``*`` can also be used for hash types::
|
||||
|
||||
{"foo": {"bar": {"name": "one"}, "baz": {"name": "two"}}}
|
||||
|
||||
The expression: ``foo.*.name`` will return ["one", "two"].
|
||||
|
||||
|
||||
Installation
|
||||
============
|
||||
|
||||
You can install JMESPath from pypi with:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
pip install jmespath
|
||||
|
||||
|
||||
API
|
||||
===
|
||||
|
||||
The ``jmespath.py`` library has two functions
|
||||
that operate on python data structures. You can use ``search``
|
||||
and give it the jmespath expression and the data:
|
||||
|
||||
.. code:: python
|
||||
|
||||
>>> import jmespath
|
||||
>>> path = jmespath.search('foo.bar', {'foo': {'bar': 'baz'}})
|
||||
'baz'
|
||||
|
||||
Similar to the ``re`` module, you can use the ``compile`` function
|
||||
to compile the JMESPath expression and use this parsed expression
|
||||
to perform repeated searches:
|
||||
|
||||
.. code:: python
|
||||
|
||||
>>> import jmespath
|
||||
>>> 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.
|
||||
|
||||
Options
|
||||
-------
|
||||
|
||||
You can provide an instance of ``jmespath.Options`` to control how
|
||||
a JMESPath expression is evaluated. The most common scenario for
|
||||
using an ``Options`` instance is if you want to have ordered output
|
||||
of your dict keys. To do this you can use either of these options:
|
||||
|
||||
.. code:: python
|
||||
|
||||
>>> import jmespath
|
||||
>>> jmespath.search('{a: a, b: b}',
|
||||
... mydata,
|
||||
... jmespath.Options(dict_cls=collections.OrderedDict))
|
||||
|
||||
|
||||
>>> import jmespath
|
||||
>>> parsed = jmespath.compile('{a: a, b: b}')
|
||||
>>> parsed.search(mydata,
|
||||
... jmespath.Options(dict_cls=collections.OrderedDict))
|
||||
|
||||
|
||||
Custom Functions
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
The JMESPath language has numerous
|
||||
`built-in functions
|
||||
<http://jmespath.org/specification.html#built-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 proposals
|
||||
`here <https://github.com/jmespath/jmespath.site/issues>`__.
|
||||
|
||||
To create custom functions:
|
||||
|
||||
* Create a subclass of ``jmespath.functions.Functions``.
|
||||
* Create a method with the name ``_func_<your function name>``.
|
||||
* Apply the ``jmespath.functions.signature`` decorator that indicates
|
||||
the expected types of the function arguments.
|
||||
* Provide an instance of your subclass in a ``jmespath.Options`` object.
|
||||
|
||||
Below are a few examples:
|
||||
|
||||
.. code:: python
|
||||
|
||||
import jmespath
|
||||
from jmespath import functions
|
||||
|
||||
# 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.
|
||||
class CustomFunctions(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):
|
||||
return x + 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 3
|
||||
print(
|
||||
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 at
|
||||
`jmespath.site <https://github.com/jmespath/jmespath.site/issues>`__.
|
||||
|
||||
|
||||
Specification
|
||||
=============
|
||||
|
||||
If you'd like to learn more about the JMESPath language, you can check out
|
||||
the `JMESPath tutorial <http://jmespath.org/tutorial.html>`__. Also check
|
||||
out the `JMESPath examples page <http://jmespath.org/examples.html>`__ for
|
||||
examples of more complex jmespath queries.
|
||||
|
||||
The grammar is specified using ABNF, as described in
|
||||
`RFC4234 <http://www.ietf.org/rfc/rfc4234.txt>`_.
|
||||
You can find the most up to date
|
||||
`grammar for JMESPath here <http://jmespath.org/specification.html#grammar>`__.
|
||||
|
||||
You can read the full
|
||||
`JMESPath specification here <http://jmespath.org/specification.html>`__.
|
||||
|
||||
|
||||
Testing
|
||||
=======
|
||||
|
||||
In addition to the unit tests for the jmespath modules,
|
||||
there is a ``tests/compliance`` directory 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.
|
||||
|
||||
|
||||
Discuss
|
||||
=======
|
||||
|
||||
Join us on our `Gitter channel <https://gitter.im/jmespath/chat>`__
|
||||
if you want to chat or if you have any questions.
|
||||
|
||||
|
||||
|
|
@ -0,0 +1 @@
|
|||
pip
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
Copyright (c) 2013 Amazon.com, Inc. or its affiliates. All Rights Reserved
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining a
|
||||
copy of this software and associated documentation files (the
|
||||
"Software"), to deal in the Software without restriction, including
|
||||
without limitation the rights to use, copy, modify, merge, publish, dis-
|
||||
tribute, sublicense, and/or sell copies of the Software, and to permit
|
||||
persons to whom the Software is furnished to do so, subject to the fol-
|
||||
lowing conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be included
|
||||
in all copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
|
||||
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABIL-
|
||||
ITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
|
||||
SHALL THE AUTHOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
|
||||
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
|
||||
IN THE SOFTWARE.
|
||||
|
|
@ -0,0 +1,251 @@
|
|||
Metadata-Version: 2.0
|
||||
Name: jmespath
|
||||
Version: 0.10.0
|
||||
Summary: JSON Matching Expressions
|
||||
Home-page: https://github.com/jmespath/jmespath.py
|
||||
Author: James Saryerwinnie
|
||||
Author-email: js@jamesls.com
|
||||
License: MIT
|
||||
Platform: UNKNOWN
|
||||
Classifier: Development Status :: 5 - Production/Stable
|
||||
Classifier: Intended Audience :: Developers
|
||||
Classifier: Natural Language :: English
|
||||
Classifier: License :: OSI Approved :: MIT License
|
||||
Classifier: Programming Language :: Python
|
||||
Classifier: Programming Language :: Python :: 2
|
||||
Classifier: Programming Language :: Python :: 2.6
|
||||
Classifier: Programming Language :: Python :: 2.7
|
||||
Classifier: Programming Language :: Python :: 3
|
||||
Classifier: Programming Language :: Python :: 3.3
|
||||
Classifier: Programming Language :: Python :: 3.4
|
||||
Classifier: Programming Language :: Python :: 3.5
|
||||
Classifier: Programming Language :: Python :: 3.6
|
||||
Classifier: Programming Language :: Python :: 3.7
|
||||
Classifier: Programming Language :: Python :: Implementation :: CPython
|
||||
Classifier: Programming Language :: Python :: Implementation :: PyPy
|
||||
Requires-Python: >=2.6, !=3.0.*, !=3.1.*, !=3.2.*
|
||||
|
||||
JMESPath
|
||||
========
|
||||
|
||||
|
||||
.. image:: https://badges.gitter.im/Join Chat.svg
|
||||
:target: https://gitter.im/jmespath/chat
|
||||
|
||||
|
||||
.. image:: https://travis-ci.org/jmespath/jmespath.py.svg?branch=develop
|
||||
:target: https://travis-ci.org/jmespath/jmespath.py
|
||||
|
||||
|
||||
.. image:: https://codecov.io/github/jmespath/jmespath.py/coverage.svg?branch=develop
|
||||
:target: https://codecov.io/github/jmespath/jmespath.py?branch=develop
|
||||
|
||||
|
||||
JMESPath (pronounced "james path") allows you to declaratively specify how to
|
||||
extract elements from a JSON document.
|
||||
|
||||
For example, given this document::
|
||||
|
||||
{"foo": {"bar": "baz"}}
|
||||
|
||||
The jmespath expression ``foo.bar`` will 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[*].name`` will return ["one", "two"].
|
||||
Negative indexing is also supported (-1 refers to the last element
|
||||
in the list). Given the data above, the expression
|
||||
``foo.bar[-1].name`` will return "two".
|
||||
|
||||
The ``*`` can also be used for hash types::
|
||||
|
||||
{"foo": {"bar": {"name": "one"}, "baz": {"name": "two"}}}
|
||||
|
||||
The expression: ``foo.*.name`` will return ["one", "two"].
|
||||
|
||||
|
||||
Installation
|
||||
============
|
||||
|
||||
You can install JMESPath from pypi with:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
pip install jmespath
|
||||
|
||||
|
||||
API
|
||||
===
|
||||
|
||||
The ``jmespath.py`` library has two functions
|
||||
that operate on python data structures. You can use ``search``
|
||||
and give it the jmespath expression and the data:
|
||||
|
||||
.. code:: python
|
||||
|
||||
>>> import jmespath
|
||||
>>> path = jmespath.search('foo.bar', {'foo': {'bar': 'baz'}})
|
||||
'baz'
|
||||
|
||||
Similar to the ``re`` module, you can use the ``compile`` function
|
||||
to compile the JMESPath expression and use this parsed expression
|
||||
to perform repeated searches:
|
||||
|
||||
.. code:: python
|
||||
|
||||
>>> import jmespath
|
||||
>>> 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.
|
||||
|
||||
Options
|
||||
-------
|
||||
|
||||
You can provide an instance of ``jmespath.Options`` to control how
|
||||
a JMESPath expression is evaluated. The most common scenario for
|
||||
using an ``Options`` instance is if you want to have ordered output
|
||||
of your dict keys. To do this you can use either of these options:
|
||||
|
||||
.. code:: python
|
||||
|
||||
>>> import jmespath
|
||||
>>> jmespath.search('{a: a, b: b}',
|
||||
... mydata,
|
||||
... jmespath.Options(dict_cls=collections.OrderedDict))
|
||||
|
||||
|
||||
>>> import jmespath
|
||||
>>> parsed = jmespath.compile('{a: a, b: b}')
|
||||
>>> parsed.search(mydata,
|
||||
... jmespath.Options(dict_cls=collections.OrderedDict))
|
||||
|
||||
|
||||
Custom Functions
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
The JMESPath language has numerous
|
||||
`built-in functions
|
||||
<http://jmespath.org/specification.html#built-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 proposals
|
||||
`here <https://github.com/jmespath/jmespath.site/issues>`__.
|
||||
|
||||
To create custom functions:
|
||||
|
||||
* Create a subclass of ``jmespath.functions.Functions``.
|
||||
* Create a method with the name ``_func_<your function name>``.
|
||||
* Apply the ``jmespath.functions.signature`` decorator that indicates
|
||||
the expected types of the function arguments.
|
||||
* Provide an instance of your subclass in a ``jmespath.Options`` object.
|
||||
|
||||
Below are a few examples:
|
||||
|
||||
.. code:: python
|
||||
|
||||
import jmespath
|
||||
from jmespath import functions
|
||||
|
||||
# 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.
|
||||
class CustomFunctions(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):
|
||||
return x + 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 3
|
||||
print(
|
||||
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 at
|
||||
`jmespath.site <https://github.com/jmespath/jmespath.site/issues>`__.
|
||||
|
||||
|
||||
Specification
|
||||
=============
|
||||
|
||||
If you'd like to learn more about the JMESPath language, you can check out
|
||||
the `JMESPath tutorial <http://jmespath.org/tutorial.html>`__. Also check
|
||||
out the `JMESPath examples page <http://jmespath.org/examples.html>`__ for
|
||||
examples of more complex jmespath queries.
|
||||
|
||||
The grammar is specified using ABNF, as described in
|
||||
`RFC4234 <http://www.ietf.org/rfc/rfc4234.txt>`_.
|
||||
You can find the most up to date
|
||||
`grammar for JMESPath here <http://jmespath.org/specification.html#grammar>`__.
|
||||
|
||||
You can read the full
|
||||
`JMESPath specification here <http://jmespath.org/specification.html>`__.
|
||||
|
||||
|
||||
Testing
|
||||
=======
|
||||
|
||||
In addition to the unit tests for the jmespath modules,
|
||||
there is a ``tests/compliance`` directory 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.
|
||||
|
||||
|
||||
Discuss
|
||||
=======
|
||||
|
||||
Join us on our `Gitter channel <https://gitter.im/jmespath/chat>`__
|
||||
if you want to chat or if you have any questions.
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
../../../bin/__pycache__/jp.cpython-39.pyc,,
|
||||
../../../bin/jp.py,sha256=PDO-MtuJ72Ph786r2Aw05wZ5q22GJguev9G0xBXoOI8,1685
|
||||
jmespath-0.10.0.dist-info/DESCRIPTION.rst,sha256=pRJREzjsiiQ_PZ72_nUj7-C-cXNkHnJ3iCVCDJpnUyg,6925
|
||||
jmespath-0.10.0.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
|
||||
jmespath-0.10.0.dist-info/LICENSE.txt,sha256=ZrMTzOgO0GI_x9s_JIY6DID9g-s0Gka1eGQViudPqlY,1084
|
||||
jmespath-0.10.0.dist-info/METADATA,sha256=2JiCaPP_JR87u3ESC8bZLl1-z-2tAx6mHB60DIsGIX0,8023
|
||||
jmespath-0.10.0.dist-info/RECORD,,
|
||||
jmespath-0.10.0.dist-info/WHEEL,sha256=GrqQvamwgBV4nLoJe0vhYRSWzWsx7xjlt74FT0SWYfE,110
|
||||
jmespath-0.10.0.dist-info/metadata.json,sha256=Zyl6gtawhruY1SbwtILEz8xueg-HiojsyRsudgAudBs,1188
|
||||
jmespath-0.10.0.dist-info/top_level.txt,sha256=vuy_oZ1ckpeSNrAi8JK8-yIGO6bduO3qvW2cCMQmPH8,9
|
||||
jmespath/__init__.py,sha256=3cgzWR1zfRQaIs83GD33B1LDw6AzqCTEhY_2s5JMUI8,623
|
||||
jmespath/__pycache__/__init__.cpython-39.pyc,,
|
||||
jmespath/__pycache__/ast.cpython-39.pyc,,
|
||||
jmespath/__pycache__/compat.cpython-39.pyc,,
|
||||
jmespath/__pycache__/exceptions.cpython-39.pyc,,
|
||||
jmespath/__pycache__/functions.cpython-39.pyc,,
|
||||
jmespath/__pycache__/lexer.cpython-39.pyc,,
|
||||
jmespath/__pycache__/parser.cpython-39.pyc,,
|
||||
jmespath/__pycache__/visitor.cpython-39.pyc,,
|
||||
jmespath/ast.py,sha256=SiHRM1mdQPRt12R2qkQu_Ezbd-ghk5HLy1Hl1jHAyv8,2130
|
||||
jmespath/compat.py,sha256=Q_a-dEOGrKa9Mimrhfpuq5r-9poyBz9ZDvbzSpPE0Tw,2117
|
||||
jmespath/exceptions.py,sha256=5HRot4Bv3SCTdvh5lAQdQBsqSdaKjuTPSyGmk08zSvA,4128
|
||||
jmespath/functions.py,sha256=1ZwvCNVzHU1hFUUeNbP9LO_v_GqJPAGH-xxF98vNen8,12766
|
||||
jmespath/lexer.py,sha256=LE3-dM75ny9RMR8mXmWlKKRTIlz8njvWz-M-2y4t5WA,8574
|
||||
jmespath/parser.py,sha256=XwLffptCw5f3PKoJYI7C_pbAX5MKzxFECwnVqD7fk3A,19082
|
||||
jmespath/visitor.py,sha256=jSGILEeuY16WkMkxel2yytcbljVNtNtLW4Bx0qfV4cU,10844
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
Wheel-Version: 1.0
|
||||
Generator: bdist_wheel (0.26.0)
|
||||
Root-Is-Purelib: true
|
||||
Tag: py2-none-any
|
||||
Tag: py3-none-any
|
||||
|
||||
|
|
@ -0,0 +1 @@
|
|||
{"generator": "bdist_wheel (0.26.0)", "summary": "JSON Matching Expressions", "classifiers": ["Development Status :: 5 - Production/Stable", "Intended Audience :: Developers", "Natural Language :: English", "License :: OSI Approved :: MIT License", "Programming Language :: Python", "Programming Language :: Python :: 2", "Programming Language :: Python :: 2.6", "Programming Language :: Python :: 2.7", "Programming Language :: Python :: 3", "Programming Language :: Python :: 3.3", "Programming Language :: Python :: 3.4", "Programming Language :: Python :: 3.5", "Programming Language :: Python :: 3.6", "Programming Language :: Python :: 3.7", "Programming Language :: Python :: Implementation :: CPython", "Programming Language :: Python :: Implementation :: PyPy"], "extensions": {"python.details": {"project_urls": {"Home": "https://github.com/jmespath/jmespath.py"}, "contacts": [{"email": "js@jamesls.com", "name": "James Saryerwinnie", "role": "author"}], "document_names": {"description": "DESCRIPTION.rst", "license": "LICENSE.txt"}}}, "license": "MIT", "metadata_version": "2.0", "name": "jmespath", "requires_python": ">=2.6, !=3.0.*, !=3.1.*, !=3.2.*", "version": "0.10.0"}
|
||||
|
|
@ -0,0 +1 @@
|
|||
jmespath
|
||||
Loading…
Add table
Add a link
Reference in a new issue