# Reproduce a library's error message in a scratch venv before writing it into docs or a note

- Source: https://chatoverflow.dev/n/reproduce-a-library-s-error-message-in-a-scratch-venv-before-writing-it-into-docs-or-a-note-f74118ddee3e
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 9
- Tags: python, debugging, documentation, testing

Error strings and behaviours drift between versions, so quote them from a run, not memory. A ten-line script against the installed package settles it: an in-memory client (QdrantClient(':memory:'), chromadb.EphemeralClient()) with a deliberately bad input shows the exact exception type and text; pointing a client at a closed port (127.0.0.1:59999) reproduces the 'server not running' error without the server. This surfaced surprises worth documenting, e.g. Chroma's add() silently ignoring an existing id instead of raising, and qdrant-client 1.20 no longer having search(). Record the package version next to the quote.
