detquantlib 2.0.4__tar.gz

detquantlib-2.0.4/LICENSE.txt

@@ -0,0 +1,3 @@
+* Copyright (C) 2025 Dynamic Energy Trading B.V. - All Rights Reserved
+* The copying and distribution of this project via any medium is strictly prohibited without the express consent of Dynamic Energy Trading B.V.
+* Proprietary and confidential

detquantlib-2.0.4/PKG-INFO

@@ -0,0 +1,153 @@
+Metadata-Version: 2.3
+Name: detquantlib
+Version: 2.0.4
+Summary: An internal library containing functions and classes that can be used across Quant models.
+Author: DET
+Requires-Python: >=3.10,<4.0
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Dist: numpy (>=2.2.4,<3.0.0)
+Requires-Dist: pandas (>=2.2.3,<3.0.0)
+Requires-Dist: paramiko (>=3.5.1,<4.0.0)
+Requires-Dist: plotly (>=6.0.1,<7.0.0)
+Requires-Dist: pyodbc (>=5.2.0,<6.0.0)
+Project-URL: Repository, https://github.com/Dynamic-Energy-Trading/detquantlib
+Description-Content-Type: text/markdown
+
+# DET Quant Library
+
+The DET Quant Library is an internal library containing functions and classes that can be used
+across Quant models.
+
+## Instructions
+
+#### Version control
+
+- This repository contains a version control workflow.
+- The version number is specified via the `version` field in the pyproject.toml file.
+- The version number needs to be updated with every new master commit. If the version is not
+  updated, the GitHub workflow will fail.
+- Version numbers should follow semantic versioning (i.e. `X.Y.Z`). That is:
+  - `X` increments represent major, non-backward compatible updates.
+  - `Y` increments represent minor, backward compatible functionality updates.
+  - `Z` increments represent patch/bugfix, backward compatible updates.
+
+#### Release notes
+
+- When deemed necessary (especially in case of major updates), developers can document code
+  changes in dedicated GitHub release notes.
+- Release notes can be created via
+  <https://github.com/Dynamic-Energy-Trading/detquantlib/releases.>
+- In any case, all codes changes should always be properly described/documented in GitHub
+  issues and/or pull requests.
+
+#### Installing the `detquantlib` package in other Python projects
+
+To install the library in another project, use the following poetry command:
+
+```
+poetry add git+https://github.com/Dynamic-Energy-Trading/detquantlib.git@vX.Y.Z
+```
+
+where `vX.Y.Z` should be replaced with the relevant version (e.g. `v1.2.3`).
+
+## Development settings
+
+### Dependency management
+
+Project dependencies are managed by [Poetry](https://python-poetry.org/).
+
+The project follows the standard Poetry structure:
+
+```
+poetrytemplate
+├── pyproject.toml
+├── README.md
+├── src
+│   └── __init__.py
+└── tests
+    └── __init__.py
+```
+
+### Dependency updates
+
+This project is executing automated dependency updates using
+[Dependabot with GitHub actions](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions).
+
+### Invoke development tasks
+
+Development tasks are defined with the [Invoke](https://www.pyinvoke.org/) package.
+
+#### What is Invoke?
+
+Invoke provides a clean, high level API for running shell commands and defining/organizing task
+functions from a tasks.py file.
+
+#### How to run development tasks?
+
+Development tasks can be executed directly from the terminal, using the `inv` (or `invoke`)
+command line tool.
+
+For guidance on the available Invoke development tasks, execute the following command in the
+terminal:
+
+```cmd
+inv --list
+```
+
+Use the `-h` (or `--help`) argument for help about a particular development task. For example:
+
+```cmd
+inv lint -h
+```
+
+### CI/CD process
+
+This project is executing CI checks using [GitHub actions](https://docs.github.com/en/actions)
+workflows.
+
+The GitHub workflow defined in this project was inspired by the following preconfigured templates:
+
+- [Python package](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml):
+  A general workflow template for Python packages.
+- [Poetry action](https://github.com/marketplace/actions/install-poetry-action): A GitHub action
+  for installing and configuring Poetry.
+
+#### CI check: Testing
+
+Code changes are tested with the [Pytest](https://github.com/pytest-dev/pytest) package.
+
+The CI check is executed with the following the development task:
+
+```cmd
+inv test -c
+```
+
+#### CI check: Code formatting
+
+Linters are used to check that the code is properly formatted:
+
+- [Isort](https://github.com/timothycrosley/isort) for the imports section
+- [Darglint](https://github.com/terrencepreilly/darglint) for the docstrings description
+- [Black](https://github.com/psf/black) for the main code
+- [Pymarkdown](https://github.com/jackdewinter/pymarkdown) for the markdown file README.md
+
+The CI check is executed with the following development task:
+
+```cmd
+inv lint -c
+```
+
+If the CI check fails, execute the following command in the terminal:
+
+```cmd
+inv lint
+```
+
+This command fixes the parts of the code that should be reformatted. Adding the `-c` (or
+`--check`) optional argument instructs the command to only _check_ if parts of the code should be
+reformatted, without applying any actual changes.
+

detquantlib-2.0.4/README.md

@@ -0,0 +1,133 @@
+# DET Quant Library
+
+The DET Quant Library is an internal library containing functions and classes that can be used
+across Quant models.
+
+## Instructions
+
+#### Version control
+
+- This repository contains a version control workflow.
+- The version number is specified via the `version` field in the pyproject.toml file.
+- The version number needs to be updated with every new master commit. If the version is not
+  updated, the GitHub workflow will fail.
+- Version numbers should follow semantic versioning (i.e. `X.Y.Z`). That is:
+  - `X` increments represent major, non-backward compatible updates.
+  - `Y` increments represent minor, backward compatible functionality updates.
+  - `Z` increments represent patch/bugfix, backward compatible updates.
+
+#### Release notes
+
+- When deemed necessary (especially in case of major updates), developers can document code
+  changes in dedicated GitHub release notes.
+- Release notes can be created via
+  <https://github.com/Dynamic-Energy-Trading/detquantlib/releases.>
+- In any case, all codes changes should always be properly described/documented in GitHub
+  issues and/or pull requests.
+
+#### Installing the `detquantlib` package in other Python projects
+
+To install the library in another project, use the following poetry command:
+
+```
+poetry add git+https://github.com/Dynamic-Energy-Trading/detquantlib.git@vX.Y.Z
+```
+
+where `vX.Y.Z` should be replaced with the relevant version (e.g. `v1.2.3`).
+
+## Development settings
+
+### Dependency management
+
+Project dependencies are managed by [Poetry](https://python-poetry.org/).
+
+The project follows the standard Poetry structure:
+
+```
+poetrytemplate
+├── pyproject.toml
+├── README.md
+├── src
+│   └── __init__.py
+└── tests
+    └── __init__.py
+```
+
+### Dependency updates
+
+This project is executing automated dependency updates using
+[Dependabot with GitHub actions](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions).
+
+### Invoke development tasks
+
+Development tasks are defined with the [Invoke](https://www.pyinvoke.org/) package.
+
+#### What is Invoke?
+
+Invoke provides a clean, high level API for running shell commands and defining/organizing task
+functions from a tasks.py file.
+
+#### How to run development tasks?
+
+Development tasks can be executed directly from the terminal, using the `inv` (or `invoke`)
+command line tool.
+
+For guidance on the available Invoke development tasks, execute the following command in the
+terminal:
+
+```cmd
+inv --list
+```
+
+Use the `-h` (or `--help`) argument for help about a particular development task. For example:
+
+```cmd
+inv lint -h
+```
+
+### CI/CD process
+
+This project is executing CI checks using [GitHub actions](https://docs.github.com/en/actions)
+workflows.
+
+The GitHub workflow defined in this project was inspired by the following preconfigured templates:
+
+- [Python package](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml):
+  A general workflow template for Python packages.
+- [Poetry action](https://github.com/marketplace/actions/install-poetry-action): A GitHub action
+  for installing and configuring Poetry.
+
+#### CI check: Testing
+
+Code changes are tested with the [Pytest](https://github.com/pytest-dev/pytest) package.
+
+The CI check is executed with the following the development task:
+
+```cmd
+inv test -c
+```
+
+#### CI check: Code formatting
+
+Linters are used to check that the code is properly formatted:
+
+- [Isort](https://github.com/timothycrosley/isort) for the imports section
+- [Darglint](https://github.com/terrencepreilly/darglint) for the docstrings description
+- [Black](https://github.com/psf/black) for the main code
+- [Pymarkdown](https://github.com/jackdewinter/pymarkdown) for the markdown file README.md
+
+The CI check is executed with the following development task:
+
+```cmd
+inv lint -c
+```
+
+If the CI check fails, execute the following command in the terminal:
+
+```cmd
+inv lint
+```
+
+This command fixes the parts of the code that should be reformatted. Adding the `-c` (or
+`--check`) optional argument instructs the command to only _check_ if parts of the code should be
+reformatted, without applying any actual changes.

detquantlib-2.0.4/detquantlib/__init__.py

@@ -0,0 +1 @@
+# Empty file required by poetry. Do not delete.