ayes 0.0.1__tar.gz

ayes-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: uv sync --group dev
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run mypy
+      - run: uv run pytest

ayes-0.0.1/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+.env
+
+# Notes de travail locales, jamais versionnées
+CLAUDE.md

ayes-0.0.1/.python-version

@@ -0,0 +1 @@
+3.14

ayes-0.0.1/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## 0.0.1 — unreleased
+
+- Project skeleton: packaging, license, CI, design notes in the README.

ayes-0.0.1/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

ayes-0.0.1/NOTICE

@@ -0,0 +1,4 @@
+Ayes
+Copyright 2026 API-Air
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).

ayes-0.0.1/PKG-INFO

@@ -0,0 +1,184 @@
+Metadata-Version: 2.5
+Name: ayes
+Version: 0.0.1
+Summary: Pundit-style authorization policies for Python web apps.
+Author: API-Air
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: authorization,fastapi,multi-tenant,permissions,policy,pundit
+Classifier: Development Status :: 1 - Planning
+Classifier: Framework :: FastAPI
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Provides-Extra: fastapi
+Requires-Dist: fastapi>=0.115; extra == 'fastapi'
+Description-Content-Type: text/markdown
+
+# Ayes
+
+**Pundit-style authorization policies for Python web apps.** FastAPI first.
+
+*The ayes have it:* every action your app allows has been voted through by a policy.
+
+> Status: **pre-alpha, design phase.** Nothing below is implemented yet. The API sketched here is a
+> proposal, open to change.
+
+Ayes answers one question, everywhere in your app, the same way:
+
+> *May this user do this action on this object?*
+
+Authentication tells you **who** is calling. Ayes decides **what they may do**. It does this with
+plain Python policy classes, one per kind of object, the way Ruby's Pundit does. Then it checks
+that every route actually asks.
+
+## Why
+
+FastAPI deliberately ships no authorization layer. OAuth2 scopes answer "may this token write
+invoices?", not "may this user edit *this* invoice?". So most apps grow access checks inline,
+route by route. Each route recombines the rules a little differently, and the gaps look alike:
+
+- an object reachable from another tenant because two checks were made separately and never
+  compared;
+- three code paths for the same action, and only two of them apply the rule;
+- the same refusal answered 403 here, 404 there, 422 elsewhere, leaking whether an object exists.
+
+Ayes' goal is to make those mistakes hard to write and easy to catch.
+
+## Principles
+
+1. **One policy per object, plain Python.** A class with one method per action. No DSL to learn.
+2. **Explicit, not magic.** The route names its policy and its action. Nothing is inferred from
+   class or function names.
+3. **Authorize the object, then hand it over.** The FastAPI dependency loads the object, checks it,
+   and gives the route the *authorized* object. The route can't load a different one by mistake.
+4. **Tenancy is an invariant, not a rule you remember.** If your app is multi-tenant, "same tenant"
+   is checked once, before any policy runs.
+5. **Normalized refusals.** Out of scope → 404 (never confirm an object exists). In scope, not
+   allowed → 403. Allowed, but the object's state forbids it → 409.
+6. **Scopes for lists.** A policy also says which rows a user may list, as a query filter.
+7. **Async first.** Policies often need the database. The user's context (tenants, roles) is loaded
+   once per request, not once per check.
+8. **The rules are a table, and the table is tested.** You declare who may do what. Ayes generates
+   the test cases from that declaration.
+9. **No route left behind.** A test inspects every route and fails if one doesn't go through a
+   policy (with an explicit allow-list for public routes).
+
+## API sketch (draft)
+
+A multi-tenant publishing tool: each workspace is a tenant, and holds articles. In a workspace, a
+person is an `admin`, an `editor` or a `user`. Users write drafts; editors edit and publish;
+admins can also delete.
+
+```python
+from ayes import Policy, Refused
+
+
+class ArticlePolicy(Policy[Article]):
+    def tenant_of(self, article: Article) -> UUID:
+        return article.workspace_id
+
+    async def view(self) -> bool:
+        return (
+            self.obj.is_published or self.role in {"admin", "editor"} or self.is_author
+        )
+
+    async def update(self) -> bool:
+        return self.role in {"admin", "editor"} or (
+            self.is_author and self.obj.is_draft
+        )
+
+    async def publish(self) -> bool:
+        return self.role in {"admin", "editor"}
+
+    async def delete(self) -> bool:
+        if self.obj.is_under_legal_hold:
+            raise Refused.state("article_under_legal_hold")  # → 409
+        return self.role == "admin"
+
+    @property
+    def is_author(self) -> bool:
+        return self.obj.author_id == self.user.id
+
+    @classmethod
+    def scope(cls, user: Context) -> ColumnElement[bool]:
+        return Article.workspace_id.in_(user.workspace_ids)
+```
+
+In a FastAPI route:
+
+```python
+from ayes.fastapi import authorize
+
+CanUpdate = Depends(authorize(ArticlePolicy, "update", load=get_article))
+
+
+@router.patch("/articles/{article_id}")
+async def update_article(
+    article: Annotated[Article, CanUpdate],
+    payload: ArticleUpdate,
+):
+    # No access checks here: `article` is already authorized.
+    ...
+```
+
+Declaring the rules, and getting the tests:
+
+```python
+from ayes.testing import Matrix
+
+matrix = Matrix(
+    ArticlePolicy,
+    roles=["admin", "editor", "user", "outsider"],
+    rules={
+        "update": ["admin", "editor"],
+        "publish": ["admin", "editor"],
+        "delete": ["admin"],
+    },
+)
+
+# One test per role × action, plus the cross-tenant case.
+test_article_policy = matrix.pytest()
+```
+
+Checking coverage:
+
+```python
+from ayes.testing import assert_all_routes_authorized
+
+
+def test_every_route_is_authorized():
+    assert_all_routes_authorized(app, public={"/health", "/auth/login"})
+```
+
+## Coming from Pundit
+
+| Pundit (Rails) | Ayes |
+|---|---|
+| `PostPolicy#update?` | `PostPolicy.update()`, async |
+| `authorize @post` | `Depends(authorize(PostPolicy, "update", load=...))`, returns the post |
+| `policy_scope(Post)` | `PostPolicy.scope(user)`, a SQL filter |
+| `verify_authorized` | `assert_all_routes_authorized(app)`, in CI rather than at runtime |
+| `rescue_from Pundit::NotAuthorizedError` | one exception handler mapping refusals to 404 / 403 / 409 |
+| `permitted_attributes` | fields allowed per action, checked against the request model |
+
+## Roadmap
+
+- **0.1** — core: `Policy`, request context, tenant invariant, normalized refusals, FastAPI
+  `authorize` dependency, list scopes.
+- **0.2** — testing: declared rule matrix → generated tests; route coverage check (report mode,
+  then blocking).
+- **0.3** — permitted fields; SQLAlchemy helpers.
+- Later — Django and Flask integrations, if the core holds up.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

ayes-0.0.1/README.md

@@ -0,0 +1,159 @@
+# Ayes
+
+**Pundit-style authorization policies for Python web apps.** FastAPI first.
+
+*The ayes have it:* every action your app allows has been voted through by a policy.
+
+> Status: **pre-alpha, design phase.** Nothing below is implemented yet. The API sketched here is a
+> proposal, open to change.
+
+Ayes answers one question, everywhere in your app, the same way:
+
+> *May this user do this action on this object?*
+
+Authentication tells you **who** is calling. Ayes decides **what they may do**. It does this with
+plain Python policy classes, one per kind of object, the way Ruby's Pundit does. Then it checks
+that every route actually asks.
+
+## Why
+
+FastAPI deliberately ships no authorization layer. OAuth2 scopes answer "may this token write
+invoices?", not "may this user edit *this* invoice?". So most apps grow access checks inline,
+route by route. Each route recombines the rules a little differently, and the gaps look alike:
+
+- an object reachable from another tenant because two checks were made separately and never
+  compared;
+- three code paths for the same action, and only two of them apply the rule;
+- the same refusal answered 403 here, 404 there, 422 elsewhere, leaking whether an object exists.
+
+Ayes' goal is to make those mistakes hard to write and easy to catch.
+
+## Principles
+
+1. **One policy per object, plain Python.** A class with one method per action. No DSL to learn.
+2. **Explicit, not magic.** The route names its policy and its action. Nothing is inferred from
+   class or function names.
+3. **Authorize the object, then hand it over.** The FastAPI dependency loads the object, checks it,
+   and gives the route the *authorized* object. The route can't load a different one by mistake.
+4. **Tenancy is an invariant, not a rule you remember.** If your app is multi-tenant, "same tenant"
+   is checked once, before any policy runs.
+5. **Normalized refusals.** Out of scope → 404 (never confirm an object exists). In scope, not
+   allowed → 403. Allowed, but the object's state forbids it → 409.
+6. **Scopes for lists.** A policy also says which rows a user may list, as a query filter.
+7. **Async first.** Policies often need the database. The user's context (tenants, roles) is loaded
+   once per request, not once per check.
+8. **The rules are a table, and the table is tested.** You declare who may do what. Ayes generates
+   the test cases from that declaration.
+9. **No route left behind.** A test inspects every route and fails if one doesn't go through a
+   policy (with an explicit allow-list for public routes).
+
+## API sketch (draft)
+
+A multi-tenant publishing tool: each workspace is a tenant, and holds articles. In a workspace, a
+person is an `admin`, an `editor` or a `user`. Users write drafts; editors edit and publish;
+admins can also delete.
+
+```python
+from ayes import Policy, Refused
+
+
+class ArticlePolicy(Policy[Article]):
+    def tenant_of(self, article: Article) -> UUID:
+        return article.workspace_id
+
+    async def view(self) -> bool:
+        return (
+            self.obj.is_published or self.role in {"admin", "editor"} or self.is_author
+        )
+
+    async def update(self) -> bool:
+        return self.role in {"admin", "editor"} or (
+            self.is_author and self.obj.is_draft
+        )
+
+    async def publish(self) -> bool:
+        return self.role in {"admin", "editor"}
+
+    async def delete(self) -> bool:
+        if self.obj.is_under_legal_hold:
+            raise Refused.state("article_under_legal_hold")  # → 409
+        return self.role == "admin"
+
+    @property
+    def is_author(self) -> bool:
+        return self.obj.author_id == self.user.id
+
+    @classmethod
+    def scope(cls, user: Context) -> ColumnElement[bool]:
+        return Article.workspace_id.in_(user.workspace_ids)
+```
+
+In a FastAPI route:
+
+```python
+from ayes.fastapi import authorize
+
+CanUpdate = Depends(authorize(ArticlePolicy, "update", load=get_article))
+
+
+@router.patch("/articles/{article_id}")
+async def update_article(
+    article: Annotated[Article, CanUpdate],
+    payload: ArticleUpdate,
+):
+    # No access checks here: `article` is already authorized.
+    ...
+```
+
+Declaring the rules, and getting the tests:
+
+```python
+from ayes.testing import Matrix
+
+matrix = Matrix(
+    ArticlePolicy,
+    roles=["admin", "editor", "user", "outsider"],
+    rules={
+        "update": ["admin", "editor"],
+        "publish": ["admin", "editor"],
+        "delete": ["admin"],
+    },
+)
+
+# One test per role × action, plus the cross-tenant case.
+test_article_policy = matrix.pytest()
+```
+
+Checking coverage:
+
+```python
+from ayes.testing import assert_all_routes_authorized
+
+
+def test_every_route_is_authorized():
+    assert_all_routes_authorized(app, public={"/health", "/auth/login"})
+```
+
+## Coming from Pundit
+
+| Pundit (Rails) | Ayes |
+|---|---|
+| `PostPolicy#update?` | `PostPolicy.update()`, async |
+| `authorize @post` | `Depends(authorize(PostPolicy, "update", load=...))`, returns the post |
+| `policy_scope(Post)` | `PostPolicy.scope(user)`, a SQL filter |
+| `verify_authorized` | `assert_all_routes_authorized(app)`, in CI rather than at runtime |
+| `rescue_from Pundit::NotAuthorizedError` | one exception handler mapping refusals to 404 / 403 / 409 |
+| `permitted_attributes` | fields allowed per action, checked against the request model |
+
+## Roadmap
+
+- **0.1** — core: `Policy`, request context, tenant invariant, normalized refusals, FastAPI
+  `authorize` dependency, list scopes.
+- **0.2** — testing: declared rule matrix → generated tests; route coverage check (report mode,
+  then blocking).
+- **0.3** — permitted fields; SQLAlchemy helpers.
+- Later — Django and Flask integrations, if the core holds up.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

ayes-0.0.1/pyproject.toml

@@ -0,0 +1,63 @@
+[build-system]
+requires = ["hatchling>=1.25"]
+build-backend = "hatchling.build"
+
+[project]
+name = "ayes"
+version = "0.0.1"
+description = "Pundit-style authorization policies for Python web apps."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+requires-python = ">=3.11"
+authors = [{ name = "API-Air" }]
+keywords = ["authorization", "policy", "permissions", "fastapi", "multi-tenant", "pundit"]
+classifiers = [
+    "Development Status :: 1 - Planning",
+    "Framework :: FastAPI",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Security",
+    "Typing :: Typed",
+]
+# The core has no runtime dependency. Framework integrations are optional extras.
+dependencies = []
+
+[project.optional-dependencies]
+fastapi = ["fastapi>=0.115"]
+
+[dependency-groups]
+dev = [
+    "pytest>=8.3",
+    "pytest-asyncio>=0.25",
+    "httpx>=0.28",
+    "fastapi>=0.115",
+    "ruff>=0.11",
+    "mypy>=1.15",
+]
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/ayes"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+asyncio_mode = "auto"
+asyncio_default_fixture_loop_scope = "function"
+
+[tool.ruff]
+line-length = 88
+target-version = "py311"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP", "SIM", "RUF"]
+
+[tool.mypy]
+python_version = "3.11"
+strict = true
+packages = ["ayes"]
+mypy_path = "src"

ayes-0.0.1/src/ayes/__init__.py

@@ -0,0 +1,8 @@
+"""Ayes — Pundit-style authorization policies for Python web apps.
+
+Pre-alpha: the public API is being designed. See README.md.
+"""
+
+__version__ = "0.0.1"
+
+__all__ = ["__version__"]

ayes-0.0.1/tests/test_package.py

@@ -0,0 +1,5 @@
+import ayes
+
+
+def test_version_is_exposed() -> None:
+    assert ayes.__version__ == "0.0.1"