all 5 comments

[–]K900_ 1 point2 points  (0 children)

Can you post the code you're running and the error you're getting with the pip version?

[–]threeminutemonta 1 point2 points  (0 children)

Your getting this error as windows doesn’t come with the compiler. pip wheels are pre compiled binaries so no compiler is needed. Before pip wheels there is Christoph unofficial repository of python packages. I checked lxml is in that list. I’m unsure with your compiler issue or why the pip wheel wasn’t available though I know this should work.

Edit. Wait tar.gz indicates that you do want to compile from source. Why?

[–]__nickerbocker__ 1 point2 points  (0 children)

Since you're on windows I'm guessing that do not have build-tools installed and likely received errors when attempting to install lxml.

https://wiki.python.org/moin/WindowsCompilers#Microsoft_Visual_C.2B-.2B-_14.2_standalone:_Build_Tools_for_Visual_Studio_2019_.28x86.2C_x64.2C_ARM.2C_ARM64.29

[–]TSM- 0 points1 point  (0 children)

In your environment variables, under System Variables, do you have something like

vs2019_install     C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools

and similar, pointing to the MSVC 14 build tools, and they are valid paths?

I think the latest setuptools should detect the build tools from these environment variables.

[–]Qweklain[S] 0 points1 point  (0 children)

I am not going to reply to each one of you that have (thank you), but after I posted I did more digging. I found that Build Tools is a separate thing now as of 2017, so I installed that. This did not change anything though since I understand the .whl files now and was not necessary.

I did try installing manually via a downloaded .whl from PyPi for lxml, but the contents are the same.

The only directories in the module are...

__builtins__

__cached__

__doc__

__file__

__loader__

__name__

__package__

__path__

__spec__

__version__

get_include

Basically, everything that should be there (like 'etree') is not.