When I try to use jmespath after a clean install I get, "Exception: No valid extractor name to use in input".
Judging from the traceback error shown, it seems pyresttest is using Python 2.7
Traceback (most recent call last): File "/usr/local/bin/pyresttest", line 4, in <module> __import__('pkg_resources').run_script('pyresttest==1.7.2.dev0', 'pyresttest') File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/__init__.py", line 742, in run_script
Jmespath seems to be installed for Python 2.7:
$ easy_install jmespath Searching for jmespath Best match: jmespath 0.9.3 Processing jmespath-0.9.3-py2.7.egg jmespath 0.9.3 is already the active version in easy-install.pth Installing jp.py script to /usr/local/bin Using /usr/local/lib/python2.7/site-packages/jmespath-0.9.3-py2.7.egg Processing dependencies for jmespath Finished processing dependencies for jmespath
Anjimeduri
commented
6 years ago
When I try to use jmespath after a clean install I get, "Exception: No valid extractor name to use in input". Judging from the traceback error shown, it seems pyresttest is using Python 2.7
Traceback (most recent call last): File "/usr/local/bin/pyresttest", line 4, in <module> __import__('pkg_resources').run_script('pyresttest==1.7.2.dev0', 'pyresttest') File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources/__init__.py", line 742, in run_scriptJmespath seems to be installed for Python 2.7:
$ easy_install jmespath Searching for jmespath Best match: jmespath 0.9.3 Processing jmespath-0.9.3-py2.7.egg jmespath 0.9.3 is already the active version in easy-install.pth Installing jp.py script to /usr/local/bin Using /usr/local/lib/python2.7/site-packages/jmespath-0.9.3-py2.7.egg Processing dependencies for jmespath Finished processing dependencies for jmespath