memory-graph 0.3.79__tar.gz → 0.3.80__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {memory_graph-0.3.79 → memory_graph-0.3.80}/PKG-INFO +9 -2
- {memory_graph-0.3.79 → memory_graph-0.3.80}/README.md +8 -1
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/__init__.py +2 -2
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/config_default.py +5 -1
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph.egg-info/PKG-INFO +9 -2
- {memory_graph-0.3.79 → memory_graph-0.3.80}/pyproject.toml +1 -1
- {memory_graph-0.3.79 → memory_graph-0.3.80}/LICENSE.txt +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/call_stack.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/config.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/config_helpers.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/extension_numpy.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/extension_pandas.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/extension_torch.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/html_table.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/list_view.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/memory_to_nodes.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/node_base.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/node_key_value.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/node_leaf.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/node_linear.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/node_table.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/sequence.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/slicer.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/slices.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/slices_iterator.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/slices_table_iterator.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_max_graph_depth.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_memory_graph.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_memory_to_nodes.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_sequence.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_slicer.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_slices.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/test_slices_iterator.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph/utils.py +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph.egg-info/SOURCES.txt +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph.egg-info/dependency_links.txt +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph.egg-info/requires.txt +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/memory_graph.egg-info/top_level.txt +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/setup.cfg +0 -0
- {memory_graph-0.3.79 → memory_graph-0.3.80}/setup.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: memory_graph
|
|
3
|
-
Version: 0.3.
|
|
3
|
+
Version: 0.3.80
|
|
4
4
|
Summary: Teaching tool and debugging aid in context of references, mutable data types, and shallow and deep copy.
|
|
5
5
|
Author-email: Bas Terwijn <bterwijn@gmail.com>
|
|
6
6
|
License-Expression: BSD-2-Clause
|
|
@@ -690,7 +690,7 @@ for i in range(n):
|
|
|
690
690
|
Here we show values being inserted in a Binary Tree in Visual Studio Code. When inserting the last value '29' we "Step Into" the code to show the recursive implementation.
|
|
691
691
|

|
|
692
692
|
|
|
693
|
-
See it in the [Memory Graph Web Debugger](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/bin_tree.py×tep=0.2&play) or see the more advanced [Multiway Tree](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/multiway_tree.py&breakpoints=
|
|
693
|
+
See it in the [Memory Graph Web Debugger](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/bin_tree.py×tep=0.2&play) or see the more advanced [Multiway Tree](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/multiway_tree.py&breakpoints=20,34&continues=1×tep=0.2&play) with more than two children per node, making the tree less deep and more efficient.
|
|
694
694
|
|
|
695
695
|
## Hash Set ##
|
|
696
696
|
```python
|
|
@@ -1046,6 +1046,13 @@ Different aspects of memory_graph can be configured. The default configuration c
|
|
|
1046
1046
|
- ***mg.config.fontsize*** : str
|
|
1047
1047
|
- The font size used in the graph, default '14'.
|
|
1048
1048
|
|
|
1049
|
+
## Functions ##
|
|
1050
|
+
|
|
1051
|
+
- **mg.dark_mode(b: bool = None)**
|
|
1052
|
+
- Set dark mode to 'True' or 'False', or 'None' to toggle.
|
|
1053
|
+
|
|
1054
|
+
- **mg.transparent_background(b: bool = None)**
|
|
1055
|
+
- Set transparent_background to 'True' or 'False', or 'None' to toggle.
|
|
1049
1056
|
|
|
1050
1057
|
## Simplified Graph ##
|
|
1051
1058
|
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.
|
|
@@ -670,7 +670,7 @@ for i in range(n):
|
|
|
670
670
|
Here we show values being inserted in a Binary Tree in Visual Studio Code. When inserting the last value '29' we "Step Into" the code to show the recursive implementation.
|
|
671
671
|

|
|
672
672
|
|
|
673
|
-
See it in the [Memory Graph Web Debugger](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/bin_tree.py×tep=0.2&play) or see the more advanced [Multiway Tree](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/multiway_tree.py&breakpoints=
|
|
673
|
+
See it in the [Memory Graph Web Debugger](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/bin_tree.py×tep=0.2&play) or see the more advanced [Multiway Tree](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/multiway_tree.py&breakpoints=20,34&continues=1×tep=0.2&play) with more than two children per node, making the tree less deep and more efficient.
|
|
674
674
|
|
|
675
675
|
## Hash Set ##
|
|
676
676
|
```python
|
|
@@ -1026,6 +1026,13 @@ Different aspects of memory_graph can be configured. The default configuration c
|
|
|
1026
1026
|
- ***mg.config.fontsize*** : str
|
|
1027
1027
|
- The font size used in the graph, default '14'.
|
|
1028
1028
|
|
|
1029
|
+
## Functions ##
|
|
1030
|
+
|
|
1031
|
+
- **mg.dark_mode(b: bool = None)**
|
|
1032
|
+
- Set dark mode to 'True' or 'False', or 'None' to toggle.
|
|
1033
|
+
|
|
1034
|
+
- **mg.transparent_background(b: bool = None)**
|
|
1035
|
+
- Set transparent_background to 'True' or 'False', or 'None' to toggle.
|
|
1029
1036
|
|
|
1030
1037
|
## Simplified Graph ##
|
|
1031
1038
|
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.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
# Copyright (c) 2023, Bas Terwijn.
|
|
3
3
|
# SPDX-License-Identifier: BSD-2-Clause
|
|
4
4
|
|
|
5
|
-
__version__ = "0.3.
|
|
5
|
+
__version__ = "0.3.80"
|
|
6
6
|
__author__ = 'Bas Terwijn'
|
|
7
7
|
|
|
8
8
|
import memory_graph.memory_to_nodes as memory_to_nodes
|
|
@@ -26,7 +26,7 @@ if not hasattr(builtins, "mg"):
|
|
|
26
26
|
builtins.mg = mg
|
|
27
27
|
|
|
28
28
|
# re-exports for shorter names
|
|
29
|
-
from .config_default import dark_mode, transparent_background
|
|
29
|
+
from .config_default import dark_mode, transparent_background, set_colors
|
|
30
30
|
from .slicer import Slicer
|
|
31
31
|
from .node_leaf import Node_Leaf
|
|
32
32
|
from .node_linear import Node_Linear
|
|
@@ -77,7 +77,11 @@ type_to_color_dark = {
|
|
|
77
77
|
BaseException : "#a52e37",
|
|
78
78
|
}
|
|
79
79
|
|
|
80
|
-
def set_colors(dark, transparent):
|
|
80
|
+
def set_colors(dark=None, transparent=None):
|
|
81
|
+
if dark is None:
|
|
82
|
+
dark = config.color_mode_dark
|
|
83
|
+
if transparent is None:
|
|
84
|
+
transparent = config.transparent_background
|
|
81
85
|
if dark:
|
|
82
86
|
config.foreground_color = foreground_color_dark
|
|
83
87
|
config.index_color = index_color_dark
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: memory_graph
|
|
3
|
-
Version: 0.3.
|
|
3
|
+
Version: 0.3.80
|
|
4
4
|
Summary: Teaching tool and debugging aid in context of references, mutable data types, and shallow and deep copy.
|
|
5
5
|
Author-email: Bas Terwijn <bterwijn@gmail.com>
|
|
6
6
|
License-Expression: BSD-2-Clause
|
|
@@ -690,7 +690,7 @@ for i in range(n):
|
|
|
690
690
|
Here we show values being inserted in a Binary Tree in Visual Studio Code. When inserting the last value '29' we "Step Into" the code to show the recursive implementation.
|
|
691
691
|

|
|
692
692
|
|
|
693
|
-
See it in the [Memory Graph Web Debugger](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/bin_tree.py×tep=0.2&play) or see the more advanced [Multiway Tree](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/multiway_tree.py&breakpoints=
|
|
693
|
+
See it in the [Memory Graph Web Debugger](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/bin_tree.py×tep=0.2&play) or see the more advanced [Multiway Tree](https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/multiway_tree.py&breakpoints=20,34&continues=1×tep=0.2&play) with more than two children per node, making the tree less deep and more efficient.
|
|
694
694
|
|
|
695
695
|
## Hash Set ##
|
|
696
696
|
```python
|
|
@@ -1046,6 +1046,13 @@ Different aspects of memory_graph can be configured. The default configuration c
|
|
|
1046
1046
|
- ***mg.config.fontsize*** : str
|
|
1047
1047
|
- The font size used in the graph, default '14'.
|
|
1048
1048
|
|
|
1049
|
+
## Functions ##
|
|
1050
|
+
|
|
1051
|
+
- **mg.dark_mode(b: bool = None)**
|
|
1052
|
+
- Set dark mode to 'True' or 'False', or 'None' to toggle.
|
|
1053
|
+
|
|
1054
|
+
- **mg.transparent_background(b: bool = None)**
|
|
1055
|
+
- Set transparent_background to 'True' or 'False', or 'None' to toggle.
|
|
1049
1056
|
|
|
1050
1057
|
## Simplified Graph ##
|
|
1051
1058
|
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.
|
|
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "memory_graph"
|
|
7
|
-
version = "0.3.
|
|
7
|
+
version = "0.3.80"
|
|
8
8
|
description = "Teaching tool and debugging aid in context of references, mutable data types, and shallow and deep copy."
|
|
9
9
|
authors = [
|
|
10
10
|
{name = "Bas Terwijn", email = "bterwijn@gmail.com"}
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|