memory-graph 0.3.80__tar.gz → 0.3.82__tar.gz

{memory_graph-0.3.80 → memory_graph-0.3.82}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memory_graph
-Version: 0.3.80
+Version: 0.3.82
 Summary: Teaching tool and debugging aid in context of references, mutable data types, and shallow and deep copy.
 Author-email: Bas Terwijn <bterwijn@gmail.com>
 License-Expression: BSD-2-Clause
@@ -1052,7 +1052,7 @@ Different aspects of memory_graph can be configured. The default configuration c
   - Set dark mode to 'True' or 'False', or 'None' to toggle.
 
 - **mg.transparent_background(b: bool = None)**
-  - Set transparent_background to 'True' or 'False', or 'None' to toggle.
+  - Set transparent background to 'True' or 'False', or 'None' to toggle.
 
 ## Simplified Graph ##
 Memory_graph simplifies the visualization (and the viewer's mental model) by **not** showing separate nodes for immutable types like `bool`, `int`, `float`, `complex`, and `str` by default. This simplification can sometimes be slightly misleading. As in the example below, after a shallow copy, lists `a` and `b` technically share their `int` values, but the graph makes it appear as though `a` and `b` each have their own copies. However, since `int` is immutable, this simplification will never lead to unexpected changes (changing `a`'s ints won’t affect `b`) so will never result in bugs.

{memory_graph-0.3.80 → memory_graph-0.3.82}/README.md

@@ -1032,7 +1032,7 @@ Different aspects of memory_graph can be configured. The default configuration c
   - Set dark mode to 'True' or 'False', or 'None' to toggle.
 
 - **mg.transparent_background(b: bool = None)**
-  - Set transparent_background to 'True' or 'False', or 'None' to toggle.
+  - Set transparent background to 'True' or 'False', or 'None' to toggle.
 
 ## Simplified Graph ##
 Memory_graph simplifies the visualization (and the viewer's mental model) by **not** showing separate nodes for immutable types like `bool`, `int`, `float`, `complex`, and `str` by default. This simplification can sometimes be slightly misleading. As in the example below, after a shallow copy, lists `a` and `b` technically share their `int` values, but the graph makes it appear as though `a` and `b` each have their own copies. However, since `int` is immutable, this simplification will never lead to unexpected changes (changing `a`'s ints won’t affect `b`) so will never result in bugs.

{memory_graph-0.3.80 → memory_graph-0.3.82}/memory_graph/__init__.py

@@ -2,7 +2,7 @@
 # Copyright (c) 2023, Bas Terwijn.
 # SPDX-License-Identifier: BSD-2-Clause
 
-__version__ = "0.3.80"
+__version__ = "0.3.82"
 __author__ = 'Bas Terwijn'
 
 import memory_graph.memory_to_nodes as memory_to_nodes

{memory_graph-0.3.80 → memory_graph-0.3.82}/memory_graph/config_default.py

@@ -86,12 +86,12 @@ def set_colors(dark=None, transparent=None):
         config.foreground_color = foreground_color_dark
         config.index_color = index_color_dark
         config.background_color = background_color_dark
-        config.type_to_color = type_to_color_dark
+        config.type_to_color = type_to_color_dark.copy()
     else:
         config.foreground_color = foreground_color_light
         config.index_color = index_color_light
         config.background_color = background_color_light
-        config.type_to_color = type_to_color_light
+        config.type_to_color = type_to_color_light.copy()
     if transparent:
         config.background_color = "transparent"
 

{memory_graph-0.3.80 → memory_graph-0.3.82}/memory_graph/config_helpers.py

@@ -48,11 +48,9 @@ def default_to_string(data):
             s = data
         else:
             s = str(data)
-        return 
     except Exception as e:
         s = 'no stringification, '+ type(e).__name__ +': '+ str(e)
-    finally:
-        return utils.prep_str(s)
+    return utils.prep_str(s)
 
 def get_to_string(data, default=lambda d: default_to_string(d)):
     return get_property(id(data),
@@ -61,7 +59,7 @@ def get_to_string(data, default=lambda d: default_to_string(d)):
                         config.type_to_string, 
                         default )
 
-def get_node_color(node, default='white'):
+def get_node_color(node, default=config.background_color):
     return get_property(node.get_id(),
                         utils.get_all_types(node.get_data()),
                         type(node),

{memory_graph-0.3.80 → memory_graph-0.3.82}/memory_graph.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memory_graph
-Version: 0.3.80
+Version: 0.3.82
 Summary: Teaching tool and debugging aid in context of references, mutable data types, and shallow and deep copy.
 Author-email: Bas Terwijn <bterwijn@gmail.com>
 License-Expression: BSD-2-Clause
@@ -1052,7 +1052,7 @@ Different aspects of memory_graph can be configured. The default configuration c
   - Set dark mode to 'True' or 'False', or 'None' to toggle.
 
 - **mg.transparent_background(b: bool = None)**
-  - Set transparent_background to 'True' or 'False', or 'None' to toggle.
+  - Set transparent background to 'True' or 'False', or 'None' to toggle.
 
 ## Simplified Graph ##
 Memory_graph simplifies the visualization (and the viewer's mental model) by **not** showing separate nodes for immutable types like `bool`, `int`, `float`, `complex`, and `str` by default. This simplification can sometimes be slightly misleading. As in the example below, after a shallow copy, lists `a` and `b` technically share their `int` values, but the graph makes it appear as though `a` and `b` each have their own copies. However, since `int` is immutable, this simplification will never lead to unexpected changes (changing `a`'s ints won’t affect `b`) so will never result in bugs.

{memory_graph-0.3.80 → memory_graph-0.3.82}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "memory_graph"
-version = "0.3.80"
+version = "0.3.82"
 description = "Teaching tool and debugging aid in context of references, mutable data types, and shallow and deep copy."
 authors = [
     {name = "Bas Terwijn", email = "bterwijn@gmail.com"}