Update notable differences.

Author: jg-rp

LICENSE.txt

@@ -2,8 +2,20 @@ MIT License
 
 Copyright (c) 2023-present James Prior <[email protected]>
 
-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, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+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, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+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 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS 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.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS 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.

README.md

@@ -276,16 +276,14 @@ This is a list of things that you might find in other JSONPath implementation th
 - We don't support extension functions of the form `selector.func()`.
 - We always return a list of matches from `jsonpath.findall()`, never a scalar value.
 - We do not support arithmetic in filter expression.
-- Python JSONPath is strictly read only. There are no update "selectors".
+- Python JSONPath is strictly read only. There are no update "selectors", although a Python API for working with `JSONPathMatch`s may well be added in the future.
 
 And this is a list of areas where we deviate from the [IETF JSONPath draft](https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-11).
 
-- The built-in `match()` function uses Python's standard _re_ module, without attempting to map I-Regexps to it. A closer approximation of I-Regexps could be achieved by depending on the third-party [regex](https://pypi.org/project/regex/) package.
 - We don't require filters that use a function extension to include a comparison operator.
 - Whitespace is mostly insignificant unless inside quotes.
 - The root token (default `$`) is optional.
 - Paths starting with a dot (`.`) are OK. `.thing` is the same as `$.thing`, as is `thing`, `$[thing]` and `$["thing"]`.
-- Nested filters are not supported.
 
 And this is a list of features that are uncommon or unique to Python JSONPath.
 

docs/syntax.md

@@ -157,16 +157,14 @@ This is a list of things that you might find in other JSONPath implementation th
 - We don't support extension functions of the form `selector.func()`.
 - We always return a list of matches from `jsonpath.findall()`, never a scalar value.
 - We do not support arithmetic in filter expression.
-- Python JSONPath is strictly read only. There are no update "selectors".
+- Python JSONPath is strictly read only. There are no update "selectors", although a Python API for working with `JSONPathMatch`s may well be added in the future.
 
 And this is a list of areas where we deviate from the [IETF JSONPath draft](https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-11).
 
-- For now, the only built-in function extension is `length()`.
 - We don't require filters that use a function extension to include a comparison operator.
 - Whitespace is mostly insignificant unless inside quotes.
 - The root token (default `$`) is optional.
 - Paths starting with a dot (`.`) are OK. `.thing` is the same as `$.thing`, as is `thing`, `$[thing]` and `$["thing"]`.
-- Nested filters are not supported.
 
 And this is a list of features that are uncommon or unique to Python JSONPath.