lambda-api-decorators-cdk 0.2.3__tar.gz

lambda_api_decorators_cdk-0.2.3/.github/workflows/release.yml

@@ -0,0 +1,85 @@
+name: Release to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - name: Check out tagged revision
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Validate release tag
+        env:
+          RELEASE_TAG: ${{ github.ref_name }}
+        run: |
+          if [[ ! "$RELEASE_TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+            echo "Invalid release tag: $RELEASE_TAG" >&2
+            exit 1
+          fi
+
+      - name: Install test and build dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install build pytest setuptools-scm
+          python -m pip install .
+
+      - name: Run tests
+        run: pytest -q
+
+      - name: Build distributions
+        run: python -m build
+
+      - name: Verify generated package version
+        env:
+          RELEASE_TAG: ${{ github.ref_name }}
+        run: |
+          generated_version="$(python -m setuptools_scm)"
+          expected_version="${RELEASE_TAG#v}"
+          echo "Tag version:       $expected_version"
+          echo "Generated version: $generated_version"
+          if [[ "$generated_version" != "$expected_version" ]]; then
+            echo "Generated package version does not match the release tag" >&2
+            exit 1
+          fi
+          python - "$expected_version" <<'PY'
+          from email.parser import BytesParser
+          from pathlib import Path
+          from zipfile import ZipFile
+          import sys
+
+          expected_version = sys.argv[1]
+          wheel = next(Path("dist").glob("*.whl"))
+          with ZipFile(wheel) as archive:
+              metadata_path = next(
+                  name for name in archive.namelist()
+                  if name.endswith(".dist-info/METADATA")
+              )
+              metadata = BytesParser().parsebytes(archive.read(metadata_path))
+          if metadata["Version"] != expected_version:
+              raise SystemExit(
+                  f"Wheel version {metadata['Version']} does not match {expected_version}"
+              )
+          print(f"Wheel metadata version: {metadata['Version']}")
+          PY
+
+      - name: Publish distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

lambda_api_decorators_cdk-0.2.3/.gitignore

@@ -0,0 +1,9 @@
+pycache
+.venv
+build
+dist
+lambda_api_decorators_cdk.egg-info
+.idea
+TODO.txt
+__pycache__/
+*.py[cod]

lambda_api_decorators_cdk-0.2.3/AGENTS.md

@@ -0,0 +1,232 @@
+# Lambda API Decorators CDK — Agent Instructions
+
+## Project purpose
+
+This repository contains **Lambda API Decorators CDK**, the AWS CDK integration for the Lambda API Decorators project.
+
+The project goal is:
+
+> Define AWS Lambda APIs with Python decorators and automatically generate the infrastructure with AWS CDK.
+
+GitHub organization:
+
+`lambda-api-decorators`
+
+Package:
+
+`lambda-api-decorators-cdk`
+
+Python module:
+
+`lambda_api_decorators_cdk`
+
+Project documentation:
+
+`https://lambda-api-decorators.github.io/`
+
+## Design principles
+
+Follow these principles when changing the project:
+
+> Simple by default, CDK-native when needed.
+
+> Convention when convenient, configuration when needed.
+
+> Explicit configuration always wins over convention.
+
+Prefer small, composable APIs over large constructors or abstractions.
+
+Do not add configuration knobs before the corresponding feature has been designed.
+
+Do not introduce compatibility shims or aliases unless explicitly requested.
+
+## Public architecture
+
+The intended architecture is:
+
+```text
+LambdaApi
+    ↓
+LambdaApiConfig
+    ↓
+ResourceBuilder
+    ↓
+AWS CDK
+```
+
+`LambdaApi` is the recommended high-level CDK construct.
+
+`LambdaApiConfig` contains reusable Lambda/API build configuration and creates isolated `ResourceBuilder` snapshots.
+
+`ResourceBuilder` remains the lower-level engine and a supported public API.
+
+Do not duplicate `ResourceBuilder` option-resolution or precedence logic in higher-level classes.
+
+## Configuration lifecycle
+
+The high-level lifecycle is:
+
+```text
+configure
+    ↓
+construct
+    ↓
+build
+```
+
+Configuration intended to affect generated Lambda resources must exist before `LambdaApi` construction.
+
+Do not expose post-build configuration APIs that imply already-created resources can be retroactively changed.
+
+## Mutable state
+
+Avoid mutable default arguments.
+
+Reusable configuration must not share mutable container state across builds.
+
+Shallow-copy configuration containers when isolation is required.
+
+Do not deep-copy AWS CDK constructs.
+
+CDK objects supplied by callers should normally preserve object identity.
+
+## AWS CDK usage
+
+Prefer AWS CDK interfaces in public type annotations when the actual implementation supports them.
+
+Do not claim support for an interface unless the underlying implementation can actually operate on all supported instances.
+
+Be careful with JSII Python proxy identity.
+
+Two accesses to the same CDK property may produce different Python proxy objects.
+
+When appropriate, compare stable CDK properties instead of Python proxy identity.
+
+## REST and HTTP APIs
+
+REST is the semantic default for `LambdaApi`.
+
+Standard created and imported REST APIs are supported by the current high-level API.
+
+Concrete `apigatewayv2.HttpApi` instances are supported.
+
+Do not claim general imported `IHttpApi` support unless route construction is explicitly redesigned to support it.
+
+## Backward compatibility
+
+Existing `ResourceBuilder` behavior is compatibility-sensitive.
+
+Before modifying `ResourceBuilder`, determine whether the change affects existing direct callers.
+
+Do not silently change existing low-level behavior to simplify a new high-level API.
+
+When a new behavior conflicts with legacy behavior, prefer an explicit compatibility boundary.
+
+## Scope discipline
+
+Implement only the feature requested by the current task.
+
+Do not opportunistically implement future roadmap items.
+
+In particular, do not mix unrelated changes involving:
+
+* source packaging;
+* layer discovery;
+* permissions;
+* resource registries;
+* Lambda identity or caching;
+* logical-ID redesign;
+* decorator syntax;
+* supported HTTP methods;
+* API Gateway security features.
+
+A task may explicitly authorize one or more of these areas.
+
+## Testing workflow
+
+Tests are part of the public contract.
+
+Do not weaken, delete, skip, or mark tests `xfail` simply to make a change pass.
+
+When a task starts from a red test baseline, preserve the intended assertions while implementing the feature.
+
+Equivalent parametrization is acceptable, but do not silently remove behavioral coverage.
+
+Use real AWS CDK constructs when JSII runtime behavior, construct ownership, or type inference matters.
+
+Mock or monkeypatch narrow boundaries when necessary to avoid Docker or Lambda bundling.
+
+## Required verification
+
+After code changes, run at minimum:
+
+```bash
+pytest -q
+python -m compileall -q src tests
+git diff --check
+git status --short
+```
+
+When test inventory matters, also run:
+
+```bash
+pytest --collect-only -q
+```
+
+The existing test suite must remain green unless the current task explicitly establishes a deliberate red baseline.
+
+## Docker and bundling
+
+Unit tests should not require Docker unless the task explicitly concerns bundling behavior that cannot otherwise be tested.
+
+Prefer testing packaging-path calculation and construct orchestration independently from Docker-based bundling.
+
+## Git workflow
+
+Do not push changes to a remote repository unless explicitly requested.
+
+Do not create or update pull requests unless explicitly requested.
+
+Do not create unrelated branches.
+
+Do not amend or rewrite existing commits unless explicitly requested.
+
+If the task explicitly says PLAN ONLY, AUDIT ONLY, REVIEW ONLY, or TESTS ONLY, respect that boundary exactly.
+
+## Planning and audits
+
+For architectural changes, inspect the existing implementation before proposing a design.
+
+Identify:
+
+* current behavior;
+* public compatibility constraints;
+* affected files;
+* tests that protect current behavior;
+* proposed API;
+* migration or compatibility boundary;
+* deferred work.
+
+Do not implement during a PLAN ONLY or AUDIT ONLY task.
+
+## Documentation
+
+The repository README should explain this package clearly and link prominently to the complete project documentation.
+
+Central documentation is the source for complete cross-package architecture and guides.
+
+Avoid duplicating large documentation sections across repositories.
+
+## General engineering guidance
+
+Prefer straightforward code over clever abstractions.
+
+Avoid speculative generalization.
+
+Preserve type clarity.
+
+Keep public APIs intentionally small.
+
+When an implementation detail is not useful to callers, keep it private.
+
+If repository behavior contradicts an assumption in the task, report the conflict rather than silently redesigning unrelated code.

lambda_api_decorators_cdk-0.2.3/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Lambda API Decorators CDK
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

lambda_api_decorators_cdk-0.2.3/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.4
+Name: lambda-api-decorators-cdk
+Version: 0.2.3
+Summary: AWS CDK integration for Lambda API Decorators. Generate AWS Lambda and API Gateway infrastructure from decorated Python handlers.
+Author: Mateo Marcos, Emanuel Arguinarena, Lucas Picchi
+License: MIT License
+        
+        Copyright (c) 2024 Lambda API Decorators CDK
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+Project-URL: Homepage, https://github.com/lambda-api-decorators/lambda-api-decorators-cdk
+Project-URL: Repository, https://github.com/lambda-api-decorators/lambda-api-decorators-cdk
+Project-URL: Bug Reports, https://github.com/lambda-api-decorators/lambda-api-decorators-cdk
+Keywords: cdk,lambda,aws,api gateway,ast
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Framework :: AWS CDK :: 2
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aws-cdk.aws-lambda-python-alpha
+Dynamic: license-file
+
+# Lambda API Decorators CDK
+
+## A library for AWS API Gateway/Lambda Proxy Integration
+
+Lambda API Decorators CDK allows simplified resource creation for AWS Lambda functions and Rest API resources by using decorators and setting a builder with default, common or custom values for IAM Roles, Runtimes, Timeouts, Layers, Environment values, etc. This project relies abstract syntactic trees (ast) to analyze the code of your lambda functions and generate infraestructure accordingly.
+
+### Installation
+
+`lambda_api_decorators_cdk` is available from PyPI as `lambda-api-decorators-cdk`:
+
+    pip install lambda-api-decorators-cdk
+
+Installation of [lambda-api-decorators](https://pypi.org/project/lambda-api-decorators/) is also required as a dependency for your lambda functions, since it provides the definition of decorators used within this module.
+
+
+### Example
+
+```python
+    import lambda_api_decorators_cdk
+    or
+    from lambda_api_decorators_cdk import ResourceBuilder
+```
+
+### Builder instance
+
+You may define a builder using lambda_api_decorators_cdk's constructor `ResourceBuilder`. This method returns an instance of the class that will be used to configure and create your Lambda Functions. By default, no parameters are required to instantiate the object, but custom options may be passed in advanced use cases.
+
+```python
+    from lambda_api_decorators_cdk import ResourceBuilder
+
+    builder = ResourceBuilder()
+```
+
+### Builder Configuration
+
+If opted to, you can set default values for IAM Roles, Memory Size, Timeout, Runtime and VPC.
+
+On the same note, support for common configuration that all the Lambda Functions will receive, such as Security Groups, Environment variables and Layers, is provided.
+
+Lastly you can setup custom environments, layers, security groups, vpcs a Lambda Function will receive ONLY if they have the decorators defined.
+
+```python
+    from lambda_api_decorators_cdk import ResourceBuilder
+    from aws_cdk import Duration
+
+    builder = ResourceBuilder()
+    builder.set_default_timeout(Duration.seconds(30))
+    builder.add_common_environment("DATABASE_URI", "something-db-related")
+    builder.add_custom_environment("URL-PREFIX", "lambda-api-decorators-cdk-") #Lambda Function should have decorator @environment("URL-PREFIX")
+```
+
+### Building
+
+Assuming you have already instantiated a Builder, configured it and ready to deploy your stack, then simply define the directory of your Lambda Functions and build!
+
+Note: For a Lambda Function to be recognised and built, it has to have a decorator specifying the HTTP method it responds to. Decorators are defined in the [lambda-api-decorators](https://pypi.org/project/lambda-api-decorators/) package.
+
+```python
+[...] # Imports
+
+class LambdaApiDecoratorsExampleStack(Stack):
+
+    def __init__(self, scope: Construct, construct_id: str, **kwargs) -> None:
+        super().__init__(scope, construct_id, **kwargs)
+
+        [...]  # Instantiating builder, defining options and layers...
+
+        lambda_path = 'lambdas'
+
+        restapi = apigateway.RestApi(
+            self, 'lambda-api-decorators-RestApi',
+            rest_api_name= 'lambda-api-decorators-restApi')
+        root_resource = restapi.root
+
+        builder.build(self, root_resource, lambda_path, print_tree=True)
+
+```
+
+## Maintainer releases
+
+The Git tag is the single source of truth for this package's version. For
+example, `v0.3.0` produces Python package version `0.3.0`. This repository is
+versioned independently from `lambda-api-decorators`.
+
+To release from `main`, choose and push a semantic version tag:
+
+```bash
+git checkout main
+git pull
+
+git tag v0.3.0
+git push origin v0.3.0
+```
+
+Pushing the tag triggers the release workflow, which tests, builds, verifies
+the version, and publishes with PyPI trusted publishing. The PyPI project must
+have a trusted publisher configured for this repository, the `release.yml`
+workflow, and the `pypi` GitHub environment.

lambda_api_decorators_cdk-0.2.3/README.md

@@ -0,0 +1,98 @@
+# Lambda API Decorators CDK
+
+## A library for AWS API Gateway/Lambda Proxy Integration
+
+Lambda API Decorators CDK allows simplified resource creation for AWS Lambda functions and Rest API resources by using decorators and setting a builder with default, common or custom values for IAM Roles, Runtimes, Timeouts, Layers, Environment values, etc. This project relies abstract syntactic trees (ast) to analyze the code of your lambda functions and generate infraestructure accordingly.
+
+### Installation
+
+`lambda_api_decorators_cdk` is available from PyPI as `lambda-api-decorators-cdk`:
+
+    pip install lambda-api-decorators-cdk
+
+Installation of [lambda-api-decorators](https://pypi.org/project/lambda-api-decorators/) is also required as a dependency for your lambda functions, since it provides the definition of decorators used within this module.
+
+
+### Example
+
+```python
+    import lambda_api_decorators_cdk
+    or
+    from lambda_api_decorators_cdk import ResourceBuilder
+```
+
+### Builder instance
+
+You may define a builder using lambda_api_decorators_cdk's constructor `ResourceBuilder`. This method returns an instance of the class that will be used to configure and create your Lambda Functions. By default, no parameters are required to instantiate the object, but custom options may be passed in advanced use cases.
+
+```python
+    from lambda_api_decorators_cdk import ResourceBuilder
+
+    builder = ResourceBuilder()
+```
+
+### Builder Configuration
+
+If opted to, you can set default values for IAM Roles, Memory Size, Timeout, Runtime and VPC.
+
+On the same note, support for common configuration that all the Lambda Functions will receive, such as Security Groups, Environment variables and Layers, is provided.
+
+Lastly you can setup custom environments, layers, security groups, vpcs a Lambda Function will receive ONLY if they have the decorators defined.
+
+```python
+    from lambda_api_decorators_cdk import ResourceBuilder
+    from aws_cdk import Duration
+
+    builder = ResourceBuilder()
+    builder.set_default_timeout(Duration.seconds(30))
+    builder.add_common_environment("DATABASE_URI", "something-db-related")
+    builder.add_custom_environment("URL-PREFIX", "lambda-api-decorators-cdk-") #Lambda Function should have decorator @environment("URL-PREFIX")
+```
+
+### Building
+
+Assuming you have already instantiated a Builder, configured it and ready to deploy your stack, then simply define the directory of your Lambda Functions and build!
+
+Note: For a Lambda Function to be recognised and built, it has to have a decorator specifying the HTTP method it responds to. Decorators are defined in the [lambda-api-decorators](https://pypi.org/project/lambda-api-decorators/) package.
+
+```python
+[...] # Imports
+
+class LambdaApiDecoratorsExampleStack(Stack):
+
+    def __init__(self, scope: Construct, construct_id: str, **kwargs) -> None:
+        super().__init__(scope, construct_id, **kwargs)
+
+        [...]  # Instantiating builder, defining options and layers...
+
+        lambda_path = 'lambdas'
+
+        restapi = apigateway.RestApi(
+            self, 'lambda-api-decorators-RestApi',
+            rest_api_name= 'lambda-api-decorators-restApi')
+        root_resource = restapi.root
+
+        builder.build(self, root_resource, lambda_path, print_tree=True)
+
+```
+
+## Maintainer releases
+
+The Git tag is the single source of truth for this package's version. For
+example, `v0.3.0` produces Python package version `0.3.0`. This repository is
+versioned independently from `lambda-api-decorators`.
+
+To release from `main`, choose and push a semantic version tag:
+
+```bash
+git checkout main
+git pull
+
+git tag v0.3.0
+git push origin v0.3.0
+```
+
+Pushing the tag triggers the release workflow, which tests, builds, verifies
+the version, and publishes with PyPI trusted publishing. The PyPI project must
+have a trusted publisher configured for this repository, the `release.yml`
+workflow, and the `pypi` GitHub environment.

lambda_api_decorators_cdk-0.2.3/pyproject.toml

@@ -0,0 +1,104 @@
+# Guide (user-friendly):
+# https://packaging.python.org/en/latest/guides/writing-pyproject-toml/
+
+# Specification (technical, formal):
+# https://packaging.python.org/en/latest/specifications/pyproject-toml/
+
+
+# Choosing a build backend:
+# https://packaging.python.org/en/latest/tutorials/packaging-projects/#choosing-a-build-backend
+[build-system]
+# A list of packages that are needed to build your package:
+requires = ["setuptools", "setuptools-scm>=8"]  # REQUIRED if [build-system] table is used
+# The name of the Python object that frontends will use to perform the build:
+build-backend = "setuptools.build_meta"  # If not defined, then legacy behavior can happen.
+
+
+[project]
+# https://packaging.python.org/specifications/core-metadata/#name
+name = "lambda-api-decorators-cdk"
+# https://packaging.python.org/guides/single-sourcing-package-version/
+dynamic = ["version"]
+
+# https://packaging.python.org/specifications/core-metadata/#summary
+description = "AWS CDK integration for Lambda API Decorators. Generate AWS Lambda and API Gateway infrastructure from decorated Python handlers."
+
+# https://packaging.python.org/specifications/core-metadata/#description-optional
+readme = "README.md"
+
+# https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
+requires-python = ">=3.9"
+
+
+# https://packaging.python.org/en/latest/specifications/core-metadata/#license
+license = {file = "LICENSE"}
+
+keywords = ["cdk", "lambda", "aws", "api gateway", "ast"]
+
+authors = [
+  {name = "Mateo Marcos"},
+  {name = "Emanuel Arguinarena"},
+  {name = "Lucas Picchi"}
+]
+
+#maintainers = [
+#  {name = "A. Great Maintainer", email = "maintainer@example.com" }
+#]
+
+
+# For a list of valid classifiers, see https://pypi.org/classifiers/
+classifiers = [
+  'Development Status :: 2 - Pre-Alpha',
+  'Intended Audience :: Developers',
+  'Framework :: AWS CDK :: 2',
+  'Topic :: Software Development :: Libraries :: Python Modules',
+  'Topic :: Software Development :: Build Tools',
+  'License :: OSI Approved :: MIT License',
+  'Programming Language :: Python :: 3.9',
+  'Programming Language :: Python :: 3.10',
+  'Programming Language :: Python :: 3.11',
+  'Programming Language :: Python :: 3.12'
+]
+
+# For an analysis of this field vs pip's requirements files see:
+# https://packaging.python.org/discussions/install-requires-vs-requirements/
+dependencies = [
+  "aws-cdk.aws-lambda-python-alpha"
+]
+
+
+# https://packaging.python.org/en/latest/specifications/dependency-specifiers/#extras
+#[project.optional-dependencies]
+#dev = ["check-manifest"]
+#test = ["coverage"]
+
+# List URLs that are relevant to your project
+#
+# This field corresponds to the "Project-URL" and "Home-Page" metadata fields:
+# https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
+# https://packaging.python.org/specifications/core-metadata/#home-page-optional
+#
+# Examples listed include a pattern for specifying where the package tracks
+# issues, where the source is hosted, where to say thanks to the package
+# maintainers, and where to support the project financially. The key is
+# what's used to render the link text on PyPI.
+[project.urls]
+"Homepage" = "https://github.com/lambda-api-decorators/lambda-api-decorators-cdk"
+"Repository" = "https://github.com/lambda-api-decorators/lambda-api-decorators-cdk"
+"Bug Reports" = "https://github.com/lambda-api-decorators/lambda-api-decorators-cdk"
+
+# The following would provide a command line executable called `sample`
+# which executes the function `main` from this package when invoked.
+#[project.scripts]
+#sample = "sample:main"
+
+
+# This is configuration specific to the `setuptools` build backend.
+# If you are using a different build backend, you will need to change this.
+[tool.setuptools]
+
+[tool.setuptools_scm]
+tag_regex = '^v(?P<version>[0-9]+\.[0-9]+\.[0-9]+)$'
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]