Closed wroyca closed 11 months ago
Huh? lxml
is listed as a requirement in requirements.txt, and is included by the pip install script. This likely isn't a bug in poxy, but something amiss with your local python environment.
Actually, wait. This suggests otherwise. Well, I'm confused; I use windows as my daily driver and haven't run into this O_O
Ah, that page lists the binary page you've linked above. I see now 😅
Not sure what a good solve for this is, since I can't automate that in the installer (I don't think). I guess just documenting it?
Ah, that page lists the binary page you've linked above. I see now 😅
Not sure what a good solve for this is, since I can't automate that in the installer (I don't think). I guess just documenting it?
Seems reasonable :)
Hmmn, the lxml docs say this:
If you fail to build lxml on your MS Windows system from the signed and tested sources that we release, consider using the binary builds from PyPI [...]
I'm confused about what this is saying. To me this means pip install lxml
should do the right thing on windows? That tracks with my experience so far, at least, but I'm not sure if this is a case of correlation and not causation...
I tried but it didn't work, I ended up with more gibberish errors. Unfortunately, I don't have the logs anymore, but it may be worth trying again
it may be worth trying again
Yup. I'd like to test this on a 'clean room' PC at some point, one that I haven't been doing any dev tasks on - I'm concerned that all my use of Poxy on windows has always been on machines that I've also done dev stuff on and may have accidently installed the libxml prerequisites through some other means.
No longer the case, closing. :)
Can be fixed by installing lxml-4.9.0-cp311-cp311-win_amd64.whl from https://www.lfd.uci.edu/~gohlke/pythonlibs/#lxml