forked from archi-physics/archi
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpyproject.toml
More file actions
90 lines (81 loc) · 3.21 KB
/
Copy pathpyproject.toml
File metadata and controls
90 lines (81 loc) · 3.21 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
[project]
name = "archi"
version = "1.2.4"
description = "An AI Augmented Research Chat Intelligence (archi)"
requires-python = ">=3.7"
authors = [
{name="Pietro Lugato", email="[email protected]"},
{name="Julius Heitkoetter", email="[email protected]"},
{name="Tim Kraska", email="[email protected]"},
{name="Christoph Paus", email="[email protected]"},
{name="Matthew Russo", email="[email protected]"},
{name="Luca Lavezzo", email="[email protected]"},
{name="Jason Mohoney", email="[email protected]"}
]
dependencies = [
"pyyaml==6.0.1",
"click==8.1.7",
"jinja2==3.1.3",
"requests==2.31.0",
"podman-compose==1.4.0",
"python-dotenv>=0.19.0",
"mkdocs==1.6.1",
# glossary: docs/mkdocs.yml enables the `pymdownx.snippets` extension (acronym
# tooltips auto-appended to every page). It ships in pymdown-extensions, which
# reaches the PR-preview build only transitively via mkdocs-material in
# requirements-base.txt. The deploy-docs workflow builds with `pip install .`
# (no requirements-base), so it MUST be declared here or `mkdocs build --strict`
# aborts with ModuleNotFoundError: pymdownx. Version matches requirements-base.txt.
"pymdown-extensions==11.0.1",
"ipykernel==6.30.1",
"ipython==8.18.0",
"matplotlib==3.9.4",
"pandas==2.3.2",
"isort==6.0.1",
"pre-commit>=4",
"psycopg2-binary==2.9.10",
"markitdown[pdf,pptx]==0.1.5",
# hierarchical-rerank-retrieval: the deployment images install deps via
# `pip install .` (Dockerfile-chat / Dockerfile-data-manager) on top of the
# published a2rchi base image, so feature deps MUST be declared here — not only
# in requirements/requirements-base.txt (which the gate/CI and base-image build
# use). Versions match requirements-base.txt.
"llama-index-core==0.14.19",
"flashrank==0.2.10",
# html-markdown-categorize-ingest: HTML->Markdown conversion at the persist
# seam. Built on the already-present beautifulsoup4. Pin matches
# requirements/requirements-base.txt.
"markdownify==1.2.2",
# add-sources-build-command: the `archi sources build` crawl path imports
# bs4. beautifulsoup4 was declared only in requirements/requirements-base.txt,
# so a fresh `pip install .`/editable install and the deployment images would
# lack it and the crawl path would ImportError. Version matches
# requirements-base.txt.
"beautifulsoup4==4.12.3"
]
[project.scripts]
archi = "src.cli.cli_main:main"
[tool.setuptools.package-data]
"src.cli" = ["templates/**/*"]
[tool.setuptools]
include-package-data = true
[tool.setuptools.packages.find]
include = ["src*"]
[build-system]
requires = ["setuptools>=61.0.0"]
build-backend = "setuptools.build_meta"
[tool.pytest.ini_options]
testpaths = ["tests/unit"]
addopts = "-v --tb=short"
[tool.pyright]
pythonVersion = "3.11"
extraPaths = ["."]
include = ["src", "tests"]
exclude = ["**/__pycache__", "**/node_modules", "config", "openspec/changes"]
[tool.isort]
# Adopt black's import-wrapping style so `isort` and `black` agree. Without this
# they disagree on multi-line import formatting and the two can never both pass
# --check on the same file.
profile = "black"
[project.urls]
"Homepage" = "https://github.com/archi-physics/archi"