mainsequence 3.3.8__tar.gz → 3.4.1__tar.gz

{mainsequence-3.3.8 → mainsequence-3.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 3.3.8
+Version: 3.4.1
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License: MainSequence GmbH SDK License Agreement
@@ -87,6 +87,7 @@ Requires-Dist: duckdb
 Requires-Dist: plotly
 Requires-Dist: typer
 Requires-Dist: QuantLib
+Requires-Dist: streamlit
 Dynamic: license-file
 
 <p align="center">
@@ -97,12 +98,63 @@ Dynamic: license-file
 
 
 
-The **Main Sequence Python SDK** is a powerful set of client libraries designed to facilitate interaction with Main Sequence systems using Python. 
+The Main Sequence Python SDK is a high-performance client library that enables seamless integration with the Main Sequence platform. 
+It provides a unified and intuitive interface for interacting with data, compute, and intelligence services across the platform.
 
-**We strongly** encourage you to go through our examples. 
-We have built the examples as individual Jupyter notebooks that explain the SDK through use cases. 
-Since most platform usage involves a combination of operations, this is the most intuitive way to learn about Main Sequence.
+Main Sequence functions as a centralized engine for data intelligence—integrating information from diverse data sources and systems
+while abstracting away the complexity of underlying storage layers. This allows quants, researchers, analysts,
+and engineers to focus on the data-generating process itself, while Main Sequence optimizes all CRUD operations and manages 
+the mapping between logical data structures and physical storage.
 
+The Main Sequence SDK is also a foundational component of all Main Sequence Platform projects. 
+It acts as the backbone for automation, process orchestration, and the rapid development of dashboards,
+data nodes, and agentic tools built on top of the platform.
 
+---
+
+## Developing with the Main Sequence SDK & Platform
+To make it easy to work on Main Sequence projects from your local environment, you have two options:
+
+1. **Use the MainSequence CLI directly in your terminal**, or  
+2. **Use the Main Sequence VS Code extension** (recommended if you already work in VS Code).
+
+The VS Code extension provides a more visual, editor-integrated workflow on top of what the CLI offers.
+
+
+### Visual Studio Code Extension
+
+1. **Open the Extensions view in VS Code**
+
+   - **macOS:** Press `Cmd` + `Shift` + `X`  
+   - **Windows/Linux:** Press `Ctrl` + `Shift` + `X`  
+   - Or click the **Extensions** icon in the Activity Bar on the left side of the window.
+
+2. **Search for the extension**
+
+   In the Extensions search box, type Main Sequence and press Enter.:
+
+
+![img.png](/docs/img/vs_code_extension.png)
+
+### MainSequence CLI
+
+MainSequence CLI is a small helper tool to:
+
+- Authenticate against the Main Sequence backend
+- Manage your local project checkouts (clone, open, delete)
+- Set up SSH deploy keys for project repos
+- Generate and maintain a `.env` file with project-specific tokens and endpoints
+- Build & run your project in Docker (via `uv` + `docker`)
+- Bundle and copy AI/LLM instruction markdowns to the clipboard
+
+The CLI is implemented with [Typer](https://typer.tiangolo.com/) and exposes a `mainsequence` command.
 
 ---
+
+## Installation & Invocation
+
+How you install the CLI depends on how this repository is packaged, but assuming it’s installed in your environment and provides the `mainsequence` entry point:
+
+```bash
+# General form
+mainsequence --help

mainsequence-3.4.1/README.md

@@ -0,0 +1,68 @@
+<p align="center">
+<img src="https://main-sequence.app/static/media/logos/MS_logo_long_black.png" alt="Main Sequence Logo" width="500"/>
+</p>
+
+# Main Sequence Python SDK
+
+
+
+The Main Sequence Python SDK is a high-performance client library that enables seamless integration with the Main Sequence platform. 
+It provides a unified and intuitive interface for interacting with data, compute, and intelligence services across the platform.
+
+Main Sequence functions as a centralized engine for data intelligence—integrating information from diverse data sources and systems
+while abstracting away the complexity of underlying storage layers. This allows quants, researchers, analysts,
+and engineers to focus on the data-generating process itself, while Main Sequence optimizes all CRUD operations and manages 
+the mapping between logical data structures and physical storage.
+
+The Main Sequence SDK is also a foundational component of all Main Sequence Platform projects. 
+It acts as the backbone for automation, process orchestration, and the rapid development of dashboards,
+data nodes, and agentic tools built on top of the platform.
+
+---
+
+## Developing with the Main Sequence SDK & Platform
+To make it easy to work on Main Sequence projects from your local environment, you have two options:
+
+1. **Use the MainSequence CLI directly in your terminal**, or  
+2. **Use the Main Sequence VS Code extension** (recommended if you already work in VS Code).
+
+The VS Code extension provides a more visual, editor-integrated workflow on top of what the CLI offers.
+
+
+### Visual Studio Code Extension
+
+1. **Open the Extensions view in VS Code**
+
+   - **macOS:** Press `Cmd` + `Shift` + `X`  
+   - **Windows/Linux:** Press `Ctrl` + `Shift` + `X`  
+   - Or click the **Extensions** icon in the Activity Bar on the left side of the window.
+
+2. **Search for the extension**
+
+   In the Extensions search box, type Main Sequence and press Enter.:
+
+
+![img.png](/docs/img/vs_code_extension.png)
+
+### MainSequence CLI
+
+MainSequence CLI is a small helper tool to:
+
+- Authenticate against the Main Sequence backend
+- Manage your local project checkouts (clone, open, delete)
+- Set up SSH deploy keys for project repos
+- Generate and maintain a `.env` file with project-specific tokens and endpoints
+- Build & run your project in Docker (via `uv` + `docker`)
+- Bundle and copy AI/LLM instruction markdowns to the clipboard
+
+The CLI is implemented with [Typer](https://typer.tiangolo.com/) and exposes a `mainsequence` command.
+
+---
+
+## Installation & Invocation
+
+How you install the CLI depends on how this repository is packaged, but assuming it’s installed in your environment and provides the `mainsequence` entry point:
+
+```bash
+# General form
+mainsequence --help

{mainsequence-3.3.8 → mainsequence-3.4.1}/mainsequence/cli/cli.py

@@ -752,94 +752,6 @@ def project_set_up_locally(
         typer.echo("Public key copied to clipboard.")
 
 
-@app.command("build_and_run")
-def build_and_run(
-    dockerfile: str | None = typer.Argument(
-        None, help="Path to Dockerfile to build & run. If omitted, only lock & export requirements."
-    )
-):
-    """
-    - uv lock
-    - uv export --format requirements --no-dev --hashes > requirements.txt
-    - If DOCKERFILE argument is given: docker build -f DOCKERFILE . && docker run IMAGE
-    """
-
-    # ----- sanity checks for uv + project files -----
-    if shutil.which("uv") is None:
-        typer.secho("uv is not installed. Install it with: pip install uv", fg=typer.colors.RED)
-        raise typer.Exit(1)
-
-    if not pathlib.Path("pyproject.toml").exists():
-        typer.secho(f"pyproject.toml not found in {pathlib.Path.cwd()}", fg=typer.colors.RED)
-        raise typer.Exit(1)
-
-    # ----- 1) solve and lock -----
-    typer.secho("Running: uv lock", fg=typer.colors.BLUE)
-    p = subprocess.run(["uv", "lock"])
-    if p.returncode != 0:
-        typer.secho("uv lock failed.", fg=typer.colors.RED)
-        raise typer.Exit(p.returncode)
-
-    # ----- 2) export pinned, hashed requirements -----
-    typer.secho("Exporting hashed requirements to requirements.txt", fg=typer.colors.BLUE)
-    p = subprocess.run(
-        ["uv", "export", "--format", "requirements", "--no-dev", "--hashes"],
-        capture_output=True,
-        text=True,
-    )
-    if p.returncode != 0:
-        typer.secho("uv export failed:", fg=typer.colors.RED)
-        if p.stderr:
-            typer.echo(p.stderr.strip())
-        raise typer.Exit(p.returncode)
-
-    pathlib.Path("requirements.txt").write_text(p.stdout, encoding="utf-8")
-    typer.secho("requirements.txt written.", fg=typer.colors.GREEN)
-
-    # ----- 3) optional Docker build + run -----
-    if dockerfile is None:
-        typer.secho("No Dockerfile provided; skipping Docker build/run.", fg=typer.colors.BLUE)
-        return
-
-    df_path = pathlib.Path(dockerfile)
-    if not df_path.exists():
-        typer.secho(f"Dockerfile not found: {dockerfile}", fg=typer.colors.RED)
-        raise typer.Exit(1)
-
-    if shutil.which("docker") is None:
-        typer.secho("Docker CLI is not installed or not on PATH.", fg=typer.colors.RED)
-        raise typer.Exit(1)
-
-    # Image name: directory-name + '-img' (overridable via env IMAGE_NAME)
-    cwd_name = pathlib.Path.cwd().name
-    safe_name = re.sub(r"[^a-z0-9_.-]+", "-", cwd_name.lower())
-    image_name = os.environ.get("IMAGE_NAME", f"{safe_name}-img")
-
-    # Tag: short git sha if available, else timestamp (overridable via env TAG)
-    tag = os.environ.get("TAG")
-    if not tag:
-        try:
-            tag = subprocess.check_output(
-                ["git", "rev-parse", "--short", "HEAD"], text=True
-            ).strip()
-        except Exception:
-            tag = time.strftime("%Y%m%d%H%M%S")
-
-    image_ref = f"{image_name}:{tag}"
-
-    typer.secho(f"Building Docker image: {image_ref}", fg=typer.colors.BLUE)
-    build = subprocess.run(["docker", "build", "-f", str(df_path), "-t", image_ref, "."])
-    if build.returncode != 0:
-        typer.secho("docker build failed.", fg=typer.colors.RED)
-        raise typer.Exit(build.returncode)
-
-    typer.secho(f"Running container: {image_ref}", fg=typer.colors.BLUE)
-    try:
-        # interactive by default; relies on your ENTRYPOINT
-        subprocess.check_call(["docker", "run", "--rm", "-it", image_ref])
-    except subprocess.CalledProcessError as e:
-        typer.secho(f"docker run failed (exit {e.returncode}).", fg=typer.colors.RED)
-        raise typer.Exit(e.returncode)
 
 
 @app.command("copy-llm-instructions")

{mainsequence-3.3.8 → mainsequence-3.4.1}/mainsequence/client/models_tdag.py

@@ -1066,40 +1066,52 @@ class DataNodeStorage(BasePydanticModel, BaseObjectOrm):
         df = df.set_index(stc.index_names)
         return df
 
-
-
-    def get_data_between_dates_from_api(
-        self,
-        start_date: datetime.datetime = None,
-        end_date: datetime.datetime = None,
-        great_or_equal: bool = None,
-        less_or_equal: bool = None,
-        unique_identifier_list: list = None,
-        columns: list = None,
-        unique_identifier_range_map: None | UniqueIdentifierRangeMap = None,
-        column_range_descriptor: None | UniqueIdentifierRangeMap = None,
-    ):
-        """Helper function to make a single batch request (or multiple paged requests if next_offset)."""
+    @classmethod
+    def _get_data_between_dates_common(
+            cls,
+            url: str,
+            start_date: datetime.datetime = None,
+            end_date: datetime.datetime = None,
+            great_or_equal: bool = None,
+            less_or_equal: bool = None,
+            unique_identifier_list: list = None,
+            columns: list = None,
+            unique_identifier_range_map: None | UniqueIdentifierRangeMap = None,
+            column_range_descriptor: None | UniqueIdentifierRangeMap = None,
+            node_identifier: str | None = None,
+    ) -> pd.DataFrame:
+        """Internal shared implementation for fetching data between dates."""
 
         def fetch_one_batch(chunk_range_map):
             all_results_chunk = []
             offset = 0
+
             while True:
-                payload = {
-                    "json": {
-                        "start_date": start_date.timestamp() if start_date else None,
-                        "end_date": end_date.timestamp() if end_date else None,
-                        "great_or_equal": great_or_equal,
-                        "less_or_equal": less_or_equal,
-                        "unique_identifier_list": unique_identifier_list,
-                        "columns": columns,
-                        "offset": offset,  # pagination offset
-                        "unique_identifier_range_map": chunk_range_map,
-                    }
+                payload_json = {
+                    "start_date": start_date.timestamp() if start_date else None,
+                    "end_date": end_date.timestamp() if end_date else None,
+                    "great_or_equal": great_or_equal,
+                    "less_or_equal": less_or_equal,
+                    "unique_identifier_list": unique_identifier_list,
+                    "columns": columns,
+                    "offset": offset,  # pagination offset
+                    "unique_identifier_range_map": chunk_range_map,
+                    # "column_range_descriptor": column_range_descriptor,  # if/when needed
                 }
 
+                if node_identifier is not None:
+                    payload_json["node_identifier"] = node_identifier
+
+                payload = {"json": payload_json}
+
                 # Perform the POST request
-                r = make_request(s=s, loaders=self.LOADERS, payload=payload, r_type="POST", url=url)
+                r = make_request(
+                    s=s,
+                    loaders=cls.LOADERS,
+                    payload=payload,
+                    r_type="POST",
+                    url=url,
+                )
                 if r.status_code != 200:
                     logger.warning(f"Error in request: {r.text}")
                     return []
@@ -1119,28 +1131,34 @@ class DataNodeStorage(BasePydanticModel, BaseObjectOrm):
 
             return all_results_chunk
 
-        s = self.build_session()
-        url = self.get_object_url() + f"/{self.id}/get_data_between_dates_from_remote/"
+        s = cls.build_session()
 
+        # Deep copy & convert date fields in unique_identifier_range_map
         unique_identifier_range_map = copy.deepcopy(unique_identifier_range_map)
         if unique_identifier_range_map is not None:
             for _, date_info in unique_identifier_range_map.items():
                 # Convert start_date if present
                 if "start_date" in date_info and isinstance(
-                    date_info["start_date"], datetime.datetime
+                        date_info["start_date"], datetime.datetime
                 ):
-                    date_info["start_date"] = int(date_info["start_date"].timestamp())
+                    date_info["start_date"] = int(
+                        date_info["start_date"].timestamp()
+                    )
 
                 # Convert end_date if present
-                if "end_date" in date_info and isinstance(date_info["end_date"], datetime.datetime):
-                    date_info["end_date"] = int(date_info["end_date"].timestamp())
+                if "end_date" in date_info and isinstance(
+                        date_info["end_date"], datetime.datetime
+                ):
+                    date_info["end_date"] = int(
+                        date_info["end_date"].timestamp()
+                    )
 
         all_results = []
         if unique_identifier_range_map:
             keys = list(unique_identifier_range_map.keys())
             chunk_size = 100
             for start_idx in range(0, len(keys), chunk_size):
-                key_chunk = keys[start_idx : start_idx + chunk_size]
+                key_chunk = keys[start_idx: start_idx + chunk_size]
 
                 # Build sub-dictionary for this chunk
                 chunk_map = {k: unique_identifier_range_map[k] for k in key_chunk}
@@ -1155,6 +1173,65 @@ class DataNodeStorage(BasePydanticModel, BaseObjectOrm):
 
         return pd.DataFrame(all_results)
 
+    def get_data_between_dates_from_api(
+            self,
+            start_date: datetime.datetime = None,
+            end_date: datetime.datetime = None,
+            great_or_equal: bool = None,
+            less_or_equal: bool = None,
+            unique_identifier_list: list = None,
+            columns: list = None,
+            unique_identifier_range_map: None | UniqueIdentifierRangeMap = None,
+            column_range_descriptor: None | UniqueIdentifierRangeMap = None,
+    ):
+        """Public helper for /{id}/get_data_between_dates_from_remote/."""
+        url = self.get_object_url() + f"/{self.id}/get_data_between_dates_from_remote/"
+
+        return self._get_data_between_dates_common(
+            url=url,
+            start_date=start_date,
+            end_date=end_date,
+            great_or_equal=great_or_equal,
+            less_or_equal=less_or_equal,
+            unique_identifier_list=unique_identifier_list,
+            columns=columns,
+            unique_identifier_range_map=unique_identifier_range_map,
+            column_range_descriptor=column_range_descriptor,
+            node_identifier=None,
+        )
+
+    @classmethod
+    def get_data_between_dates_from_node_identifier(
+            cls,
+            node_identifier: str,
+            start_date: datetime.datetime = None,
+            end_date: datetime.datetime = None,
+            great_or_equal: bool = None,
+            less_or_equal: bool = None,
+            unique_identifier_list: list = None,
+            columns: list = None,
+            unique_identifier_range_map: None | UniqueIdentifierRangeMap = None,
+            column_range_descriptor: None | UniqueIdentifierRangeMap = None,
+    ):
+        """
+        Same behaviour as get_data_between_dates_from_api,
+        but calls the node-identifier endpoint and includes node_identifier in payload.
+        """
+        url = cls.get_object_url() + "/get_data_between_dates_from_node_identifier/"
+
+        return cls._get_data_between_dates_common(
+            url=url,
+            start_date=start_date,
+            end_date=end_date,
+            great_or_equal=great_or_equal,
+            less_or_equal=less_or_equal,
+            unique_identifier_list=unique_identifier_list,
+            columns=columns,
+            unique_identifier_range_map=unique_identifier_range_map,
+            column_range_descriptor=column_range_descriptor,
+            node_identifier=node_identifier,
+        )
+
 
 class Scheduler(BasePydanticModel, BaseObjectOrm):
     id: int | None = None

{mainsequence-3.3.8 → mainsequence-3.4.1}/mainsequence/tdag/data_nodes/run_operations.py

@@ -214,7 +214,7 @@ class UpdateRunner:
         # Check that the time index is a UTC datetime
         time_index = df.index.get_level_values(0)
         if not pd.api.types.is_datetime64_ns_dtype(time_index) or str(time_index.tz) != str(
-            datetime.timezone.utc
+            datetime.UTC
         ):
             raise TypeError(f"Time index must be datetime64[ns, UTC], but found {time_index.dtype}")
 
@@ -249,11 +249,9 @@ class UpdateRunner:
         # 2. Execute the core data calculation
         with tracer.start_as_current_span("Update Calculation") as update_span:
 
-            # Add specific log message for the initial run
-            if not self.ts.update_statistics:
-                self.logger.debug(f"Performing first-time update for {self.ts}...")
-            else:
-                self.logger.debug(f"Calculating update for {self.ts}...")
+
+
+            self.logger.debug(f"Calculating update for {self.ts}...")
 
             try:
                 # Call the business logic defined on the DataNode class
@@ -295,7 +293,11 @@ class UpdateRunner:
                 self.logger.exception("Failed during update calculation or persistence.")
                 update_span.set_status(Status(StatusCode.ERROR, description=str(e)))
                 raise e
-        return tmp_df
+            finally:
+                self.ts.local_persist_manager.synchronize_data_node_update(None)
+                us = self.ts.local_persist_manager.get_update_statistics_for_table()
+                self.ts.update_statistics = us
+
 
     @tracer.start_as_current_span("UpdateRunner._verify_tree_is_updated")
     def _verify_tree_is_updated(
@@ -474,10 +476,6 @@ class UpdateRunner:
                     raise e  # Re-raise to halt the entire process on failure
 
         # refresh update statistics of direct dependencies
-        # for edge case of multicolumn self update
-        self.ts.local_persist_manager.synchronize_data_node_update(None)
-        us = self.ts.local_persist_manager.get_update_statistics_for_table()
-        self.ts.update_statistics = us
 
         refresh_update_statistics_of_deps(self.ts)
 

{mainsequence-3.3.8 → mainsequence-3.4.1}/mainsequence.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 3.3.8
+Version: 3.4.1
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License: MainSequence GmbH SDK License Agreement
@@ -87,6 +87,7 @@ Requires-Dist: duckdb
 Requires-Dist: plotly
 Requires-Dist: typer
 Requires-Dist: QuantLib
+Requires-Dist: streamlit
 Dynamic: license-file
 
 <p align="center">
@@ -97,12 +98,63 @@ Dynamic: license-file
 
 
 
-The **Main Sequence Python SDK** is a powerful set of client libraries designed to facilitate interaction with Main Sequence systems using Python. 
+The Main Sequence Python SDK is a high-performance client library that enables seamless integration with the Main Sequence platform. 
+It provides a unified and intuitive interface for interacting with data, compute, and intelligence services across the platform.
 
-**We strongly** encourage you to go through our examples. 
-We have built the examples as individual Jupyter notebooks that explain the SDK through use cases. 
-Since most platform usage involves a combination of operations, this is the most intuitive way to learn about Main Sequence.
+Main Sequence functions as a centralized engine for data intelligence—integrating information from diverse data sources and systems
+while abstracting away the complexity of underlying storage layers. This allows quants, researchers, analysts,
+and engineers to focus on the data-generating process itself, while Main Sequence optimizes all CRUD operations and manages 
+the mapping between logical data structures and physical storage.
 
+The Main Sequence SDK is also a foundational component of all Main Sequence Platform projects. 
+It acts as the backbone for automation, process orchestration, and the rapid development of dashboards,
+data nodes, and agentic tools built on top of the platform.
 
+---
+
+## Developing with the Main Sequence SDK & Platform
+To make it easy to work on Main Sequence projects from your local environment, you have two options:
+
+1. **Use the MainSequence CLI directly in your terminal**, or  
+2. **Use the Main Sequence VS Code extension** (recommended if you already work in VS Code).
+
+The VS Code extension provides a more visual, editor-integrated workflow on top of what the CLI offers.
+
+
+### Visual Studio Code Extension
+
+1. **Open the Extensions view in VS Code**
+
+   - **macOS:** Press `Cmd` + `Shift` + `X`  
+   - **Windows/Linux:** Press `Ctrl` + `Shift` + `X`  
+   - Or click the **Extensions** icon in the Activity Bar on the left side of the window.
+
+2. **Search for the extension**
+
+   In the Extensions search box, type Main Sequence and press Enter.:
+
+
+![img.png](/docs/img/vs_code_extension.png)
+
+### MainSequence CLI
+
+MainSequence CLI is a small helper tool to:
+
+- Authenticate against the Main Sequence backend
+- Manage your local project checkouts (clone, open, delete)
+- Set up SSH deploy keys for project repos
+- Generate and maintain a `.env` file with project-specific tokens and endpoints
+- Build & run your project in Docker (via `uv` + `docker`)
+- Bundle and copy AI/LLM instruction markdowns to the clipboard
+
+The CLI is implemented with [Typer](https://typer.tiangolo.com/) and exposes a `mainsequence` command.
 
 ---
+
+## Installation & Invocation
+
+How you install the CLI depends on how this repository is packaged, but assuming it’s installed in your environment and provides the `mainsequence` entry point:
+
+```bash
+# General form
+mainsequence --help

{mainsequence-3.3.8 → mainsequence-3.4.1}/mainsequence.egg-info/requires.txt

@@ -33,3 +33,4 @@ duckdb
 plotly
 typer
 QuantLib
+streamlit

{mainsequence-3.3.8 → mainsequence-3.4.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mainsequence"
-version = "3.3.8"
+version = "3.4.1"
 description = "Main Sequence SDK "
 readme = "README.md"
 requires-python = ">=3.10"
@@ -56,6 +56,7 @@ dependencies = [
   "plotly",
   "typer",
   "QuantLib", # ← renamed from `quantlib`
+  "streamlit"
 
 ]
 

mainsequence-3.3.8/README.md

@@ -1,17 +0,0 @@
-<p align="center">
-<img src="https://main-sequence.app/static/media/logos/MS_logo_long_black.png" alt="Main Sequence Logo" width="500"/>
-</p>
-
-# Main Sequence Python SDK
-
-
-
-The **Main Sequence Python SDK** is a powerful set of client libraries designed to facilitate interaction with Main Sequence systems using Python. 
-
-**We strongly** encourage you to go through our examples. 
-We have built the examples as individual Jupyter notebooks that explain the SDK through use cases. 
-Since most platform usage involves a combination of operations, this is the most intuitive way to learn about Main Sequence.
-
-
-
----