@yahyahammad/venastine 0.1.0 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/pyproject.toml CHANGED
@@ -1,100 +1,100 @@
1
- # Issue #144 -- requirements.txt was the whole of what this project said
2
- # about how to install it, and it is the one packaging format that cannot
3
- # express a Python floor or an optional group.
4
- #
5
- # Python 3.11 is a hard requirement, not a preference: mcp_client/client.py
6
- # uses asyncio.timeout (3.11+), and 27 sites use runtime `X | Y` annotations
7
- # (3.10+). On 3.10 a user got `AttributeError: module 'asyncio' has no
8
- # attribute 'timeout'` from inside the MCP connect path, AFTER
9
- # `pip install -r requirements.txt` reported success. requires-python turns
10
- # that into a refusal at install time.
11
-
12
- # setuptools>=77 is the floor for PEP 639: the SPDX `license = "Apache-2.0"` string below is
13
- # read as a classifier expression only from that release on. An older backend treats it as a
14
- # path and fails the build rather than warning, so this floor and that line move together.
15
- [build-system]
16
- requires = ["setuptools>=77"]
17
- build-backend = "setuptools.build_meta"
18
-
19
- [project]
20
- name = "venastine-research-harness"
21
- version = "0.1.0"
22
- description = "A from-scratch agentic harness: tool-using chat plus a ten-pass self-critiquing research pipeline."
23
- readme = "README.md"
24
- requires-python = ">=3.11"
25
- # PEP 639: a bare SPDX expression, not the deprecated `{ text = ... }` table, and no
26
- # `License :: OSI Approved ::` classifier -- PEP 639 supersedes those and setuptools warns on
27
- # both. `license-files` is declared rather than left to the backend's default glob so the file
28
- # that ships is the one named here.
29
- license = "Apache-2.0"
30
- # NOTICE ships WITH the licence, not beside it in the repo only: a NOTICE that
31
- # is not listed here exists in a checkout and is absent from every sdist and
32
- # wheel, which defeats the reason for having one. Apache-2.0 4(d) is what makes
33
- # the pairing meaningful downstream.
34
- license-files = ["LICENSE", "NOTICE"]
35
- authors = [{ name = "Yahya Hammad" }]
36
- maintainers = [{ name = "Yahya Hammad" }]
37
- classifiers = [
38
- "Programming Language :: Python :: 3",
39
- "Programming Language :: Python :: 3.11",
40
- "Programming Language :: Python :: 3.12",
41
- "Programming Language :: Python :: 3.13",
42
- "Intended Audience :: Science/Research",
43
- "Topic :: Scientific/Engineering :: Artificial Intelligence",
44
- ]
45
-
46
- # ONE dependency list, and it stays in requirements.txt -- the file that
47
- # already carries the D22 rationale comments explaining why `textual` and
48
- # `mcp` are upper-bounded. Inlining the list here would create a second
49
- # hand-maintained copy of the same fact, which is the shape #144 was filed
50
- # about in the first place ("a hand-maintained list is only as complete as
51
- # the file it lives in"). setuptools strips comments and blank lines.
52
- #
53
- # THIS KEY MUST STAY INSIDE [project], above the sub-tables. TOML scopes a
54
- # bare key to the most recent table header, so when this sat below
55
- # [project.urls] it parsed as `project.urls.dynamic` and setuptools refused
56
- # the whole file: "`project.urls.dynamic` must be string". `pip install -e .`
57
- # failed outright, which also meant requires-python -- the entire point of
58
- # #144 -- was never enforced, because the install never got far enough to
59
- # check it. Moving a key past a table header here is not cosmetic.
60
- dynamic = ["dependencies"]
61
-
62
- [project.urls]
63
- Homepage = "https://github.com/YahyaHammad/Venastine-Research-Harness"
64
- Repository = "https://github.com/YahyaHammad/Venastine-Research-Harness"
65
- Issues = "https://github.com/YahyaHammad/Venastine-Research-Harness/issues"
66
-
67
- [project.optional-dependencies]
68
- # markitdown's only consumer is tools/builtin/file_ops.py, which implements
69
- # read/write/edit -- all three globally denied, and per S24 they cannot be
70
- # re-enabled at runtime at all (is_tool_allowed reads config.ToolPermissions
71
- # directly, settings.json has no permissions section, and D14 forbids a
72
- # ToolContext widening anything). The import is lazy, so a default install
73
- # never reaches it. It brought 11 transitive distributions, 5 of them for
74
- # markitdown alone.
75
- #
76
- # protobuf moves with it rather than staying in the default set: nothing in
77
- # the repo imports it, and the only installed distribution requiring it is
78
- # onnxruntime, which arrives through markitdown. Left behind it would pin a
79
- # transitive dependency of a package no longer installed by default.
80
- documents = ["markitdown==0.1.6", "protobuf==7.35.1"]
81
-
82
- # Optional in the code too, and documented as such at
83
- # core/reasoning/output_writer.py:185 -- the PDF path is guarded by
84
- # `except ImportError: return`. Declared here so the group has a name;
85
- # neither was ever in requirements.txt.
86
- pdf = ["markdown", "weasyprint"]
87
-
88
- [tool.setuptools.dynamic]
89
- dependencies = { file = ["requirements.txt"] }
90
-
91
- [tool.setuptools]
92
- # DECLARATIVE ONLY -- this project is run from a checkout, not installed.
93
- # `pip install .` would otherwise put `config`, `main`, `storage` and
94
- # `conftest` into site-packages as top-level names, where they collide with
95
- # anything. Empty lists mean `pip install -e .` resolves the dependencies
96
- # and enforces the Python floor without installing a single module, which
97
- # is exactly what is wanted here. README's `pip install -r requirements.txt`
98
- # remains the documented install path.
99
- packages = []
100
- py-modules = []
1
+ # Issue #144 -- requirements.txt was the whole of what this project said
2
+ # about how to install it, and it is the one packaging format that cannot
3
+ # express a Python floor or an optional group.
4
+ #
5
+ # Python 3.11 is a hard requirement, not a preference: mcp_client/client.py
6
+ # uses asyncio.timeout (3.11+), and 27 sites use runtime `X | Y` annotations
7
+ # (3.10+). On 3.10 a user got `AttributeError: module 'asyncio' has no
8
+ # attribute 'timeout'` from inside the MCP connect path, AFTER
9
+ # `pip install -r requirements.txt` reported success. requires-python turns
10
+ # that into a refusal at install time.
11
+
12
+ # setuptools>=77 is the floor for PEP 639: the SPDX `license = "Apache-2.0"` string below is
13
+ # read as a classifier expression only from that release on. An older backend treats it as a
14
+ # path and fails the build rather than warning, so this floor and that line move together.
15
+ [build-system]
16
+ requires = ["setuptools>=77"]
17
+ build-backend = "setuptools.build_meta"
18
+
19
+ [project]
20
+ name = "venastine-research-harness"
21
+ version = "0.2.0"
22
+ description = "A from-scratch agentic harness: tool-using chat plus a ten-pass self-critiquing research pipeline."
23
+ readme = "README.md"
24
+ requires-python = ">=3.11"
25
+ # PEP 639: a bare SPDX expression, not the deprecated `{ text = ... }` table, and no
26
+ # `License :: OSI Approved ::` classifier -- PEP 639 supersedes those and setuptools warns on
27
+ # both. `license-files` is declared rather than left to the backend's default glob so the file
28
+ # that ships is the one named here.
29
+ license = "Apache-2.0"
30
+ # NOTICE ships WITH the licence, not beside it in the repo only: a NOTICE that
31
+ # is not listed here exists in a checkout and is absent from every sdist and
32
+ # wheel, which defeats the reason for having one. Apache-2.0 4(d) is what makes
33
+ # the pairing meaningful downstream.
34
+ license-files = ["LICENSE", "NOTICE"]
35
+ authors = [{ name = "Yahya Hammad" }]
36
+ maintainers = [{ name = "Yahya Hammad" }]
37
+ classifiers = [
38
+ "Programming Language :: Python :: 3",
39
+ "Programming Language :: Python :: 3.11",
40
+ "Programming Language :: Python :: 3.12",
41
+ "Programming Language :: Python :: 3.13",
42
+ "Intended Audience :: Science/Research",
43
+ "Topic :: Scientific/Engineering :: Artificial Intelligence",
44
+ ]
45
+
46
+ # ONE dependency list, and it stays in requirements.txt -- the file that
47
+ # already carries the D22 rationale comments explaining why `textual` and
48
+ # `mcp` are upper-bounded. Inlining the list here would create a second
49
+ # hand-maintained copy of the same fact, which is the shape #144 was filed
50
+ # about in the first place ("a hand-maintained list is only as complete as
51
+ # the file it lives in"). setuptools strips comments and blank lines.
52
+ #
53
+ # THIS KEY MUST STAY INSIDE [project], above the sub-tables. TOML scopes a
54
+ # bare key to the most recent table header, so when this sat below
55
+ # [project.urls] it parsed as `project.urls.dynamic` and setuptools refused
56
+ # the whole file: "`project.urls.dynamic` must be string". `pip install -e .`
57
+ # failed outright, which also meant requires-python -- the entire point of
58
+ # #144 -- was never enforced, because the install never got far enough to
59
+ # check it. Moving a key past a table header here is not cosmetic.
60
+ dynamic = ["dependencies"]
61
+
62
+ [project.urls]
63
+ Homepage = "https://github.com/YahyaHammad/Venastine-Research-Harness"
64
+ Repository = "https://github.com/YahyaHammad/Venastine-Research-Harness"
65
+ Issues = "https://github.com/YahyaHammad/Venastine-Research-Harness/issues"
66
+
67
+ [project.optional-dependencies]
68
+ # markitdown's only consumer is tools/builtin/file_ops.py, which implements
69
+ # read/write/edit -- all three globally denied, and per S24 they cannot be
70
+ # re-enabled at runtime at all (is_tool_allowed reads config.ToolPermissions
71
+ # directly, settings.json has no permissions section, and D14 forbids a
72
+ # ToolContext widening anything). The import is lazy, so a default install
73
+ # never reaches it. It brought 11 transitive distributions, 5 of them for
74
+ # markitdown alone.
75
+ #
76
+ # protobuf moves with it rather than staying in the default set: nothing in
77
+ # the repo imports it, and the only installed distribution requiring it is
78
+ # onnxruntime, which arrives through markitdown. Left behind it would pin a
79
+ # transitive dependency of a package no longer installed by default.
80
+ documents = ["markitdown==0.1.6", "protobuf==7.35.1"]
81
+
82
+ # Optional in the code too, and documented as such at
83
+ # core/reasoning/output_writer.py:185 -- the PDF path is guarded by
84
+ # `except ImportError: return`. Declared here so the group has a name;
85
+ # neither was ever in requirements.txt.
86
+ pdf = ["markdown", "weasyprint"]
87
+
88
+ [tool.setuptools.dynamic]
89
+ dependencies = { file = ["requirements.txt"] }
90
+
91
+ [tool.setuptools]
92
+ # DECLARATIVE ONLY -- this project is run from a checkout, not installed.
93
+ # `pip install .` would otherwise put `config`, `main`, `storage` and
94
+ # `conftest` into site-packages as top-level names, where they collide with
95
+ # anything. Empty lists mean `pip install -e .` resolves the dependencies
96
+ # and enforces the Python floor without installing a single module, which
97
+ # is exactly what is wanted here. README's `pip install -r requirements.txt`
98
+ # remains the documented install path.
99
+ packages = []
100
+ py-modules = []