memory-graph 0.2.1__tar.gz → 0.2.3__tar.gz

{memory_graph-0.2.1 → memory_graph-0.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: memory_graph
-Version: 0.2.1
+Version: 0.2.3
 Summary: Draws a graph of your data to analyze its structure.
 Home-page: https://github.com/bterwijn/memory_graph
 Author: Bas Terwijn
@@ -67,7 +67,7 @@ identical?: True
 ```
 A better way to understand what data is shared is to draw a graph of the data using the [memory_graph](https://pypi.org/project/memory-graph/) package.
 
-# Memory Graph Packge #
+# Memory Graph #
 The [memory_graph](https://pypi.org/project/memory-graph/) package can graph many different data types.
 
 ```python
@@ -131,7 +131,7 @@ The [Python Data Model](https://docs.python.org/3/reference/datamodel.html) make
 In the code below variable `a` and `b` both reference the same `int` value 10. An `int` is an immutable type and therefore when we change variable `a` its value can **not** be mutated in place, and thus a copy is made and `a` and `b` reference a different value afterwards.
 ```python
 import memory_graph
-memory_graph.rewrite_to_node.reduce_reference_children.remove("int") # shows references to 'int'
+memory_graph.config.no_reference_types.pop(int, None) # show references to ints
 
 a = 10
 b = a
@@ -287,7 +287,7 @@ print(f"a:{a} b:{b} c:{c}")
 
 As `a` is of immutable type 'int' and as we call the function with a copy of `c`, only `b` is shared so only `b` is changed in the calling stack frame as reflected in the printed output:
 ```
-a:0 b:[4, 3, 2, 1] c:[4, 3, 2]
+a:10 b:[4, 3, 2, 1] c:[4, 3, 2]
 ```
 
 ### Recursion ###
@@ -488,7 +488,7 @@ Different aspects of memory_graph can be configured. The default configuration i
   - Maps each type to a Slicer. A slicer determines how many elements of a data type are shown in the graph to prevent the graph from getting too big. 'Slicer()' does no slicing, 'Slicer(1,2,3)' shows just 1 element at the beginning, 2 in the middle, and 3 at the end.
 
 ### Temporary Configuration ###
-In addition to the global configuration, a temporary configuration can be set for a single `show()`, `render()`, or `d()` call to change the colors, orientation, and slicer. This example highlights a particular list element in red, gives it a horizontal orientattion, and overwrites the default slicer for lists:
+In addition to the global configuration, a temporary configuration can be set for a single `show()`, `render()`, or `d()` call to change the colors, orientation, and slicer. This example highlights a particular list element in red, gives it a horizontal orientation, and overwrites the default slicer for lists:
 
 ```python
 import memory_graph
@@ -506,7 +506,7 @@ memory_graph.show( locals(),
 ![highlight.png](https://raw.githubusercontent.com/bterwijn/memory_graph/main/images/highlight.png)
 
 ## 6. Extensions ##
-Different extension are available for types from Python packages. 
+Different extensions are available for types from other Python packages. 
 
 ### Numpy ###
 Numpy types `arrray` and `matrix` and `ndarray` can be graphed with the "memory_graph.extension_numpy" extension:
@@ -515,6 +515,7 @@ Numpy types `arrray` and `matrix` and `ndarray` can be graphed with the "memory_
 from memory_graph import d
 import numpy as np
 import memory_graph.extension_numpy
+np.random.seed(0) # use same random numbers each run
 
 array = np.array([1.1, 2, 3, 4, 5])
 matrix = np.matrix([[i*20+j for j in range(20)] for i in range(20)])

{memory_graph-0.2.1 → memory_graph-0.2.3}/README.md

@@ -48,7 +48,7 @@ identical?: True
 ```
 A better way to understand what data is shared is to draw a graph of the data using the [memory_graph](https://pypi.org/project/memory-graph/) package.
 
-# Memory Graph Packge #
+# Memory Graph #
 The [memory_graph](https://pypi.org/project/memory-graph/) package can graph many different data types.
 
 ```python
@@ -112,7 +112,7 @@ The [Python Data Model](https://docs.python.org/3/reference/datamodel.html) make
 In the code below variable `a` and `b` both reference the same `int` value 10. An `int` is an immutable type and therefore when we change variable `a` its value can **not** be mutated in place, and thus a copy is made and `a` and `b` reference a different value afterwards.
 ```python
 import memory_graph
-memory_graph.rewrite_to_node.reduce_reference_children.remove("int") # shows references to 'int'
+memory_graph.config.no_reference_types.pop(int, None) # show references to ints
 
 a = 10
 b = a
@@ -268,7 +268,7 @@ print(f"a:{a} b:{b} c:{c}")
 
 As `a` is of immutable type 'int' and as we call the function with a copy of `c`, only `b` is shared so only `b` is changed in the calling stack frame as reflected in the printed output:
 ```
-a:0 b:[4, 3, 2, 1] c:[4, 3, 2]
+a:10 b:[4, 3, 2, 1] c:[4, 3, 2]
 ```
 
 ### Recursion ###
@@ -469,7 +469,7 @@ Different aspects of memory_graph can be configured. The default configuration i
   - Maps each type to a Slicer. A slicer determines how many elements of a data type are shown in the graph to prevent the graph from getting too big. 'Slicer()' does no slicing, 'Slicer(1,2,3)' shows just 1 element at the beginning, 2 in the middle, and 3 at the end.
 
 ### Temporary Configuration ###
-In addition to the global configuration, a temporary configuration can be set for a single `show()`, `render()`, or `d()` call to change the colors, orientation, and slicer. This example highlights a particular list element in red, gives it a horizontal orientattion, and overwrites the default slicer for lists:
+In addition to the global configuration, a temporary configuration can be set for a single `show()`, `render()`, or `d()` call to change the colors, orientation, and slicer. This example highlights a particular list element in red, gives it a horizontal orientation, and overwrites the default slicer for lists:
 
 ```python
 import memory_graph
@@ -487,7 +487,7 @@ memory_graph.show( locals(),
 ![highlight.png](https://raw.githubusercontent.com/bterwijn/memory_graph/main/images/highlight.png)
 
 ## 6. Extensions ##
-Different extension are available for types from Python packages. 
+Different extensions are available for types from other Python packages. 
 
 ### Numpy ###
 Numpy types `arrray` and `matrix` and `ndarray` can be graphed with the "memory_graph.extension_numpy" extension:
@@ -496,6 +496,7 @@ Numpy types `arrray` and `matrix` and `ndarray` can be graphed with the "memory_
 from memory_graph import d
 import numpy as np
 import memory_graph.extension_numpy
+np.random.seed(0) # use same random numbers each run
 
 array = np.array([1.1, 2, 3, 4, 5])
 matrix = np.matrix([[i*20+j for j in range(20)] for i in range(20)])

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph/Node.py

@@ -15,11 +15,10 @@ class Node:
         children (list): The children of the node.
         size (string): The size of the node to be shown in the graph.
     """
-    def __init__(self, data, children=None, size=None):
+    def __init__(self, data, children=None):
         self.node_id = Node.node_id
         Node.node_id += 1
         self.data = data
-        self.size = size
         self.parent = None
         self.children = children
 
@@ -34,6 +33,18 @@ class Node:
         Return the original data represented by the node.
         """
         return self.data
+    
+    def get_type(self):
+        """
+        Return the type of the data represented by the node.
+        """
+        return type(self.data)
+    
+    def get_type_name(self):
+        """
+        Return the name of the type of the data represented by the node.
+        """
+        return utils.get_type_name(self.data)
 
     def set_parent(self, parent):
         """
@@ -47,12 +58,6 @@ class Node:
         """    
         return self.parent
 
-    def get_size(self):
-        """
-        Return the size of the node to be shown in the graph.
-        """
-        return self.size
-
     def get_children(self):
         """
         Return the children of the node. Initially the children are raw data, but 
@@ -78,17 +83,6 @@ class Node:
             self.fill_html_table(html_table)
         return html_table
     
-    def get_label(self):
-        """
-        Return a label for the node to be shown in the graph next to the HTML table, the size 
-        is included in the label if available.
-        """
-        label = utils.get_type_name(self.data)
-        size = self.get_size()
-        if not size is None:
-            label +=f' ({size})'
-        return label
-    
     # -------------------- Node interface, overriden by subclasses --------------------
 
     def do_backtrack_callback(self):
@@ -109,3 +103,9 @@ class Node:
         Fill the HTML_Table object with each child of the node.
         """
         pass
+
+    def get_label(self):
+        """
+        Return a label for the node to be shown in the graph next to the HTML table.
+        """
+        return self.get_type_name()

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph/Node_Key_Value.py

@@ -37,9 +37,10 @@ class Node_Key_Value(Node):
         """
         #print('Node_Key_Value children:', children)
         hidden_children = [ Node_Hidden(i,list(i)) for i in children ]
+        self.size = len(hidden_children)
         slicer = config_helpers.get_slicer_1d(self, data)
         sliced_children = slicer.slice(hidden_children)
-        super().__init__(data, sliced_children, sliced_children.get_original_length())
+        super().__init__(data, sliced_children)
         
     def transform(self, fun):
         """
@@ -91,3 +92,12 @@ class Node_Key_Value(Node):
             if value is not None:
                 key_value = value.get_children() # add the key-value pair of Hidden_Node, not the tuple
                 html_table.add_entry(self, key_value[1])
+
+    def get_label(self):
+        """
+        Return a label for the node to be shown in the graph next to the HTML table.
+        """
+        if self.get_children().has_all_data():
+            return f'{self.get_type_name()}'
+        return f'{self.get_type_name()} {self.size}'
+    

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph/Node_Linear.py

@@ -16,7 +16,7 @@ class Node_Linear(Node):
         """
         slicer = config_helpers.get_slicer_1d(self, data)
         sliced_children = slicer.slice(children)
-        super().__init__(data, sliced_children, sliced_children.get_original_length())
+        super().__init__(data, sliced_children)
 
     def transform(self, fun):
         """

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph/Node_Table.py

@@ -38,7 +38,7 @@ class Node_Table(Node):
 
         self.row_names = row_names
         self.column_names = column_names
-        super().__init__(data, sliced_children, f'{self.data_height}⨯{self.data_width}')
+        super().__init__(data, sliced_children)
 
     def transform(self, fun):
         """
@@ -82,3 +82,9 @@ class Node_Table(Node):
                         html_table.add_entry(self, value)
                 html_table.add_new_line()
 
+    def get_label(self):
+        """
+        Return a label for the node to be shown in the graph next to the HTML table.
+        """
+        return f'{self.get_type_name()} {self.data_height}⨯{self.data_width}'
+    

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph/Sliced.py

@@ -108,4 +108,7 @@ class Sliced:
     def last_slice_empty(self):
         """ Return True if the last slice of the Sliced object is empty. """
         return len(self.slices) > 0 and len(self.slices[-1].data) == 0
-    
+    
+    def has_all_data(self):
+        """ Return True if the Sliced object has all the data. """
+        return len(self.slices) == 1 and len(self.slices[0].data) == self.original_length

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph/__init__.py

@@ -6,7 +6,7 @@ import memory_graph.utils as utils
 import inspect
 import sys
 
-__version__ = "0.2.01"
+__version__ = "0.2.03"
 __author__ = 'Bas Terwijn'
 
 log_file=sys.stdout

{memory_graph-0.2.1 → memory_graph-0.2.3}/memory_graph.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: memory-graph
-Version: 0.2.1
+Version: 0.2.3
 Summary: Draws a graph of your data to analyze its structure.
 Home-page: https://github.com/bterwijn/memory_graph
 Author: Bas Terwijn
@@ -67,7 +67,7 @@ identical?: True
 ```
 A better way to understand what data is shared is to draw a graph of the data using the [memory_graph](https://pypi.org/project/memory-graph/) package.
 
-# Memory Graph Packge #
+# Memory Graph #
 The [memory_graph](https://pypi.org/project/memory-graph/) package can graph many different data types.
 
 ```python
@@ -131,7 +131,7 @@ The [Python Data Model](https://docs.python.org/3/reference/datamodel.html) make
 In the code below variable `a` and `b` both reference the same `int` value 10. An `int` is an immutable type and therefore when we change variable `a` its value can **not** be mutated in place, and thus a copy is made and `a` and `b` reference a different value afterwards.
 ```python
 import memory_graph
-memory_graph.rewrite_to_node.reduce_reference_children.remove("int") # shows references to 'int'
+memory_graph.config.no_reference_types.pop(int, None) # show references to ints
 
 a = 10
 b = a
@@ -287,7 +287,7 @@ print(f"a:{a} b:{b} c:{c}")
 
 As `a` is of immutable type 'int' and as we call the function with a copy of `c`, only `b` is shared so only `b` is changed in the calling stack frame as reflected in the printed output:
 ```
-a:0 b:[4, 3, 2, 1] c:[4, 3, 2]
+a:10 b:[4, 3, 2, 1] c:[4, 3, 2]
 ```
 
 ### Recursion ###
@@ -488,7 +488,7 @@ Different aspects of memory_graph can be configured. The default configuration i
   - Maps each type to a Slicer. A slicer determines how many elements of a data type are shown in the graph to prevent the graph from getting too big. 'Slicer()' does no slicing, 'Slicer(1,2,3)' shows just 1 element at the beginning, 2 in the middle, and 3 at the end.
 
 ### Temporary Configuration ###
-In addition to the global configuration, a temporary configuration can be set for a single `show()`, `render()`, or `d()` call to change the colors, orientation, and slicer. This example highlights a particular list element in red, gives it a horizontal orientattion, and overwrites the default slicer for lists:
+In addition to the global configuration, a temporary configuration can be set for a single `show()`, `render()`, or `d()` call to change the colors, orientation, and slicer. This example highlights a particular list element in red, gives it a horizontal orientation, and overwrites the default slicer for lists:
 
 ```python
 import memory_graph
@@ -506,7 +506,7 @@ memory_graph.show( locals(),
 ![highlight.png](https://raw.githubusercontent.com/bterwijn/memory_graph/main/images/highlight.png)
 
 ## 6. Extensions ##
-Different extension are available for types from Python packages. 
+Different extensions are available for types from other Python packages. 
 
 ### Numpy ###
 Numpy types `arrray` and `matrix` and `ndarray` can be graphed with the "memory_graph.extension_numpy" extension:
@@ -515,6 +515,7 @@ Numpy types `arrray` and `matrix` and `ndarray` can be graphed with the "memory_
 from memory_graph import d
 import numpy as np
 import memory_graph.extension_numpy
+np.random.seed(0) # use same random numbers each run
 
 array = np.array([1.1, 2, 3, 4, 5])
 matrix = np.matrix([[i*20+j for j in range(20)] for i in range(20)])

{memory_graph-0.2.1 → memory_graph-0.2.3}/setup.py

@@ -7,7 +7,7 @@ long_description_from_readme = (this_directory / "README.md").read_text()
 
 setup(
     name = 'memory_graph',
-    version = '0.2.01',
+    version = '0.2.03',
     description = 'Draws a graph of your data to analyze its structure.',
     long_description = long_description_from_readme,
     long_description_content_type = 'text/markdown',