[Bug]: Not Compatible with Python 3.14 (lxml dependency failure)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 52/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- python
- Ambito
- build-system
Direzione di ricerca
Start by reproducing the Windows 11/Python 3.14 installation with the current dependency metadata and verify the lxml version resolution. Inspect the project’s package metadata and Python-version classifiers, then compare installation behavior with lxml 5.4.0 and 6.0.2. Done means Python 3.14 installs successfully or is rejected with a clear support message, with existing supported versions unaffected.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
crawl4ai version
0.8.6
Summary
Crawl4AI installation fails in Python 3.14 environment due to lxml~=5.3.
Using lxml 6.0.2 works!
AI Analysis
pip install crawl4ai fails on Windows with Python 3.14 due to lxml~=5.3 source build error
Body
Describe the bug
Installing crawl4ai on Windows with Python 3.14 fails during dependency installation when pip tries to build lxml from source.
The failure appears related to Crawl4AI depending on lxml~=5.3, which resolves to lxml 5.4.0 in my environment. On Windows + Python 3.14, pip does not appear to find a compatible wheel and falls back to a native source build, which then fails because libxml2 headers/libraries are not available.
To Reproduce
- On Windows, create a fresh virtual environment with Python 3.14
- Run:
pip install crawl4ai
- Installation fails while building
lxml
Expected behavior
pip install crawl4ai should either:
- install successfully on Python 3.14, or
- fail early with a clear message that Python 3.14 is not currently supported
Actual behavior
Installation fails while building lxml from source.
Error output
Building wheels for collected packages: lxml
Building wheel for lxml (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for lxml (pyproject.toml) did not run successfully.
│ exit code: 1
...
fatal error C1083: Cannot open include file: 'libxml/xmlversion.h': No such file or directory
Compile failed: command '...\\cl.exe' failed with exit code 2
...
fatal error C1083: Cannot open include file: 'libxml/xpath.h': No such file or directory
*********************************************************************************
Could not find function xmlXPathInit in library libxml2. Is libxml2 installed?
Is your C compiler installed and configured correctly?
*********************************************************************************
ERROR: Failed building wheel for lxml
Failed to build lxml
error: failed-wheel-build-for-install
× Failed to build installable wheels for some pyproject.toml based projects
╰─> lxml
Environment
- OS: Windows 11
- Python: 3.14.2
- pip: latest available at time of test
- Compiler/tooling: Visual Studio 2022 C++ tools detected in build log
Additional context
Current Crawl4AI PyPI metadata appears to declare:
Requires-Python: >=3.10- Python classifiers for:
- 3.10
- 3.11
- 3.12
- 3.13
But not 3.14.
Current dependency metadata also includes:
lxml~=5.3
So this may be a Python 3.14 compatibility gap caused by the current lxml version range, rather than a general Windows install problem.
Suggested fix
Possible options:
- Explicitly document that Python 3.14 is not yet supported
- Add a clearer install-time guard or message for unsupported Python versions
- Relax/update the
lxmldependency if a newer version line works with Python 3.14 - Document a recommended Python version such as 3.12 or 3.13 for Windows users
Workaround
Using Python 3.12 or 3.13 appears to be the safest workaround.
Current Behavior
Installation fails with error.
Is this reproducible?
Yes
OS
Windows
Python version
3.14
Browser
No response
Browser version
No response
Error logs & Screenshots (if applicable)
No response
- Lingua principale
- Python
- Stelle
- 85.4k
- Fork
- 8.9k
- Merge medio
- 5g 7h
- PR unite (30g)
- 23
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di unclecode/crawl4ai
-
[Bug]: Since 0.9.1, Linux launches chrome-headless-shell instead of ChromiumForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: BestFirstCrawlingStrategy fetches a full batch past max_pagesForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
unclecode/crawl4ai#2381 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: CrawlerRunConfig.clone() drops fallback_fetch_function, so deep crawls never use itForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Docker memory guard reads host RAM when no container limit is set — cgroup v2 "max" defeats get_container_memory_percentForse già presa @Battleplus l’ha presa 54 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
unclecode/crawl4ai#2123 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: After a streamed deep crawl is stopped early, the next deep crawl returns only the start pageForse già presa @PiUnknown l’ha presa 2 giorni fa. Aperta
Difficoltà 4/5 1-2 giorni Idoneità per principianti 12/100
unclecode/crawl4ai#2380 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di unclecode/crawl4ai
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
TomerAberbach/profiler-md#733 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
its-me-prash/vwgroup-connect-ha#1858 ·
I maintainer di solito rispondono entro 1 giorno
-
area: client bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Deleting all alarms or timers shows deleted ones until the next update when there are none leftApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
leikoilja/ha-google-home#1107 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Graphify-Labs/graphify#4524 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno