Summary
Several PaddleOCR-VL manual-install docs currently state that Python 3.8–3.13 is a hard requirement.
From a reader's perspective, that wording reads as “newer Python versions will not work”. In practice, that is stricter than what the docs seem to intend.
Why this is confusing
The same docs are describing a documented manual-install path, not a strict runtime gate enforced by PaddleOCR-VL itself.
I locally validated the following before opening this issue:
- editable install of current
paddleocr on Python 3.13: success
- editable install of current
paddleocr on Python 3.14: success
- editable install of current
langchain-paddleocr on Python 3.14: success
- install/import of released
paddleocr==3.4.1 on Python 3.14: success
paddleocr --help on Python 3.14: success
That does not prove full official 3.14 support across all environments, but it does suggest the current wording is better framed as a verified/documented range rather than a hard prohibition.
Suggested direction
Would you be open to changing the repeated wording in the PaddleOCR-VL docs from a hard requirement to something like:
This guide officially covers Python 3.8–3.13; newer versions may still work when compatible PaddlePaddle wheels are available, but they are outside the documented verification scope here.
I can send a small docs-only PR if this direction makes sense.
Summary
Several PaddleOCR-VL manual-install docs currently state that Python 3.8–3.13 is a hard requirement.
From a reader's perspective, that wording reads as “newer Python versions will not work”. In practice, that is stricter than what the docs seem to intend.
Why this is confusing
The same docs are describing a documented manual-install path, not a strict runtime gate enforced by PaddleOCR-VL itself.
I locally validated the following before opening this issue:
paddleocron Python 3.13: successpaddleocron Python 3.14: successlangchain-paddleocron Python 3.14: successpaddleocr==3.4.1on Python 3.14: successpaddleocr --helpon Python 3.14: successThat does not prove full official 3.14 support across all environments, but it does suggest the current wording is better framed as a verified/documented range rather than a hard prohibition.
Suggested direction
Would you be open to changing the repeated wording in the PaddleOCR-VL docs from a hard requirement to something like:
I can send a small docs-only PR if this direction makes sense.