Use .venv naming in the Docling vs LlamaParse README - #813
Merged
Conversation
Matches the tutorial, which creates .venv and shows (.venv) prompts. Only the README changes; the scripts are untouched so ruff format stays green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #787, from the Final QA pass on Docling vs LlamaParse: How to Extract PDF Tables in Python.
The tutorial creates
.venvand shows(.venv) $prompts. This README still saidvenv/and(venv) $, so a reader following the download diverged from the article at the first command.python3 -m venv venv/→python3 -m venv .venv/, and the matchingsourcepath(venv) $prompts →(.venv) $README only — the scripts are untouched, so
ruff format --checkstays green.🤖 Generated with Claude Code