[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Irit Katriel]

Change by Irit Katriel :


--
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Martin Panter]

Martin Panter added the comment:

I presume the problem is that Free BSD’s “type” command outputs the error to 
the shell’s original stderr, rather than the one given on the “type” command 
line. If so, the Python 3 patches for Issue 22636 should avoid it by using 
shutil.which() instead.

However that function does not exist in Python 2, so a different solution needs 
to be found. Probably an improved version of Eric’s patch would be good.

--
dependencies: +avoid using a shell in ctypes.util: replace os.popen with 
subprocess
stage: patch review -> needs patch
versions: +Python 2.7 -Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Meador Inge]

Changes by Meador Inge :


--
nosy: +meador.inge

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Martin Panter]

Martin Panter added the comment:

It would be good to close the file when it’s no longer needed. Also, if this 
bug is relevant to Python 3, I would use open() rather than file().

--
nosy: +martin.panter
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Mark Lawrence]

Changes by Mark Lawrence breamore...@yahoo.co.uk:


--
nosy:  -BreamoreBoy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6338
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Mark Lawrence]

Mark Lawrence breamore...@yahoo.co.uk added the comment:

The patch simply sends the error message to os.devnull.  I can't test it as 
posix, but can it be committed as is?

--
nosy: +BreamoreBoy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6338
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6338] Error message displayed on stderr when no C compiler is present with ctypes

[Eric Huss]

New submission from Eric Huss e...@huss.org:

Importing the uuid module on a posix system (FreeBSD in my case) that
does not have a C compiler causes cc: not found to be sent to stderr.
 This is because it imports ctypes and calls ctypes.util.find_library
which attempts to determine if the C compiler is called gcc or cc
using a shell command.

--
assignee: theller
components: ctypes
files: ctypes_util.patch
keywords: patch
messages: 89681
nosy: ehuss, theller
severity: normal
status: open
title: Error message displayed on stderr when no C compiler is present with 
ctypes
versions: Python 2.6
Added file: http://bugs.python.org/file14357/ctypes_util.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6338
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com