memory-graph 0.3.58__tar.gz → 0.3.59__tar.gz

{memory_graph-0.3.58/memory_graph.egg-info → memory_graph-0.3.59}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memory_graph
-Version: 0.3.58
+Version: 0.3.59
 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
@@ -169,7 +169,7 @@ Learn the right **mental model** to think about Python data. The [Python Data Mo
 
 
 ## Immutable Type ##
-In the code below variable `a` and `b` both reference the same tuple value (4, 3, 2). A tuple is an immutable type and therefore when we change variable `b` its value **cannot** be mutated in place, and thus an automatic copy is made and `a` and `b` reference their own value afterwards.
+In the code below variable `a` and `b` both reference the same tuple value (4, 3, 2). A tuple is an immutable type and therefore when we change variable `b` its value **cannot** be mutated in place, and thus an automatic copy is made and `a` and `b` each reference their own value afterwards.
 
 ```python
 import memory_graph as mg
@@ -203,7 +203,7 @@ mg.render(locals(), 'mutable2.png')
 |:-----------------------------------------------------------:|:-------------------------------------------------------------:|
 | mutable1.png | mutable2.png |
 
-One practical reason why Python makes the distinction between mutable and immutable types is that a value of a mutable type can be large, making it inefficient to copy each time we change it. Immutable values generally don't need to change as much, or are small making copying less of a concern.
+One practical reason why Python makes the distinction between mutable and immutable types is that a value of a mutable type can be large, making it inefficient to copy each time we change it. Values of immutable type generally don't need to change as much, or are small, making copying less of a concern.
 
 ## Copying Values of Mutable Type ##
 Python offers three different "copy" options that we will demonstrate using a nested list:
@@ -666,6 +666,9 @@ Different aspects of memory_graph can be configured. The default configuration c
 - ***mg.config.render_filename*** : str
   - The default filename to render to, default 'memory_graph.pdf'.
 
+- ***mg.config.type_labels*** : bool
+  - If True the type of each node is shown as label, default True.
+
 - ***mg.config.block_prints_location*** : bool
   - If True the source location is printed in block(), default True.
   

{memory_graph-0.3.58 → memory_graph-0.3.59}/README.md

@@ -149,7 +149,7 @@ Learn the right **mental model** to think about Python data. The [Python Data Mo
 
 
 ## Immutable Type ##
-In the code below variable `a` and `b` both reference the same tuple value (4, 3, 2). A tuple is an immutable type and therefore when we change variable `b` its value **cannot** be mutated in place, and thus an automatic copy is made and `a` and `b` reference their own value afterwards.
+In the code below variable `a` and `b` both reference the same tuple value (4, 3, 2). A tuple is an immutable type and therefore when we change variable `b` its value **cannot** be mutated in place, and thus an automatic copy is made and `a` and `b` each reference their own value afterwards.
 
 ```python
 import memory_graph as mg
@@ -183,7 +183,7 @@ mg.render(locals(), 'mutable2.png')
 |:-----------------------------------------------------------:|:-------------------------------------------------------------:|
 | mutable1.png | mutable2.png |
 
-One practical reason why Python makes the distinction between mutable and immutable types is that a value of a mutable type can be large, making it inefficient to copy each time we change it. Immutable values generally don't need to change as much, or are small making copying less of a concern.
+One practical reason why Python makes the distinction between mutable and immutable types is that a value of a mutable type can be large, making it inefficient to copy each time we change it. Values of immutable type generally don't need to change as much, or are small, making copying less of a concern.
 
 ## Copying Values of Mutable Type ##
 Python offers three different "copy" options that we will demonstrate using a nested list:
@@ -646,6 +646,9 @@ Different aspects of memory_graph can be configured. The default configuration c
 - ***mg.config.render_filename*** : str
   - The default filename to render to, default 'memory_graph.pdf'.
 
+- ***mg.config.type_labels*** : bool
+  - If True the type of each node is shown as label, default True.
+
 - ***mg.config.block_prints_location*** : bool
   - If True the source location is printed in block(), default True.
   

{memory_graph-0.3.58 → memory_graph-0.3.59}/memory_graph/__init__.py

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

{memory_graph-0.3.58 → memory_graph-0.3.59}/memory_graph/config.py

@@ -7,6 +7,8 @@
 reopen_viewer = None
 render_filename = None
 
+type_lables = None
+
 block_prints_location = None
 press_enter_message = None
 

{memory_graph-0.3.58 → memory_graph-0.3.59}/memory_graph/config_default.py

@@ -23,7 +23,10 @@ def reset():
     
     """ The default filename to render to. """
     config.render_filename = 'memory_graph.pdf'
-    
+
+    """ Show the type of each node as label. """
+    config.type_labels = True
+
     """ Determines if the filename, line number and functions name is printed on mg.block(). """
     config.block_prints_location = True
 

{memory_graph-0.3.58 → memory_graph-0.3.59}/memory_graph/memory_to_nodes.py

@@ -210,16 +210,20 @@ def build_graph(graphviz_graph, nodes, root_id, id_to_slices):
         if len(new_node_names) > 1:
             graphviz_graph.body.append('subgraph { rank=same; '+ ' -> '.join(new_node_names) + '[weight='+str(config.graph_stability)+', style=invis]; }\n')
 
-    def add_to_graphviz_graph(graphviz_graph, nodes, node, slices, id_to_slices, subgraphed_nodes, depth):
+    def add_to_graphviz_graph(graphviz_graph, nodes, node, slices, id_to_slices):
         """ Adds 'node' to 'graphviz_graph' with its children and edges. """
         html_table = node.get_html_table(nodes, slices, id_to_slices)
         edges = html_table.get_edges()
         color = config_helpers.get_color(node)
         border = 3 if node.is_root() else 1
-        graphviz_graph.node(node.get_name(),
-                            html_table.to_string(border, color),
-                            xlabel=node.get_label(slices))
-        # ------------ edges
+        if config.type_labels:
+            graphviz_graph.node(node.get_name(),
+                                html_table.to_string(border, color),
+                                xlabel=node.get_label(slices))
+        else:
+            graphviz_graph.node(node.get_name(),
+                                html_table.to_string(border, color))
+            # ------------ edges
         for parent,child,dashed in edges:
             graphviz_graph.edge(parent, child+':table', style='dashed' if dashed else 'solid')
 
@@ -239,7 +243,7 @@ def build_graph(graphviz_graph, nodes, root_id, id_to_slices):
                         child_id = id(children[index])
                         build_graph_depth_first(graphviz_graph, nodes, child_id, id_to_slices, nodes_at_depth, subgraphed_nodes, depth+1)
             if not node.is_hidden_node():
-                add_to_graphviz_graph(graphviz_graph, nodes, node, slices, id_to_slices, subgraphed_nodes, depth)
+                add_to_graphviz_graph(graphviz_graph, nodes, node, slices, id_to_slices)
 
     nodes_at_depth = {}
     build_graph_depth_first(graphviz_graph, nodes, root_id, id_to_slices, nodes_at_depth, set(), 0)

{memory_graph-0.3.58 → memory_graph-0.3.59/memory_graph.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memory_graph
-Version: 0.3.58
+Version: 0.3.59
 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
@@ -169,7 +169,7 @@ Learn the right **mental model** to think about Python data. The [Python Data Mo
 
 
 ## Immutable Type ##
-In the code below variable `a` and `b` both reference the same tuple value (4, 3, 2). A tuple is an immutable type and therefore when we change variable `b` its value **cannot** be mutated in place, and thus an automatic copy is made and `a` and `b` reference their own value afterwards.
+In the code below variable `a` and `b` both reference the same tuple value (4, 3, 2). A tuple is an immutable type and therefore when we change variable `b` its value **cannot** be mutated in place, and thus an automatic copy is made and `a` and `b` each reference their own value afterwards.
 
 ```python
 import memory_graph as mg
@@ -203,7 +203,7 @@ mg.render(locals(), 'mutable2.png')
 |:-----------------------------------------------------------:|:-------------------------------------------------------------:|
 | mutable1.png | mutable2.png |
 
-One practical reason why Python makes the distinction between mutable and immutable types is that a value of a mutable type can be large, making it inefficient to copy each time we change it. Immutable values generally don't need to change as much, or are small making copying less of a concern.
+One practical reason why Python makes the distinction between mutable and immutable types is that a value of a mutable type can be large, making it inefficient to copy each time we change it. Values of immutable type generally don't need to change as much, or are small, making copying less of a concern.
 
 ## Copying Values of Mutable Type ##
 Python offers three different "copy" options that we will demonstrate using a nested list:
@@ -666,6 +666,9 @@ Different aspects of memory_graph can be configured. The default configuration c
 - ***mg.config.render_filename*** : str
   - The default filename to render to, default 'memory_graph.pdf'.
 
+- ***mg.config.type_labels*** : bool
+  - If True the type of each node is shown as label, default True.
+
 - ***mg.config.block_prints_location*** : bool
   - If True the source location is printed in block(), default True.
   

{memory_graph-0.3.58 → memory_graph-0.3.59}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "memory_graph"
-version = "0.3.58"
+version = "0.3.59"
 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"}