New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
distutils does not show any error msg when can't build C module extensions due to a missing C compiler #49181
Comments
Today I was trying to compile a module using an extension in C and Python 2.5: D:\pyftpdlib\svn\psutil\trunk>C:\python25\python.exe setup.py install Python 2.6: D:\pyftpdlib\svn\psutil\trunk>C:\python26\python.exe setup.py install |
What is the specific error you are reporting? |
Currently I haven't any C compiler installed on my system so I expect |
The problem has two causes:
This function should not be used IMO. Its docstring claims that it Patch attached. |
Tarek: This patch seems reasonable to me, is this something that can be applied? |
I guess i can be applied on distutils, and backported in distutils2. I'll do it in the coming days. Notice that I am now applying only bug fixes and regression fixes now for distutils. |
I will commit this if Tarek does not do it shortly. In distutils2, I’ll remove grok_environment_error wholly, since it exists for 1.5 compat only. |
Giampaolo, can you test Amaury’s patch? I’d prefer some testing before committing. |
I don't have the same setup I had at the time when I submitted the first message so maybe something has changed in meantime. C:\Documents and Settings\foo\Desktop\psutil>setup.py build Although the message is improved ("Unable to find vcvarsall.bat" vs "None") it seems the patch had no effect. |
Any chance of getting this patch applied? It clearly makes the error message more useful, and we've run into another case where grok_environment_error gives the wrong result: when symlinking fails because the target exists, it now says "File exists: <source>", because e.filename is the source and e.filename2 the target. It's also rather embarassing that a function in Python 3.4 still says "Handles Python 1.5.1 and 1.5.2 styles..." in the docstring. |
I want to make time for Python bugs again, so I’ll try and finish this bug soon. See also msg200785 for a report from setuptools with an easy to reuse test case. |
New changeset a865f6fb82b4 by Éric Araujo in branch '2.7': |
New changeset 0f1237b61f58 by Éric Araujo in branch '2.7': |
New changeset 504eb00998f2 by Éric Araujo in branch '3.3': New changeset c7bd0f953687 by Éric Araujo in branch 'default': |
Happy to close this as fixed. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: