Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[project]
name = "nmsamplelocations"
name = "OcotilloAPI"
version = "0.1.0"
description = "Add your description here"
description = "FastAPI backend and CLI for managing Ocotillo groundwater locations, wells, assets, and bulk water-level data transfers."
readme = "README.md"
requires-python = ">=3.13"
dependencies = [
Expand Down Expand Up @@ -29,7 +29,7 @@ dependencies = [
"dnspython==2.7.0",
"dotenv>=0.9.9",
"email-validator==2.2.0",
"fastapi==0.116.1",
"fastapi==0.124.2",
"fastapi-pagination==0.14.3",
"frozenlist==1.7.0",
"geoalchemy2==0.18.0",
Expand Down Expand Up @@ -99,6 +99,10 @@ dependencies = [
"uvicorn==0.38.0",
"yarl==1.20.1",
]

[project.scripts]
oco = "cli.cli:cli"
Comment on lines +103 to +104

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Console script points to missing module

The new console entry oco is wired to cli.cli:cli, but there is no cli module/package anywhere in the repo (the only def cli is in manage.py). After installing the project, invoking the generated oco script will immediately fail with ModuleNotFoundError because setuptools cannot import cli.cli. This breakage is introduced by this commit and will affect every environment that installs and tries to use the CLI.

Useful? React with 👍 / 👎.


[tool.alembic]

# path to migration scripts.
Expand Down
Loading