New submission from klo uo:
I noticed this issue, while trying to compile Cython extension, when source
file is in path with spaces. Extension wouldn't compile because LIBDIR is
passed to MinGW g++ (though not to gcc) or MSVC compilers unquoted. I tracked
the problem to "
klo uo added the comment:
> Can you fix the bare except?
...
except ImportError:
pass
--
___
Python tracker
<http://bugs.python.org/issu
klo uo added the comment:
> klo.uo: can you kindly provide a working (or, rather, failing)
> example? A trivial "hello-world" kind of package could do, along
> with a report what path you unpacked it in, and what error you get.
As mentioned in opening thread, this doesn
klo uo added the comment:
I found two similar issues:
1. distutils compiler not handling spaces in path to output/src files:
http://bugs.python.org/issue4508
with patches for unix compiler and cygwin compiler
2. Distutils does not put quotes around paths that contain spaces when
compiling
New submission from klo uo:
Example code:
Python 3.4.3 (default, Oct 14 2015, 20:28:29)
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import shlex
>&
klo uo added the comment:
So there is no reliable way for converting chained command line sequence to
string on *nix, when I have to to use string as shell=True?
--
___
Python tracker
<http://bugs.python.org/issue27
