dotted-notation 0.49.0__tar.gz → 0.49.1__tar.gz

{dotted_notation-0.49.0 → dotted_notation-0.49.1}/CHANGELOG.md

@@ -3,6 +3,15 @@
 All notable changes to `dotted` are recorded here. Versions prior to
 the ones listed are omitted — browse git history for earlier entries.
 
+## [0.49.1]
+
+### Documentation
+- The README describes a reference, `$$(expr)`, as an inline evaluation
+  expression: the dotted expression inside, transforms included, is
+  evaluated during traversal and its value stands where it is written. In a
+  transform argument, guard or filter value that is the value itself; in an
+  access position it is the key looked up.
+
 ## [0.49.0]
 
 ### Added

{dotted_notation-0.49.0/dotted_notation.egg-info → dotted_notation-0.49.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dotted_notation
-Version: 0.49.0
+Version: 0.49.1
 Summary: Dotted notation for safe nested data traversal with optional chaining, pattern matching, and transforms
 Author-email: Frey Waid <logophage1@gmail.com>
 License-Expression: MIT
@@ -1396,7 +1396,8 @@ To chain through the items, use a pattern instead:
 ## Substitutions and References
 
 All `$`-prefixed syntax falls into two categories: **substitutions** (resolved
-at replace time) and **references** (resolved during traversal).
+at replace time) and **references**, inline expressions evaluated during
+traversal.
 
 | Syntax | Type | Resolved against |
 |---|---|---|
@@ -1502,14 +1503,22 @@ the parsed result, so a path used many times can be compiled once:
 <a id="references"></a>
 ### References
 
-A **reference** resolves a dotted path against the root object during traversal
-and uses the result as a literal key. The syntax is `$$(path)`:
+A **reference**, `$$(expr)`, is an inline evaluation expression. The dotted
+expression inside is evaluated during traversal, as `get` would evaluate it
+against the root, and its value stands where the reference is written. The
+expression is a full dotted path, so it may carry patterns and transforms:
+`$$(config.offset|mul:10)` is the value of `config.offset`, times ten.
+
+Where the reference stands decides what its value does. In a transform
+argument, a guard value or a filter value it is the value itself (see
+[References in transforms and guards](#references-in-transforms-and-guards)).
+In an access position, as a key or slot, it is the key to look up:
 
     >>> data = {'config': {'field': 'name'}, 'name': 'Alice'}
     >>> dotted.get(data, '$$(config.field)')
     'Alice'
 
-Here `$$(config.field)` resolves to `'name'`, then looks up `data['name']`.
+Here `$$(config.field)` evaluates to `'name'`, then looks up `data['name']`.
 
 References work with all access types and in any position:
 
@@ -1606,6 +1615,12 @@ and so on:
     >>> dotted.get(data, 'n|add:$$(config.offset)')
     15
 
+The expression inside may chain transforms of its own; they apply to its value
+before it is passed:
+
+    >>> dotted.get(data, 'n|add:$$(config.offset|mul:10)')
+    105
+
     >>> data = {'items': [{'price': 100, 'rate': 1.5}, {'price': 20, 'rate': 2}]}
     >>> dotted.get(data, 'items[*].price|mul:$$(^^rate)')
     (150.0, 40)

{dotted_notation-0.49.0 → dotted_notation-0.49.1}/README.md

@@ -1349,7 +1349,8 @@ To chain through the items, use a pattern instead:
 ## Substitutions and References
 
 All `$`-prefixed syntax falls into two categories: **substitutions** (resolved
-at replace time) and **references** (resolved during traversal).
+at replace time) and **references**, inline expressions evaluated during
+traversal.
 
 | Syntax | Type | Resolved against |
 |---|---|---|
@@ -1455,14 +1456,22 @@ the parsed result, so a path used many times can be compiled once:
 <a id="references"></a>
 ### References
 
-A **reference** resolves a dotted path against the root object during traversal
-and uses the result as a literal key. The syntax is `$$(path)`:
+A **reference**, `$$(expr)`, is an inline evaluation expression. The dotted
+expression inside is evaluated during traversal, as `get` would evaluate it
+against the root, and its value stands where the reference is written. The
+expression is a full dotted path, so it may carry patterns and transforms:
+`$$(config.offset|mul:10)` is the value of `config.offset`, times ten.
+
+Where the reference stands decides what its value does. In a transform
+argument, a guard value or a filter value it is the value itself (see
+[References in transforms and guards](#references-in-transforms-and-guards)).
+In an access position, as a key or slot, it is the key to look up:
 
     >>> data = {'config': {'field': 'name'}, 'name': 'Alice'}
     >>> dotted.get(data, '$$(config.field)')
     'Alice'
 
-Here `$$(config.field)` resolves to `'name'`, then looks up `data['name']`.
+Here `$$(config.field)` evaluates to `'name'`, then looks up `data['name']`.
 
 References work with all access types and in any position:
 
@@ -1559,6 +1568,12 @@ and so on:
     >>> dotted.get(data, 'n|add:$$(config.offset)')
     15
 
+The expression inside may chain transforms of its own; they apply to its value
+before it is passed:
+
+    >>> dotted.get(data, 'n|add:$$(config.offset|mul:10)')
+    105
+
     >>> data = {'items': [{'price': 100, 'rate': 1.5}, {'price': 20, 'rate': 2}]}
     >>> dotted.get(data, 'items[*].price|mul:$$(^^rate)')
     (150.0, 40)

{dotted_notation-0.49.0 → dotted_notation-0.49.1/dotted_notation.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dotted_notation
-Version: 0.49.0
+Version: 0.49.1
 Summary: Dotted notation for safe nested data traversal with optional chaining, pattern matching, and transforms
 Author-email: Frey Waid <logophage1@gmail.com>
 License-Expression: MIT
@@ -1396,7 +1396,8 @@ To chain through the items, use a pattern instead:
 ## Substitutions and References
 
 All `$`-prefixed syntax falls into two categories: **substitutions** (resolved
-at replace time) and **references** (resolved during traversal).
+at replace time) and **references**, inline expressions evaluated during
+traversal.
 
 | Syntax | Type | Resolved against |
 |---|---|---|
@@ -1502,14 +1503,22 @@ the parsed result, so a path used many times can be compiled once:
 <a id="references"></a>
 ### References
 
-A **reference** resolves a dotted path against the root object during traversal
-and uses the result as a literal key. The syntax is `$$(path)`:
+A **reference**, `$$(expr)`, is an inline evaluation expression. The dotted
+expression inside is evaluated during traversal, as `get` would evaluate it
+against the root, and its value stands where the reference is written. The
+expression is a full dotted path, so it may carry patterns and transforms:
+`$$(config.offset|mul:10)` is the value of `config.offset`, times ten.
+
+Where the reference stands decides what its value does. In a transform
+argument, a guard value or a filter value it is the value itself (see
+[References in transforms and guards](#references-in-transforms-and-guards)).
+In an access position, as a key or slot, it is the key to look up:
 
     >>> data = {'config': {'field': 'name'}, 'name': 'Alice'}
     >>> dotted.get(data, '$$(config.field)')
     'Alice'
 
-Here `$$(config.field)` resolves to `'name'`, then looks up `data['name']`.
+Here `$$(config.field)` evaluates to `'name'`, then looks up `data['name']`.
 
 References work with all access types and in any position:
 
@@ -1606,6 +1615,12 @@ and so on:
     >>> dotted.get(data, 'n|add:$$(config.offset)')
     15
 
+The expression inside may chain transforms of its own; they apply to its value
+before it is passed:
+
+    >>> dotted.get(data, 'n|add:$$(config.offset|mul:10)')
+    105
+
     >>> data = {'items': [{'price': 100, 'rate': 1.5}, {'price': 20, 'rate': 2}]}
     >>> dotted.get(data, 'items[*].price|mul:$$(^^rate)')
     (150.0, 40)

{dotted_notation-0.49.0 → dotted_notation-0.49.1}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "dotted_notation"
-version = "0.49.0"
+version = "0.49.1"
 description = "Dotted notation for safe nested data traversal with optional chaining, pattern matching, and transforms"
 readme = "README.md"
 requires-python = ">=3.6"

{dotted_notation-0.49.0 → dotted_notation-0.49.1}/setup.py

@@ -11,6 +11,7 @@ same files run as Python.
 import os
 
 from setuptools import Extension, setup
+from setuptools.command.build_ext import build_ext as _build_ext
 
 # The engine and the ops it runs. grammar.py, the parser, is left out on
 # purpose: pyparsing inspects its parse actions as Python functions.
@@ -47,7 +48,20 @@ def extensions():
     return cythonize(
         [Extension('dotted.' + name, ['dotted/' + name + '.py'], optional=True) for name in MODULES],
         compiler_directives={'language_level': 3},
+        nthreads=os.cpu_count() or 1,
     )
 
 
-setup(ext_modules=extensions())
+class build_ext(_build_ext):
+    """
+    Compile the extensions one per core. setuptools builds them one after
+    another unless -j is given; the modules are independent, so a release
+    wheel compiles in a fraction of the time on a multi-core runner.
+    """
+    def finalize_options(self):
+        super().finalize_options()
+        if self.parallel is None:
+            self.parallel = os.cpu_count() or 1
+
+
+setup(ext_modules=extensions(), cmdclass={'build_ext': build_ext})