flex-evals 0.0.1__tar.gz
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.
- flex_evals-0.0.1/.claude/settings.local.json +10 -0
- flex_evals-0.0.1/.gitignore +207 -0
- flex_evals-0.0.1/CLAUDE.md +80 -0
- flex_evals-0.0.1/FEP.md +2295 -0
- flex_evals-0.0.1/LICENSE +201 -0
- flex_evals-0.0.1/Makefile +31 -0
- flex_evals-0.0.1/PKG-INFO +15 -0
- flex_evals-0.0.1/README.md +1 -0
- flex_evals-0.0.1/pyproject.toml +45 -0
- flex_evals-0.0.1/src/flex_evals/__init__.py +11 -0
- flex_evals-0.0.1/src/flex_evals/hello.py +33 -0
- flex_evals-0.0.1/tests/__init__.py +1 -0
- flex_evals-0.0.1/tests/test_hello.py +36 -0
- flex_evals-0.0.1/uv.lock +1073 -0
|
@@ -0,0 +1,207 @@
|
|
|
1
|
+
# Byte-compiled / optimized / DLL files
|
|
2
|
+
__pycache__/
|
|
3
|
+
*.py[codz]
|
|
4
|
+
*$py.class
|
|
5
|
+
|
|
6
|
+
# C extensions
|
|
7
|
+
*.so
|
|
8
|
+
|
|
9
|
+
# Distribution / packaging
|
|
10
|
+
.Python
|
|
11
|
+
build/
|
|
12
|
+
develop-eggs/
|
|
13
|
+
dist/
|
|
14
|
+
downloads/
|
|
15
|
+
eggs/
|
|
16
|
+
.eggs/
|
|
17
|
+
lib/
|
|
18
|
+
lib64/
|
|
19
|
+
parts/
|
|
20
|
+
sdist/
|
|
21
|
+
var/
|
|
22
|
+
wheels/
|
|
23
|
+
share/python-wheels/
|
|
24
|
+
*.egg-info/
|
|
25
|
+
.installed.cfg
|
|
26
|
+
*.egg
|
|
27
|
+
MANIFEST
|
|
28
|
+
|
|
29
|
+
# PyInstaller
|
|
30
|
+
# Usually these files are written by a python script from a template
|
|
31
|
+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
|
32
|
+
*.manifest
|
|
33
|
+
*.spec
|
|
34
|
+
|
|
35
|
+
# Installer logs
|
|
36
|
+
pip-log.txt
|
|
37
|
+
pip-delete-this-directory.txt
|
|
38
|
+
|
|
39
|
+
# Unit test / coverage reports
|
|
40
|
+
htmlcov/
|
|
41
|
+
.tox/
|
|
42
|
+
.nox/
|
|
43
|
+
.coverage
|
|
44
|
+
.coverage.*
|
|
45
|
+
.cache
|
|
46
|
+
nosetests.xml
|
|
47
|
+
coverage.xml
|
|
48
|
+
*.cover
|
|
49
|
+
*.py.cover
|
|
50
|
+
.hypothesis/
|
|
51
|
+
.pytest_cache/
|
|
52
|
+
cover/
|
|
53
|
+
|
|
54
|
+
# Translations
|
|
55
|
+
*.mo
|
|
56
|
+
*.pot
|
|
57
|
+
|
|
58
|
+
# Django stuff:
|
|
59
|
+
*.log
|
|
60
|
+
local_settings.py
|
|
61
|
+
db.sqlite3
|
|
62
|
+
db.sqlite3-journal
|
|
63
|
+
|
|
64
|
+
# Flask stuff:
|
|
65
|
+
instance/
|
|
66
|
+
.webassets-cache
|
|
67
|
+
|
|
68
|
+
# Scrapy stuff:
|
|
69
|
+
.scrapy
|
|
70
|
+
|
|
71
|
+
# Sphinx documentation
|
|
72
|
+
docs/_build/
|
|
73
|
+
|
|
74
|
+
# PyBuilder
|
|
75
|
+
.pybuilder/
|
|
76
|
+
target/
|
|
77
|
+
|
|
78
|
+
# Jupyter Notebook
|
|
79
|
+
.ipynb_checkpoints
|
|
80
|
+
|
|
81
|
+
# IPython
|
|
82
|
+
profile_default/
|
|
83
|
+
ipython_config.py
|
|
84
|
+
|
|
85
|
+
# pyenv
|
|
86
|
+
# For a library or package, you might want to ignore these files since the code is
|
|
87
|
+
# intended to run in multiple environments; otherwise, check them in:
|
|
88
|
+
# .python-version
|
|
89
|
+
|
|
90
|
+
# pipenv
|
|
91
|
+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
|
92
|
+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
|
93
|
+
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
|
94
|
+
# install all needed dependencies.
|
|
95
|
+
#Pipfile.lock
|
|
96
|
+
|
|
97
|
+
# UV
|
|
98
|
+
# Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
|
|
99
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
100
|
+
# commonly ignored for libraries.
|
|
101
|
+
#uv.lock
|
|
102
|
+
|
|
103
|
+
# poetry
|
|
104
|
+
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
|
105
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
106
|
+
# commonly ignored for libraries.
|
|
107
|
+
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
|
108
|
+
#poetry.lock
|
|
109
|
+
#poetry.toml
|
|
110
|
+
|
|
111
|
+
# pdm
|
|
112
|
+
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
|
113
|
+
# pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
|
|
114
|
+
# https://pdm-project.org/en/latest/usage/project/#working-with-version-control
|
|
115
|
+
#pdm.lock
|
|
116
|
+
#pdm.toml
|
|
117
|
+
.pdm-python
|
|
118
|
+
.pdm-build/
|
|
119
|
+
|
|
120
|
+
# pixi
|
|
121
|
+
# Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
|
|
122
|
+
#pixi.lock
|
|
123
|
+
# Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
|
|
124
|
+
# in the .venv directory. It is recommended not to include this directory in version control.
|
|
125
|
+
.pixi
|
|
126
|
+
|
|
127
|
+
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
|
128
|
+
__pypackages__/
|
|
129
|
+
|
|
130
|
+
# Celery stuff
|
|
131
|
+
celerybeat-schedule
|
|
132
|
+
celerybeat.pid
|
|
133
|
+
|
|
134
|
+
# SageMath parsed files
|
|
135
|
+
*.sage.py
|
|
136
|
+
|
|
137
|
+
# Environments
|
|
138
|
+
.env
|
|
139
|
+
.envrc
|
|
140
|
+
.venv
|
|
141
|
+
env/
|
|
142
|
+
venv/
|
|
143
|
+
ENV/
|
|
144
|
+
env.bak/
|
|
145
|
+
venv.bak/
|
|
146
|
+
|
|
147
|
+
# Spyder project settings
|
|
148
|
+
.spyderproject
|
|
149
|
+
.spyproject
|
|
150
|
+
|
|
151
|
+
# Rope project settings
|
|
152
|
+
.ropeproject
|
|
153
|
+
|
|
154
|
+
# mkdocs documentation
|
|
155
|
+
/site
|
|
156
|
+
|
|
157
|
+
# mypy
|
|
158
|
+
.mypy_cache/
|
|
159
|
+
.dmypy.json
|
|
160
|
+
dmypy.json
|
|
161
|
+
|
|
162
|
+
# Pyre type checker
|
|
163
|
+
.pyre/
|
|
164
|
+
|
|
165
|
+
# pytype static type analyzer
|
|
166
|
+
.pytype/
|
|
167
|
+
|
|
168
|
+
# Cython debug symbols
|
|
169
|
+
cython_debug/
|
|
170
|
+
|
|
171
|
+
# PyCharm
|
|
172
|
+
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
|
|
173
|
+
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
|
|
174
|
+
# and can be added to the global gitignore or merged into this file. For a more nuclear
|
|
175
|
+
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
|
|
176
|
+
#.idea/
|
|
177
|
+
|
|
178
|
+
# Abstra
|
|
179
|
+
# Abstra is an AI-powered process automation framework.
|
|
180
|
+
# Ignore directories containing user credentials, local state, and settings.
|
|
181
|
+
# Learn more at https://abstra.io/docs
|
|
182
|
+
.abstra/
|
|
183
|
+
|
|
184
|
+
# Visual Studio Code
|
|
185
|
+
# Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
|
|
186
|
+
# that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
|
|
187
|
+
# and can be added to the global gitignore or merged into this file. However, if you prefer,
|
|
188
|
+
# you could uncomment the following to ignore the entire vscode folder
|
|
189
|
+
# .vscode/
|
|
190
|
+
|
|
191
|
+
# Ruff stuff:
|
|
192
|
+
.ruff_cache/
|
|
193
|
+
|
|
194
|
+
# PyPI configuration file
|
|
195
|
+
.pypirc
|
|
196
|
+
|
|
197
|
+
# Cursor
|
|
198
|
+
# Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
|
|
199
|
+
# exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
|
|
200
|
+
# refer to https://docs.cursor.com/context/ignore-files
|
|
201
|
+
.cursorignore
|
|
202
|
+
.cursorindexingignore
|
|
203
|
+
|
|
204
|
+
# Marimo
|
|
205
|
+
marimo/_static/
|
|
206
|
+
marimo/_lsp/
|
|
207
|
+
__marimo__/
|
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
# CLAUDE.md
|
|
2
|
+
|
|
3
|
+
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
|
4
|
+
|
|
5
|
+
## Project Overview
|
|
6
|
+
|
|
7
|
+
This is the **flex-evals** project, a Python implementation of the Flexible Evaluation Protocol (FEP) - a vendor-neutral, schema-driven standard for measuring the quality of any system that produces complex or variable outputs, particularly LLMs and agentic workflows.
|
|
8
|
+
|
|
9
|
+
### Key Architecture Components
|
|
10
|
+
|
|
11
|
+
- **Core Protocol**: Implements FEP schema-driven evaluation framework with test cases, outputs, checks, and results
|
|
12
|
+
- **Standard Checks**: Boolean, numeric, categorical, and free-text assessments using JSONPath expressions
|
|
13
|
+
- **Extended Checks**: LLM/agentic evaluations including semantic similarity and LLM judge checks
|
|
14
|
+
- **API Interface**: REST and gRPC APIs for running evaluations locally or at scale
|
|
15
|
+
|
|
16
|
+
### Dependencies
|
|
17
|
+
|
|
18
|
+
- Core: `jsonpath-ng`, `pydantic`, `python-dotenv`, `pyyaml`, `requests`, `ruamel-yaml`, `tenacity`, `tiktoken`
|
|
19
|
+
- Dev: `pytest`, `coverage`, `ruff`, `faker`, `pytest-asyncio`, `pytest-mock`, `pytest-timeout`
|
|
20
|
+
|
|
21
|
+
## Development Commands
|
|
22
|
+
|
|
23
|
+
### Build and Package
|
|
24
|
+
```bash
|
|
25
|
+
# Build package
|
|
26
|
+
make package-build
|
|
27
|
+
|
|
28
|
+
# Publish package (requires UV_PUBLISH_TOKEN)
|
|
29
|
+
make package-publish
|
|
30
|
+
|
|
31
|
+
# Full package workflow
|
|
32
|
+
make package
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
### Testing and Quality
|
|
36
|
+
```bash
|
|
37
|
+
# Run linting
|
|
38
|
+
make linting
|
|
39
|
+
# Equivalent to:
|
|
40
|
+
# uv run ruff check src/flex_evals/
|
|
41
|
+
# uv run ruff check tests/
|
|
42
|
+
|
|
43
|
+
# Run tests with coverage
|
|
44
|
+
make unittests
|
|
45
|
+
# Equivalent to:
|
|
46
|
+
# uv run coverage run -m pytest --durations=0 tests
|
|
47
|
+
# uv run coverage html
|
|
48
|
+
|
|
49
|
+
# Run all quality checks
|
|
50
|
+
make tests
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
### Package Management
|
|
54
|
+
```bash
|
|
55
|
+
# Add new dependency
|
|
56
|
+
uv add <package_name>
|
|
57
|
+
|
|
58
|
+
# Add dev dependency
|
|
59
|
+
uv add --dev <package_name>
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
## Test Configuration
|
|
63
|
+
|
|
64
|
+
- **Framework**: pytest with asyncio support
|
|
65
|
+
- **Test Path**: `tests/` directory
|
|
66
|
+
- **Python Path**: `src/` for imports
|
|
67
|
+
- **Timeout**: 60 seconds per test with signal method (Unix only)
|
|
68
|
+
- **Coverage**: HTML reports generated in `htmlcov/`
|
|
69
|
+
|
|
70
|
+
## Project Status
|
|
71
|
+
|
|
72
|
+
This appears to be an early-stage implementation of the FEP specification. The project structure is set up but the actual Python implementation files are not yet present in the `src/flex_evals/` directory.
|
|
73
|
+
|
|
74
|
+
## Important Notes
|
|
75
|
+
|
|
76
|
+
- Uses `uv` for dependency management and task running
|
|
77
|
+
- Follows FEP protocol specification (detailed in FEP.md)
|
|
78
|
+
- Designed for evaluating both deterministic and non-deterministic systems
|
|
79
|
+
- Supports JSONPath expressions for flexible data extraction
|
|
80
|
+
- Implements both synchronous and streaming evaluation interfaces
|