spltz-viur-testing 0.1.0__tar.gz

spltz_viur_testing-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright © 2026 Andreas H. Kelch
+
+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.

spltz_viur_testing-0.1.0/PKG-INFO

@@ -0,0 +1,308 @@
+Metadata-Version: 2.4
+Name: spltz-viur-testing
+Version: 0.1.0
+Summary: Safe test-mode for ViUR core projects — Playwright e2e ready.
+Author: Andreas H. Kelch
+License: MIT License
+        
+        Copyright © 2026 Andreas H. Kelch
+        
+        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/sprengplatz/viur-testing
+Project-URL: Documentation, https://sprengplatz.github.io/viur-testing/
+Project-URL: Repository, https://github.com/sprengplatz/viur-testing.git
+Project-URL: Bug Tracker, https://github.com/sprengplatz/viur-testing/issues
+Project-URL: Changelog, https://github.com/sprengplatz/viur-testing/blob/main/CHANGELOG.md
+Keywords: viur,e2e,testing,playwright
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: viur-core<4,>=3.7
+Provides-Extra: test
+Requires-Dist: pytest~=8.0; extra == "test"
+Requires-Dist: pytest-cov~=5.0; extra == "test"
+Requires-Dist: coverage[toml]~=7.0; extra == "test"
+Requires-Dist: spltz-viur-light-mock>=0.1; extra == "test"
+Provides-Extra: docs
+Requires-Dist: mkdocs-material~=9.5; extra == "docs"
+Requires-Dist: mkdocstrings[python]~=0.26; extra == "docs"
+Provides-Extra: dev
+Requires-Dist: spltz-viur-testing[docs,test]; extra == "dev"
+Requires-Dist: build~=1.2; extra == "dev"
+Dynamic: license-file
+
+# viur-testing
+
+[![Tests](https://github.com/sprengplatz/viur-testing/actions/workflows/test.yml/badge.svg)](https://github.com/sprengplatz/viur-testing/actions/workflows/test.yml)
+[![Docs](https://github.com/sprengplatz/viur-testing/actions/workflows/docs.yml/badge.svg)](https://sprengplatz.github.io/viur-testing/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+Safe test-mode for ViUR core projects — primarily for Playwright
+end-to-end tests. Swaps the default datastore database out for a
+dedicated named database (default: `viur-tests`), with a bilateral
+handshake that refuses to let any test or endpoint run unless both the
+server **and** the runner agree they are talking to the test instance.
+
+## Bilateral guarantee in six lines
+
+1. **`activate()` refuses outside `conf.instance.is_dev_server`** —
+   read from viur-core's canonical flag.
+2. **Synchronous datastore probe** in the target database has to
+   succeed before the client swap is applied.
+3. **`TestModule` *and* `ConfigModule` both refuse to instantiate**
+   outside the dev server *or* without a prior `activate()` call —
+   both `__init__`s raise in either case. Even a host that bypasses
+   the `TestModule` container and mounts `ConfigModule` directly is
+   subject to the same checks, so a forgotten activate or a stray
+   production mount fails loudly at boot.
+4. **Per-request token validator** (`X-Viur-Test-Token`) blocks every
+   request that does not carry the session token, except the two
+   bootstrap endpoints.
+5. **`protect()` installs a production-side header guard** that 403s
+   any request carrying the test token header outside dev, regardless
+   of its value. Installed in every environment.
+6. **Runner preflight** calls `/json/_test/config/status` and refuses to run
+   any test if the server's reply (database, project_id, token hash)
+   does not match.
+
+The session token is stored only in the test database itself
+(kind `viur-tests`, entity `auth-token`) — never on disk. App Engine
+file-system writes are not needed.
+
+## Module layout
+
+```
+/_test/                    TestModule (container, refuses outside dev mode)
+  /_test/config/status     ConfigModule.status — issues/returns token
+  /_test/config/finish     ConfigModule.finish — deletes token entity
+```
+
+Future test flavours (load test, integration helpers, …) go in as
+sibling submodules under the same `_test` container.
+
+## Requirements
+
+- Python ≥ 3.12
+- viur-core ≥ 3.7, < 4
+- A named Datastore database (default name: `viur-tests`) created in
+  your GCP project alongside `(default)`.
+
+## Install
+
+The PyPI distribution name is `spltz-viur-testing` (experimental
+prefix); the Python import path stays `viur.testing`:
+
+```sh
+pip install spltz-viur-testing
+```
+
+```python
+import viur.testing
+viur.testing.setup()
+```
+
+## Server-side wiring
+
+Two one-liners. `main.py` — **as the first lines, before any
+`viur.core` import**:
+
+```python
+import viur.testing
+viur.testing.setup()
+
+# Only now may viur.core be imported by your own code.
+from viur.core import setup as core_setup
+import modules
+import render
+
+core_setup(modules, render)
+```
+
+`viur.testing.setup()` checks the `VIUR_TESTING_ENABLE` env var; if
+truthy it calls `activate()` (datastore client swap + key-factory
+patch + closed-system whitelist + state priming + validator install)
+and always installs the production header guard via `protect()`.
+
+In `modules/__init__.py` register the test endpoints — idempotent and
+safe to leave in place for production deployments (no-op when test
+mode isn't armed):
+
+```python
+# modules/__init__.py
+import viur.testing
+viur.testing.register_modules(globals())
+```
+
+That exposes `POST /json/_test/config/status` and `POST /json/_test/config/finish`.
+Both endpoints re-verify `conf.instance.is_dev_server` and the active
+datastore database before performing any work — defence in depth on
+top of the `TestModule.__init__` guard.
+
+If you need more control, the two functions wrap underlying primitives
+you can call yourself: `viur.testing.activate(database=...)`,
+`viur.testing.protect()`, plus direct mounting via
+`from viur.testing._test import TestModule`.
+
+## Running the dev server with test mode
+
+Toggle test mode at boot by setting the env var that `setup()` reads:
+
+```sh
+VIUR_TESTING_ENABLE=1 viur run
+```
+
+Without the env var, `setup()` skips `activate()` and the process boots
+against the default database as if the package were not installed.
+
+When test mode is active, the dev-server boot banner gains two extra
+lines — `database = …` and `namespace = …` — so the running slice is
+visible at a glance. The namespace line is rendered unconditionally;
+without `VIUR_TESTING_NAMESPACE` it falls back to `(default)`, making
+it obvious that test mode is armed but namespace isolation is **not**
+in effect:
+
+```
+# With VIUR_TESTING_NAMESPACE=alice
+################## LOCAL DEVELOPMENT SERVER IS UP AND RUNNING ##################
+#                          project = my-viur-project                           #
+#                               python = 3.13.0                                #
+#                                viur = 3.8.25                                 #
+#                            database = viur-tests                             #
+#                              namespace = alice                               #
+################################################################################
+
+# Without VIUR_TESTING_NAMESPACE (or with empty value)
+################## LOCAL DEVELOPMENT SERVER IS UP AND RUNNING ##################
+#                          project = my-viur-project                           #
+#                               python = 3.13.0                                #
+#                                viur = 3.8.25                                 #
+#                            database = viur-tests                             #
+#                            namespace = (default)                             #
+################################################################################
+```
+
+## Concurrency: sharing one test database across multiple testers
+
+The `viur-tests` database is a shared GCP resource. If two engineers
+both boot a dev server with the same database and run tests at the
+same time, their entities will collide — Person A's seed wipes
+Person B's user, Person B's test queries find leftovers from Person A.
+
+The fix is the optional `namespace` argument. ViUR-testing passes it
+to `google.cloud.datastore.Client(database=…, namespace=…)` and rewires
+`viur.core.db.Key` so every read and write in the process is scoped
+to that namespace. Different namespaces in the same database are
+fully isolated — no separate DB provisioning needed.
+
+Boot each dev server with its own namespace:
+
+```sh
+# Alice's machine
+VIUR_TESTING_ENABLE=1 VIUR_TESTING_NAMESPACE=alice viur run
+
+# Bob's machine
+VIUR_TESTING_ENABLE=1 VIUR_TESTING_NAMESPACE=bob viur run
+
+# CI for PR #42
+VIUR_TESTING_ENABLE=1 VIUR_TESTING_NAMESPACE=ci-pr-42 viur run
+```
+
+The runner-side `require_test_mode` can assert the expected namespace
+to fail fast when somebody points at the wrong slice::
+
+    from viur.testing import require_test_mode
+
+    status = require_test_mode(
+        "http://localhost:8080",
+        expected_namespace="alice",  # omit to skip; pass None for default
+    )
+
+`VIUR_TESTING_NAMESPACE` may be empty or unset — both mean "no
+namespace, use the Datastore default". This is the existing behaviour
+when no namespaces are needed (e.g. single-developer setup).
+
+## Runner-side wiring (pytest + Playwright)
+
+```python
+# tests/conftest.py
+import pytest
+from viur.testing import require_test_mode, finish
+
+_BASE_URL = "http://localhost:8080"
+
+
+@pytest.fixture(scope="session")
+def test_session():
+    status = require_test_mode(_BASE_URL)
+    yield status
+    finish(_BASE_URL, status.token)
+```
+
+If the server is not in test mode, points at the wrong database, or
+the token hash does not match the returned token, `require_test_mode`
+raises `TestModePreflightError` and no test ever runs.
+
+For Playwright, inject the token as a default header on the browser
+context:
+
+```python
+@pytest.fixture
+def context(browser, test_session):
+    return browser.new_context(
+        extra_http_headers={"X-Viur-Test-Token": test_session.token},
+    )
+```
+
+## Naming
+
+The Python package keeps its repository name `viur-testing` for stability,
+but everything inside it speaks the generic *test* vocabulary so future
+test flavours can be added under the same `TestModule` umbrella
+without churn. The `_test` URL prefix's leading underscore signals
+"system-internal, not for production callers".
+
+## Development
+
+```bash
+git clone git@github.com:sprengplatz/viur-testing.git
+cd viur-testing
+pip install -e ".[dev]"
+pytest                  # 100% coverage required
+mkdocs serve            # docs at http://localhost:8000
+```
+
+## Documentation
+
+See [sprengplatz.github.io/viur-testing](https://sprengplatz.github.io/viur-testing/).
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md).
+
+## License
+
+MIT — see [LICENSE](LICENSE).

spltz_viur_testing-0.1.0/README.md

@@ -0,0 +1,251 @@
+# viur-testing
+
+[![Tests](https://github.com/sprengplatz/viur-testing/actions/workflows/test.yml/badge.svg)](https://github.com/sprengplatz/viur-testing/actions/workflows/test.yml)
+[![Docs](https://github.com/sprengplatz/viur-testing/actions/workflows/docs.yml/badge.svg)](https://sprengplatz.github.io/viur-testing/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+Safe test-mode for ViUR core projects — primarily for Playwright
+end-to-end tests. Swaps the default datastore database out for a
+dedicated named database (default: `viur-tests`), with a bilateral
+handshake that refuses to let any test or endpoint run unless both the
+server **and** the runner agree they are talking to the test instance.
+
+## Bilateral guarantee in six lines
+
+1. **`activate()` refuses outside `conf.instance.is_dev_server`** —
+   read from viur-core's canonical flag.
+2. **Synchronous datastore probe** in the target database has to
+   succeed before the client swap is applied.
+3. **`TestModule` *and* `ConfigModule` both refuse to instantiate**
+   outside the dev server *or* without a prior `activate()` call —
+   both `__init__`s raise in either case. Even a host that bypasses
+   the `TestModule` container and mounts `ConfigModule` directly is
+   subject to the same checks, so a forgotten activate or a stray
+   production mount fails loudly at boot.
+4. **Per-request token validator** (`X-Viur-Test-Token`) blocks every
+   request that does not carry the session token, except the two
+   bootstrap endpoints.
+5. **`protect()` installs a production-side header guard** that 403s
+   any request carrying the test token header outside dev, regardless
+   of its value. Installed in every environment.
+6. **Runner preflight** calls `/json/_test/config/status` and refuses to run
+   any test if the server's reply (database, project_id, token hash)
+   does not match.
+
+The session token is stored only in the test database itself
+(kind `viur-tests`, entity `auth-token`) — never on disk. App Engine
+file-system writes are not needed.
+
+## Module layout
+
+```
+/_test/                    TestModule (container, refuses outside dev mode)
+  /_test/config/status     ConfigModule.status — issues/returns token
+  /_test/config/finish     ConfigModule.finish — deletes token entity
+```
+
+Future test flavours (load test, integration helpers, …) go in as
+sibling submodules under the same `_test` container.
+
+## Requirements
+
+- Python ≥ 3.12
+- viur-core ≥ 3.7, < 4
+- A named Datastore database (default name: `viur-tests`) created in
+  your GCP project alongside `(default)`.
+
+## Install
+
+The PyPI distribution name is `spltz-viur-testing` (experimental
+prefix); the Python import path stays `viur.testing`:
+
+```sh
+pip install spltz-viur-testing
+```
+
+```python
+import viur.testing
+viur.testing.setup()
+```
+
+## Server-side wiring
+
+Two one-liners. `main.py` — **as the first lines, before any
+`viur.core` import**:
+
+```python
+import viur.testing
+viur.testing.setup()
+
+# Only now may viur.core be imported by your own code.
+from viur.core import setup as core_setup
+import modules
+import render
+
+core_setup(modules, render)
+```
+
+`viur.testing.setup()` checks the `VIUR_TESTING_ENABLE` env var; if
+truthy it calls `activate()` (datastore client swap + key-factory
+patch + closed-system whitelist + state priming + validator install)
+and always installs the production header guard via `protect()`.
+
+In `modules/__init__.py` register the test endpoints — idempotent and
+safe to leave in place for production deployments (no-op when test
+mode isn't armed):
+
+```python
+# modules/__init__.py
+import viur.testing
+viur.testing.register_modules(globals())
+```
+
+That exposes `POST /json/_test/config/status` and `POST /json/_test/config/finish`.
+Both endpoints re-verify `conf.instance.is_dev_server` and the active
+datastore database before performing any work — defence in depth on
+top of the `TestModule.__init__` guard.
+
+If you need more control, the two functions wrap underlying primitives
+you can call yourself: `viur.testing.activate(database=...)`,
+`viur.testing.protect()`, plus direct mounting via
+`from viur.testing._test import TestModule`.
+
+## Running the dev server with test mode
+
+Toggle test mode at boot by setting the env var that `setup()` reads:
+
+```sh
+VIUR_TESTING_ENABLE=1 viur run
+```
+
+Without the env var, `setup()` skips `activate()` and the process boots
+against the default database as if the package were not installed.
+
+When test mode is active, the dev-server boot banner gains two extra
+lines — `database = …` and `namespace = …` — so the running slice is
+visible at a glance. The namespace line is rendered unconditionally;
+without `VIUR_TESTING_NAMESPACE` it falls back to `(default)`, making
+it obvious that test mode is armed but namespace isolation is **not**
+in effect:
+
+```
+# With VIUR_TESTING_NAMESPACE=alice
+################## LOCAL DEVELOPMENT SERVER IS UP AND RUNNING ##################
+#                          project = my-viur-project                           #
+#                               python = 3.13.0                                #
+#                                viur = 3.8.25                                 #
+#                            database = viur-tests                             #
+#                              namespace = alice                               #
+################################################################################
+
+# Without VIUR_TESTING_NAMESPACE (or with empty value)
+################## LOCAL DEVELOPMENT SERVER IS UP AND RUNNING ##################
+#                          project = my-viur-project                           #
+#                               python = 3.13.0                                #
+#                                viur = 3.8.25                                 #
+#                            database = viur-tests                             #
+#                            namespace = (default)                             #
+################################################################################
+```
+
+## Concurrency: sharing one test database across multiple testers
+
+The `viur-tests` database is a shared GCP resource. If two engineers
+both boot a dev server with the same database and run tests at the
+same time, their entities will collide — Person A's seed wipes
+Person B's user, Person B's test queries find leftovers from Person A.
+
+The fix is the optional `namespace` argument. ViUR-testing passes it
+to `google.cloud.datastore.Client(database=…, namespace=…)` and rewires
+`viur.core.db.Key` so every read and write in the process is scoped
+to that namespace. Different namespaces in the same database are
+fully isolated — no separate DB provisioning needed.
+
+Boot each dev server with its own namespace:
+
+```sh
+# Alice's machine
+VIUR_TESTING_ENABLE=1 VIUR_TESTING_NAMESPACE=alice viur run
+
+# Bob's machine
+VIUR_TESTING_ENABLE=1 VIUR_TESTING_NAMESPACE=bob viur run
+
+# CI for PR #42
+VIUR_TESTING_ENABLE=1 VIUR_TESTING_NAMESPACE=ci-pr-42 viur run
+```
+
+The runner-side `require_test_mode` can assert the expected namespace
+to fail fast when somebody points at the wrong slice::
+
+    from viur.testing import require_test_mode
+
+    status = require_test_mode(
+        "http://localhost:8080",
+        expected_namespace="alice",  # omit to skip; pass None for default
+    )
+
+`VIUR_TESTING_NAMESPACE` may be empty or unset — both mean "no
+namespace, use the Datastore default". This is the existing behaviour
+when no namespaces are needed (e.g. single-developer setup).
+
+## Runner-side wiring (pytest + Playwright)
+
+```python
+# tests/conftest.py
+import pytest
+from viur.testing import require_test_mode, finish
+
+_BASE_URL = "http://localhost:8080"
+
+
+@pytest.fixture(scope="session")
+def test_session():
+    status = require_test_mode(_BASE_URL)
+    yield status
+    finish(_BASE_URL, status.token)
+```
+
+If the server is not in test mode, points at the wrong database, or
+the token hash does not match the returned token, `require_test_mode`
+raises `TestModePreflightError` and no test ever runs.
+
+For Playwright, inject the token as a default header on the browser
+context:
+
+```python
+@pytest.fixture
+def context(browser, test_session):
+    return browser.new_context(
+        extra_http_headers={"X-Viur-Test-Token": test_session.token},
+    )
+```
+
+## Naming
+
+The Python package keeps its repository name `viur-testing` for stability,
+but everything inside it speaks the generic *test* vocabulary so future
+test flavours can be added under the same `TestModule` umbrella
+without churn. The `_test` URL prefix's leading underscore signals
+"system-internal, not for production callers".
+
+## Development
+
+```bash
+git clone git@github.com:sprengplatz/viur-testing.git
+cd viur-testing
+pip install -e ".[dev]"
+pytest                  # 100% coverage required
+mkdocs serve            # docs at http://localhost:8000
+```
+
+## Documentation
+
+See [sprengplatz.github.io/viur-testing](https://sprengplatz.github.io/viur-testing/).
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md).
+
+## License
+
+MIT — see [LICENSE](LICENSE).

spltz_viur_testing-0.1.0/pyproject.toml

@@ -0,0 +1,88 @@
+[build-system]
+requires = ["setuptools >= 61.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "spltz-viur-testing"
+dynamic = ["version"]
+description = "Safe test-mode for ViUR core projects — Playwright e2e ready."
+readme = "README.md"
+license = { file = "LICENSE" }
+requires-python = ">=3.12"
+authors = [
+    { name = "Andreas H. Kelch" },
+]
+keywords = ["viur", "e2e", "testing", "playwright"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+]
+dependencies = [
+    "viur-core>=3.7,<4",
+]
+
+[project.optional-dependencies]
+test = [
+    "pytest~=8.0",
+    "pytest-cov~=5.0",
+    "coverage[toml]~=7.0",
+    "spltz-viur-light-mock>=0.1",
+]
+docs = [
+    "mkdocs-material~=9.5",
+    "mkdocstrings[python]~=0.26",
+]
+dev = [
+    "spltz-viur-testing[test,docs]",
+    "build~=1.2",
+]
+
+[project.urls]
+Homepage = "https://github.com/sprengplatz/viur-testing"
+Documentation = "https://sprengplatz.github.io/viur-testing/"
+Repository = "https://github.com/sprengplatz/viur-testing.git"
+"Bug Tracker" = "https://github.com/sprengplatz/viur-testing/issues"
+Changelog = "https://github.com/sprengplatz/viur-testing/blob/main/CHANGELOG.md"
+
+[tool.setuptools.dynamic]
+version = { attr = "viur.testing.__version__" }
+
+[tool.setuptools.packages.find]
+where = ["src"]
+include = ["viur.*"]
+
+[tool.pytest.ini_options]
+minversion = "8.0"
+testpaths = ["tests"]
+addopts = [
+    "-ra",
+    "--strict-markers",
+    "--strict-config",
+    "--cov=viur.testing",
+    "--cov-report=term-missing",
+    "--cov-report=xml",
+    "--cov-report=html",
+    "--cov-fail-under=100",
+]
+filterwarnings = [
+    "error",
+]
+
+[tool.coverage.run]
+branch = true
+source = ["viur.testing"]
+
+[tool.coverage.report]
+exclude_also = [
+    "raise NotImplementedError",
+    "if TYPE_CHECKING:",
+    "if t\\.TYPE_CHECKING:",
+    "\\.\\.\\.",
+]
+show_missing = true
+skip_covered = false

spltz_viur_testing-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+