winipedia-utils 0.4.41__tar.gz → 0.4.43__tar.gz

{winipedia_utils-0.4.41 → winipedia_utils-0.4.43}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: winipedia-utils
-Version: 0.4.41
+Version: 0.4.43
 Summary: A package with many utility functions
 License-Expression: MIT
 License-File: LICENSE
@@ -152,6 +152,10 @@ my_project/
 
 For each function, class, and method, skeleton tests are created with `NotImplementedError` placeholders for you to implement.
 
+If you have autosuse fixtures just write and add them to the `tests/base/fixtures` directory. They will be automatically discovered, plugged into conftest and used in all tests according to defined scope.
+The filenames in the fixtures folder are just for organisation purposes for your convenience. You still have to 
+apply the pytest.fixture decorator to the fixture function and define the scope. So a session scoped function defined on function.py will still run as a session scoped fixture.
+
 ## Configuration Files
 
 Configuration files are managed automatically by the setup system:
@@ -160,6 +164,7 @@ Configuration files are managed automatically by the setup system:
 - **Empty files** - If you want to disable a config file, make it empty. This signals that the file is unwanted and won't be modified
 - **Custom additions** - You can add custom configurations as long as the standard configurations remain intact
 - **Modified standards** - If you modify the standard configurations, they will be restored on the next setup run
+- **Subclasses** - You can create custom config files by subclassing the standard ones. They will be automatically created and managed when you commit or run pytest. winipedia_utils automatically discovers and calls them. This way you can adjust or add some settings. It is however important the parent class stays a subset of the child class according to the description in the function `nested_structure_is_subset` in `winipedia_utils.iterating.iterate`.
 
 ## Branch Protection
 

{winipedia_utils-0.4.41 → winipedia_utils-0.4.43}/README.md

@@ -126,6 +126,10 @@ my_project/
 
 For each function, class, and method, skeleton tests are created with `NotImplementedError` placeholders for you to implement.
 
+If you have autosuse fixtures just write and add them to the `tests/base/fixtures` directory. They will be automatically discovered, plugged into conftest and used in all tests according to defined scope.
+The filenames in the fixtures folder are just for organisation purposes for your convenience. You still have to 
+apply the pytest.fixture decorator to the fixture function and define the scope. So a session scoped function defined on function.py will still run as a session scoped fixture.
+
 ## Configuration Files
 
 Configuration files are managed automatically by the setup system:
@@ -134,6 +138,7 @@ Configuration files are managed automatically by the setup system:
 - **Empty files** - If you want to disable a config file, make it empty. This signals that the file is unwanted and won't be modified
 - **Custom additions** - You can add custom configurations as long as the standard configurations remain intact
 - **Modified standards** - If you modify the standard configurations, they will be restored on the next setup run
+- **Subclasses** - You can create custom config files by subclassing the standard ones. They will be automatically created and managed when you commit or run pytest. winipedia_utils automatically discovers and calls them. This way you can adjust or add some settings. It is however important the parent class stays a subset of the child class according to the description in the function `nested_structure_is_subset` in `winipedia_utils.iterating.iterate`.
 
 ## Branch Protection
 

{winipedia_utils-0.4.41 → winipedia_utils-0.4.43}/pyproject.toml

@@ -1,7 +1,7 @@
 # Project section
 [project]
 name = "winipedia-utils"
-version = "0.4.41"
+version = "0.4.43"
 description = "A package with many utility functions"
 readme = "README.md"
 requires-python = ">=3.12"

{winipedia_utils-0.4.41 → winipedia_utils-0.4.43}/winipedia_utils/iterating/iterate.py

@@ -49,7 +49,7 @@ def nested_structure_is_subset(
     Each value of a key must be equal to the value of the same key in the superset.
     If the value is dictionary, the function is called recursively.
     If the value is list, each item must be in the list of the same key in the superset.
-    The order in lists matters.
+    The order in lists does not matter.
 
     Returns:
         True if subset is a nested subset of superset, False otherwise
@@ -68,6 +68,11 @@ def nested_structure_is_subset(
 
         def get_actual(key_or_index: Any) -> Any:
             """Get actual value from superset."""
+            subset_val = subset[key_or_index]
+            for superset_val in superset:
+                if nested_structure_is_subset(subset_val, superset_val):
+                    return superset_val
+
             return superset[key_or_index] if key_or_index < len(superset) else None
     else:
         return subset == superset