Chris Adams

@auvipy That's a very good point – that might be a good pilot project, simply forking the existing simple backend to produce a Postgres-specific one with minimal overhead beyond core...

@gfairchild I still think the best approach would be creating a separate project with a new backend based on the existing simple backend (we could host that repo under the...

Haystack has a “simple” backend which uses the ORM. I think it would be relatively straight forward to use that as a basis for a Postgres extension — i.e. faceting...

What does the `SearchQuery` (i.e. `sqs.query`) look like? Does that `__in` query retrieve the documents if you use it directly rather than exclude it?

> Thanks for engaging on the design! > > I think that `uv project` might be weird since all the other "project" commands are top-level, e.g., `init`, `sync`, `lock` are...

So that’s probably a usability issue since it should be consistent with `poetry env use` but that was just my reduction for this. My real projects had values like `^3.12.5`....

There are two issues: one is that the `poetry init --python` has an undocumented inconsistency with `poetry env use`, where the latter will accept things like `3.11` and use the...

> So the first is talking about versions and the later about the executable. The first part is correct but the second is misleading because it technically accepts both. As...

There've been some more semi-documented changes and it's possible to get Poetry to in some cases do the right thing by changing your `pyproject.toml` file to use `[project]` section with...

> For Poetry 2, specifying exactly the same constraint for `project.requires-python` and `tool.poetry.dependencies.python` is redundant. See https://python-poetry.org/docs/pyproject/#requires-python for example. I’m aware of the documentation, which is why I was surprised...