reference-package 0.1.8__tar.gz

reference_package-0.1.8/PKG-INFO

@@ -0,0 +1,151 @@
+Metadata-Version: 2.1
+Name: reference_package
+Version: 0.1.8
+Summary: A basic package setup with examples.
+Author: Kaleb Coberly
+Maintainer-email: kaleb.coberly@gmail.com
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: click<9.0.0,>=8.0.0
+Requires-Dist: typeguard<5.0.0,>=4.0.0
+Provides-Extra: dev
+Requires-Dist: reference_package[build]; extra == "dev"
+Requires-Dist: reference_package[doc]; extra == "dev"
+Requires-Dist: reference_package[qc]; extra == "dev"
+Requires-Dist: reference_package[test]; extra == "dev"
+Provides-Extra: build
+Requires-Dist: build; extra == "build"
+Requires-Dist: twine; extra == "build"
+Provides-Extra: doc
+Requires-Dist: furo>=2023.5.20; extra == "doc"
+Requires-Dist: sphinx>=7.0.1; extra == "doc"
+Requires-Dist: sphinx-autodoc-typehints>=1.23.3; extra == "doc"
+Provides-Extra: qc
+Requires-Dist: bandit>=1.7; extra == "qc"
+Requires-Dist: black>=23.3; extra == "qc"
+Requires-Dist: black[jupyter]>=23.3; extra == "qc"
+Requires-Dist: flake8>=6.0.0; extra == "qc"
+Requires-Dist: flake8-annotations>=3.0.1; extra == "qc"
+Requires-Dist: flake8-bandit>=4.1.1; extra == "qc"
+Requires-Dist: flake8-black>=0.3.6; extra == "qc"
+Requires-Dist: flake8-bugbear>=23.7.10; extra == "qc"
+Requires-Dist: flake8-docstrings>=1.7.0; extra == "qc"
+Requires-Dist: flake8-isort>=6.0.0; extra == "qc"
+Requires-Dist: isort>=5.12.0; extra == "qc"
+Requires-Dist: jake>=3.0.1; extra == "qc"
+Requires-Dist: pytype>=2023.6.0; extra == "qc"
+Requires-Dist: reference_package[test]; extra == "qc"
+Requires-Dist: safety>=2.3.1; extra == "qc"
+Provides-Extra: test
+Requires-Dist: coverage[toml]>=7.2.7; extra == "test"
+Requires-Dist: pytest>=7.4; extra == "test"
+Requires-Dist: pytest-cov>=4.1; extra == "test"
+
+# Basic package template
+
+## Summary
+
+Just a basic package template.
+
+## Credit
+
+I borrowed and modified the structure and tools from the idiomatic usage of IHME's Central Computation GBD team when I worked with them in 2023-2024.
+
+## Structure
+
+```bash
+    src/reference_package/api       Public and internal API.
+    src/reference_package/cli       Command-line-interface.
+    src/reference_package/lib       Implementation.
+    tests/e2e                       End-to-end tests.
+    test/integration                Integration tests.
+    tests/unit                      Unit tests.
+```
+
+## Dependencies
+
+* Python 3.11
+* [make](https://www.gnu.org/software/make/)
+
+
+## Library functions
+
+`reference_package` is a library from which you can import functions. Import the public example function like this: `from reference_package import wait_a_second`. Or, import the internal version like a power user like this: `from reference_package.api.internal import wait_a_second`.
+
+Unless you're developing, avoid importing directly from library, like `from reference_package.lib.example import wait_a_second`.
+
+## CLI
+
+Try the example CLI:
+
+    $ python -m example
+    $ python -m example --secs 2
+
+## Dev installation
+
+You'll want this package's site-package files to be the source files in this repo so you can test your changes without having to reinstall. We've got some tools for that.
+
+First build and activate the env before installing this package:
+
+    $ make build-env
+    $ conda activate reference_package_py3.12
+
+Then, install this package and its dev dependencies:
+
+    $ make install INSTALL_EXTRAS=[dev]
+
+This installs all the dependencies in your conda env site-packages, but the files for this package's installation are now your source files in this repo.
+
+## Dev workflow
+
+You can list all the make tools you might want to use:
+
+    $ make list-targets
+
+Go check them out in `Makefile`.
+
+### QC and testing
+
+Before pushing commits, you'll usually want to rebuild the env and run all the QC and testing:
+
+    $ make clean format full
+
+When making smaller commits, you might just want to run some of the smaller commands:
+
+    $ make clean format full-qc full-test
+
+### CI test run
+
+Before opening a PR or pushing to it, you'll want to run locally the same CI pipeline that GitHub will run (`.github/workflows/QC-and-build.yml`). This runs on multiple images, so you'll need to install Docker and have it running on your machine: https://www.docker.com/
+
+Once that's installed and running, you can use `act`. You'll need to install that as well. I develop on a Mac, so I used `homebrew` to install it (which you'll also need to install: https://brew.sh/):
+
+    $ brew install act
+
+Then, run it from the repo directory:
+
+    $ make ci-run
+
+That will run `.github/workflows/QC-and-build.yml` and every other action tagged to the pull_request event. Also, since `act` doesn't work with Mac and Windows architecture, it skips/fails them, but it is a good test of the Linux build.
+
+# TODO
+
+- Move these to issues.
+- Restrict deployment with GitHub environments: https://docs.github.com/en/actions/use-cases-and-examples/deploying/deploying-with-github-actions, https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment
+- Update deploy jobs to install from deployed package version and run tests again. (https://test.pypi.org/project/reference-package/ `pip install -i https://test.pypi.org/simple/ reference-package==0.1.6`)
+- Add proper branch protection on main and set publishing environments to protected branches only.
+- Add CLI help docs to documentation.
+- Make docs deploy.
+- Add Windows image to matrix.
+  - Get a local runner that will work with Windows (other than my laptop)
+- Remove upper pins on dependencies since this is a template and pretty bare? (That way I'll know if a new change is truly breaking to basic usage, and new packages built from this template can choose upper pins based on what they install at that time.)
+- Make a periodic build, with failure/success alerts. https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule, https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#create-a-repository-dispatch-event
+- Add license and other standard docs.
+- Verify user for all PRs, not just to main?
+- Install app to only allow PRs from within org?
+- Explain SPEC 0 support window as rationale for matrix build.
+- Ooo, make an experimental doc lint recipe with these neato tools: https://earthly.dev/blog/markdown-lint/
+- And, look more closely at this: https://www.writethedocs.org/guide/docs-as-code/
+- Make repo public.
+- Bump QC to python 3.13 when msgspec update gets released: https://github.com/jcrist/msgspec/issues/698, https://github.com/jcrist/msgspec/issues/698 (Add issue number to inline TODO.)
+- Build package first and install that in base env to clone and then install and run QC, tests, and doc build? Just to be more certain of what we're deploying.

reference_package-0.1.8/README.md

@@ -0,0 +1,108 @@
+# Basic package template
+
+## Summary
+
+Just a basic package template.
+
+## Credit
+
+I borrowed and modified the structure and tools from the idiomatic usage of IHME's Central Computation GBD team when I worked with them in 2023-2024.
+
+## Structure
+
+```bash
+    src/reference_package/api       Public and internal API.
+    src/reference_package/cli       Command-line-interface.
+    src/reference_package/lib       Implementation.
+    tests/e2e                       End-to-end tests.
+    test/integration                Integration tests.
+    tests/unit                      Unit tests.
+```
+
+## Dependencies
+
+* Python 3.11
+* [make](https://www.gnu.org/software/make/)
+
+
+## Library functions
+
+`reference_package` is a library from which you can import functions. Import the public example function like this: `from reference_package import wait_a_second`. Or, import the internal version like a power user like this: `from reference_package.api.internal import wait_a_second`.
+
+Unless you're developing, avoid importing directly from library, like `from reference_package.lib.example import wait_a_second`.
+
+## CLI
+
+Try the example CLI:
+
+    $ python -m example
+    $ python -m example --secs 2
+
+## Dev installation
+
+You'll want this package's site-package files to be the source files in this repo so you can test your changes without having to reinstall. We've got some tools for that.
+
+First build and activate the env before installing this package:
+
+    $ make build-env
+    $ conda activate reference_package_py3.12
+
+Then, install this package and its dev dependencies:
+
+    $ make install INSTALL_EXTRAS=[dev]
+
+This installs all the dependencies in your conda env site-packages, but the files for this package's installation are now your source files in this repo.
+
+## Dev workflow
+
+You can list all the make tools you might want to use:
+
+    $ make list-targets
+
+Go check them out in `Makefile`.
+
+### QC and testing
+
+Before pushing commits, you'll usually want to rebuild the env and run all the QC and testing:
+
+    $ make clean format full
+
+When making smaller commits, you might just want to run some of the smaller commands:
+
+    $ make clean format full-qc full-test
+
+### CI test run
+
+Before opening a PR or pushing to it, you'll want to run locally the same CI pipeline that GitHub will run (`.github/workflows/QC-and-build.yml`). This runs on multiple images, so you'll need to install Docker and have it running on your machine: https://www.docker.com/
+
+Once that's installed and running, you can use `act`. You'll need to install that as well. I develop on a Mac, so I used `homebrew` to install it (which you'll also need to install: https://brew.sh/):
+
+    $ brew install act
+
+Then, run it from the repo directory:
+
+    $ make ci-run
+
+That will run `.github/workflows/QC-and-build.yml` and every other action tagged to the pull_request event. Also, since `act` doesn't work with Mac and Windows architecture, it skips/fails them, but it is a good test of the Linux build.
+
+# TODO
+
+- Move these to issues.
+- Restrict deployment with GitHub environments: https://docs.github.com/en/actions/use-cases-and-examples/deploying/deploying-with-github-actions, https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment
+- Update deploy jobs to install from deployed package version and run tests again. (https://test.pypi.org/project/reference-package/ `pip install -i https://test.pypi.org/simple/ reference-package==0.1.6`)
+- Add proper branch protection on main and set publishing environments to protected branches only.
+- Add CLI help docs to documentation.
+- Make docs deploy.
+- Add Windows image to matrix.
+  - Get a local runner that will work with Windows (other than my laptop)
+- Remove upper pins on dependencies since this is a template and pretty bare? (That way I'll know if a new change is truly breaking to basic usage, and new packages built from this template can choose upper pins based on what they install at that time.)
+- Make a periodic build, with failure/success alerts. https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule, https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#create-a-repository-dispatch-event
+- Add license and other standard docs.
+- Verify user for all PRs, not just to main?
+- Install app to only allow PRs from within org?
+- Explain SPEC 0 support window as rationale for matrix build.
+- Ooo, make an experimental doc lint recipe with these neato tools: https://earthly.dev/blog/markdown-lint/
+- And, look more closely at this: https://www.writethedocs.org/guide/docs-as-code/
+- Make repo public.
+- Bump QC to python 3.13 when msgspec update gets released: https://github.com/jcrist/msgspec/issues/698, https://github.com/jcrist/msgspec/issues/698 (Add issue number to inline TODO.)
+- Build package first and install that in base env to clone and then install and run QC, tests, and doc build? Just to be more certain of what we're deploying.

reference_package-0.1.8/pyproject.toml

@@ -0,0 +1,32 @@
+[build-system]
+requires = ["setuptools"]
+build-backend = "setuptools.build_meta"
+
+[tool.pytest.ini_options]
+markers = [
+    "unit",
+    "integration",
+    "e2e",
+]
+
+junit_family = "xunit2"
+testpaths = [
+    "tests/unit",
+    "tests/integration",
+    "tests/e2e",
+]
+
+[tool.coverage.report]
+show_missing = true
+
+[tool.black]
+line_length = 94
+skip-magic-trailing-comma = true
+
+[tool.isort]
+line_length = 94
+profile = "black"
+multi_line_output = 3
+known_klub = ["reference_package"]
+# Custom sections and ordering, https:://pypi.org/project/isort/
+sections = ["FUTURE", "STDLIB", "THIRDPARTY", "KLUB", "FIRSTPARTY", "LOCALFOLDER"]

reference_package-0.1.8/setup.cfg

@@ -0,0 +1,63 @@
+[metadata]
+name = reference_package
+version = 0.1.8
+description = A basic package setup with examples.
+long_description = file: README.md
+long_description_content_type = text/markdown
+author = Kaleb Coberly
+maintainer_email = kaleb.coberly@gmail.com
+
+[options.entry_points]
+console_scripts = 
+	example = reference_package.cli.example:main
+
+[options]
+python_requires = >=3.11
+package_dir = 
+	=src
+packages = find:
+install_requires = 
+	click>=8.0.0,<9.0.0
+	typeguard>=4.0.0,<5.0.0
+
+[options.packages.find]
+where = src
+
+[options.extras_require]
+dev = 
+	reference_package[build]
+	reference_package[doc]
+	reference_package[qc]
+	reference_package[test]
+build = 
+	build
+	twine
+doc = 
+	furo>=2023.5.20
+	sphinx>=7.0.1
+	sphinx-autodoc-typehints>=1.23.3
+qc = 
+	bandit>=1.7
+	black>=23.3
+	black[jupyter]>=23.3
+	flake8>=6.0.0
+	flake8-annotations>=3.0.1
+	flake8-bandit>=4.1.1
+	flake8-black>=0.3.6
+	flake8-bugbear>=23.7.10
+	flake8-docstrings>=1.7.0
+	flake8-isort>=6.0.0
+	isort>=5.12.0
+	jake>=3.0.1
+	pytype>=2023.6.0
+	reference_package[test]
+	safety>=2.3.1
+test = 
+	coverage[toml]>=7.2.7
+	pytest>=7.4
+	pytest-cov>=4.1
+
+[egg_info]
+tag_build = 
+tag_date = 0
+

reference_package-0.1.8/src/reference_package/__init__.py

@@ -0,0 +1,12 @@
+"""Top-level init."""
+
+from importlib.metadata import version
+
+from reference_package.api.public import wait_a_second
+
+try:
+    __version__: str = version(__name__)
+except Exception:
+    __version__ = "unknown"
+
+del version

reference_package-0.1.8/src/reference_package/api/__init__.py

@@ -0,0 +1 @@
+"""Do not define in API, only import."""

reference_package-0.1.8/src/reference_package/api/internal.py

@@ -0,0 +1,25 @@
+"""Internal functions overlay library and are typically wrapped by public functions.
+
+This allows us to maintain a separation of API from implementation.
+Internal functions may come with extra options that public functions don't have, say for
+power users and developers who may want to use an existing DB session or something.
+"""
+
+from typeguard import typechecked
+
+from reference_package.lib import example
+
+
+@typechecked
+def wait_a_second(
+    secs: int = 1, extra_string: str = "Fancy me, calling internal functions."
+) -> None:
+    """Just wait a second, or however many seconds you want.
+
+    Also prints a message with the number you passed, along with any extra message you want.
+
+    Arguments:
+        secs: How many seconds to wait.
+        extra_string: Extra message to add on tail of existing message.
+    """
+    example.wait_a_second(secs=secs, extra_string=extra_string)

reference_package-0.1.8/src/reference_package/api/public.py

@@ -0,0 +1,21 @@
+"""Public functions wrap internal functions which wrap library functions.
+
+This allows separation of API from implementation. It also allows a simplified public API
+separate from a more complex internal API with more options for power users.
+"""
+
+from typeguard import typechecked
+
+from reference_package.api.internal import example
+
+
+@typechecked
+def wait_a_second(secs: int = 1) -> None:
+    """Just wait a second, or however many seconds you want.
+
+    Also prints a message with the number you passed.
+
+    Arguments:
+        secs: How many seconds to wait.
+    """
+    example.wait_a_second(secs=secs)

reference_package-0.1.8/src/reference_package/cli/__init__.py

@@ -0,0 +1 @@
+"""CLI init."""

reference_package-0.1.8/src/reference_package/cli/example.py

@@ -0,0 +1,14 @@
+"""This is just an example."""
+
+import click
+from typeguard import typechecked
+
+from reference_package.lib import example
+
+
+@click.command()
+@click.option("--secs", type=int, required=False, default=1)
+@typechecked
+def main(secs: int = 1) -> None:
+    """Wait n seconds."""
+    example.wait_a_second(secs=secs)

reference_package-0.1.8/src/reference_package/lib/__init__.py

@@ -0,0 +1 @@
+"""lib init."""

reference_package-0.1.8/src/reference_package/lib/example.py

@@ -0,0 +1,16 @@
+"""This is an example module."""
+
+import time
+
+
+def wait_a_second(secs: int = 1, extra_string: str = "") -> None:
+    """Just wait a second, or however many seconds you want.
+
+    Also prints a message with the number you passed, along with any extra message you want.
+
+    Arguments:
+        secs: How many seconds to wait.
+        extra_string: Extra message to add on tail of existing message.
+    """
+    print(f"Waiting {secs} seconds.{' ' + extra_string if extra_string else ''}")
+    time.sleep(secs)

reference_package-0.1.8/src/reference_package.egg-info/PKG-INFO

@@ -0,0 +1,151 @@
+Metadata-Version: 2.1
+Name: reference_package
+Version: 0.1.8
+Summary: A basic package setup with examples.
+Author: Kaleb Coberly
+Maintainer-email: kaleb.coberly@gmail.com
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: click<9.0.0,>=8.0.0
+Requires-Dist: typeguard<5.0.0,>=4.0.0
+Provides-Extra: dev
+Requires-Dist: reference_package[build]; extra == "dev"
+Requires-Dist: reference_package[doc]; extra == "dev"
+Requires-Dist: reference_package[qc]; extra == "dev"
+Requires-Dist: reference_package[test]; extra == "dev"
+Provides-Extra: build
+Requires-Dist: build; extra == "build"
+Requires-Dist: twine; extra == "build"
+Provides-Extra: doc
+Requires-Dist: furo>=2023.5.20; extra == "doc"
+Requires-Dist: sphinx>=7.0.1; extra == "doc"
+Requires-Dist: sphinx-autodoc-typehints>=1.23.3; extra == "doc"
+Provides-Extra: qc
+Requires-Dist: bandit>=1.7; extra == "qc"
+Requires-Dist: black>=23.3; extra == "qc"
+Requires-Dist: black[jupyter]>=23.3; extra == "qc"
+Requires-Dist: flake8>=6.0.0; extra == "qc"
+Requires-Dist: flake8-annotations>=3.0.1; extra == "qc"
+Requires-Dist: flake8-bandit>=4.1.1; extra == "qc"
+Requires-Dist: flake8-black>=0.3.6; extra == "qc"
+Requires-Dist: flake8-bugbear>=23.7.10; extra == "qc"
+Requires-Dist: flake8-docstrings>=1.7.0; extra == "qc"
+Requires-Dist: flake8-isort>=6.0.0; extra == "qc"
+Requires-Dist: isort>=5.12.0; extra == "qc"
+Requires-Dist: jake>=3.0.1; extra == "qc"
+Requires-Dist: pytype>=2023.6.0; extra == "qc"
+Requires-Dist: reference_package[test]; extra == "qc"
+Requires-Dist: safety>=2.3.1; extra == "qc"
+Provides-Extra: test
+Requires-Dist: coverage[toml]>=7.2.7; extra == "test"
+Requires-Dist: pytest>=7.4; extra == "test"
+Requires-Dist: pytest-cov>=4.1; extra == "test"
+
+# Basic package template
+
+## Summary
+
+Just a basic package template.
+
+## Credit
+
+I borrowed and modified the structure and tools from the idiomatic usage of IHME's Central Computation GBD team when I worked with them in 2023-2024.
+
+## Structure
+
+```bash
+    src/reference_package/api       Public and internal API.
+    src/reference_package/cli       Command-line-interface.
+    src/reference_package/lib       Implementation.
+    tests/e2e                       End-to-end tests.
+    test/integration                Integration tests.
+    tests/unit                      Unit tests.
+```
+
+## Dependencies
+
+* Python 3.11
+* [make](https://www.gnu.org/software/make/)
+
+
+## Library functions
+
+`reference_package` is a library from which you can import functions. Import the public example function like this: `from reference_package import wait_a_second`. Or, import the internal version like a power user like this: `from reference_package.api.internal import wait_a_second`.
+
+Unless you're developing, avoid importing directly from library, like `from reference_package.lib.example import wait_a_second`.
+
+## CLI
+
+Try the example CLI:
+
+    $ python -m example
+    $ python -m example --secs 2
+
+## Dev installation
+
+You'll want this package's site-package files to be the source files in this repo so you can test your changes without having to reinstall. We've got some tools for that.
+
+First build and activate the env before installing this package:
+
+    $ make build-env
+    $ conda activate reference_package_py3.12
+
+Then, install this package and its dev dependencies:
+
+    $ make install INSTALL_EXTRAS=[dev]
+
+This installs all the dependencies in your conda env site-packages, but the files for this package's installation are now your source files in this repo.
+
+## Dev workflow
+
+You can list all the make tools you might want to use:
+
+    $ make list-targets
+
+Go check them out in `Makefile`.
+
+### QC and testing
+
+Before pushing commits, you'll usually want to rebuild the env and run all the QC and testing:
+
+    $ make clean format full
+
+When making smaller commits, you might just want to run some of the smaller commands:
+
+    $ make clean format full-qc full-test
+
+### CI test run
+
+Before opening a PR or pushing to it, you'll want to run locally the same CI pipeline that GitHub will run (`.github/workflows/QC-and-build.yml`). This runs on multiple images, so you'll need to install Docker and have it running on your machine: https://www.docker.com/
+
+Once that's installed and running, you can use `act`. You'll need to install that as well. I develop on a Mac, so I used `homebrew` to install it (which you'll also need to install: https://brew.sh/):
+
+    $ brew install act
+
+Then, run it from the repo directory:
+
+    $ make ci-run
+
+That will run `.github/workflows/QC-and-build.yml` and every other action tagged to the pull_request event. Also, since `act` doesn't work with Mac and Windows architecture, it skips/fails them, but it is a good test of the Linux build.
+
+# TODO
+
+- Move these to issues.
+- Restrict deployment with GitHub environments: https://docs.github.com/en/actions/use-cases-and-examples/deploying/deploying-with-github-actions, https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment
+- Update deploy jobs to install from deployed package version and run tests again. (https://test.pypi.org/project/reference-package/ `pip install -i https://test.pypi.org/simple/ reference-package==0.1.6`)
+- Add proper branch protection on main and set publishing environments to protected branches only.
+- Add CLI help docs to documentation.
+- Make docs deploy.
+- Add Windows image to matrix.
+  - Get a local runner that will work with Windows (other than my laptop)
+- Remove upper pins on dependencies since this is a template and pretty bare? (That way I'll know if a new change is truly breaking to basic usage, and new packages built from this template can choose upper pins based on what they install at that time.)
+- Make a periodic build, with failure/success alerts. https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule, https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#create-a-repository-dispatch-event
+- Add license and other standard docs.
+- Verify user for all PRs, not just to main?
+- Install app to only allow PRs from within org?
+- Explain SPEC 0 support window as rationale for matrix build.
+- Ooo, make an experimental doc lint recipe with these neato tools: https://earthly.dev/blog/markdown-lint/
+- And, look more closely at this: https://www.writethedocs.org/guide/docs-as-code/
+- Make repo public.
+- Bump QC to python 3.13 when msgspec update gets released: https://github.com/jcrist/msgspec/issues/698, https://github.com/jcrist/msgspec/issues/698 (Add issue number to inline TODO.)
+- Build package first and install that in base env to clone and then install and run QC, tests, and doc build? Just to be more certain of what we're deploying.

reference_package-0.1.8/src/reference_package.egg-info/SOURCES.txt

@@ -0,0 +1,17 @@
+README.md
+pyproject.toml
+setup.cfg
+src/reference_package/__init__.py
+src/reference_package.egg-info/PKG-INFO
+src/reference_package.egg-info/SOURCES.txt
+src/reference_package.egg-info/dependency_links.txt
+src/reference_package.egg-info/entry_points.txt
+src/reference_package.egg-info/requires.txt
+src/reference_package.egg-info/top_level.txt
+src/reference_package/api/__init__.py
+src/reference_package/api/internal.py
+src/reference_package/api/public.py
+src/reference_package/cli/__init__.py
+src/reference_package/cli/example.py
+src/reference_package/lib/__init__.py
+src/reference_package/lib/example.py

reference_package-0.1.8/src/reference_package.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

reference_package-0.1.8/src/reference_package.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+example = reference_package.cli.example:main

reference_package-0.1.8/src/reference_package.egg-info/requires.txt

@@ -0,0 +1,39 @@
+click<9.0.0,>=8.0.0
+typeguard<5.0.0,>=4.0.0
+
+[build]
+build
+twine
+
+[dev]
+reference_package[build]
+reference_package[doc]
+reference_package[qc]
+reference_package[test]
+
+[doc]
+furo>=2023.5.20
+sphinx>=7.0.1
+sphinx-autodoc-typehints>=1.23.3
+
+[qc]
+bandit>=1.7
+black>=23.3
+black[jupyter]>=23.3
+flake8>=6.0.0
+flake8-annotations>=3.0.1
+flake8-bandit>=4.1.1
+flake8-black>=0.3.6
+flake8-bugbear>=23.7.10
+flake8-docstrings>=1.7.0
+flake8-isort>=6.0.0
+isort>=5.12.0
+jake>=3.0.1
+pytype>=2023.6.0
+reference_package[test]
+safety>=2.3.1
+
+[test]
+coverage[toml]>=7.2.7
+pytest>=7.4
+pytest-cov>=4.1

reference_package-0.1.8/src/reference_package.egg-info/top_level.txt

@@ -0,0 +1 @@
+reference_package