[issue4508] distutils compiler not handling spaces in path to output/src files

2021-02-03 Thread Steve Dower
Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If

[issue4508] distutils compiler not handling spaces in path to output/src files

2018-08-12 Thread Greg Toombs
Greg Toombs added the comment: Confirmed still broken in 3.6.3. I ran into this when running CFFI. It does very wrong things with the path to cl.exe and include files with path spaces. My workaround is to monkeypatch distutils.ccompiler.gen_preprocess_options such that include paths are

[issue4508] distutils compiler not handling spaces in path to output/src files

2014-07-30 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- components: -Distutils2 nosy: +dstufft versions: +Python 3.4, Python 3.5 -3rd party, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4508

[issue4508] distutils compiler not handling spaces in path to output/src files

2014-03-07 Thread Éric Araujo
Éric Araujo added the comment: Thanks Brian, let’s try and get this fixed. I've put together a patch adding the test requested. There is no problem on my Ubuntu machine with python 3.3. Are you saying the test does not reproduce the bug discussed here? There is a comment in the file saying

[issue4508] distutils compiler not handling spaces in path to output/src files

2014-03-03 Thread Alexandru Gheorghe
Alexandru Gheorghe added the comment: I am having the same issue on Debian 7 x86-64 (3.2.0-4-amd64) Python 2.7.3 (default, Jan 2 2013, 13:56:14) // [GCC 4.7.2] on linux2 Not noticing this bug I've opened a duplicate, for which the interesting comment can be found here:

[issue4508] distutils compiler not handling spaces in path to output/src files

2012-08-05 Thread Brian Thorne
Brian Thorne added the comment: I've put together a patch adding the test requested. There is no problem on my Ubuntu machine with python 3.3. There is a comment in the file saying Don't load the xx module more than once, I am unsure whether my patch (using a renamed c file) violates this?

[issue4508] distutils compiler not handling spaces in path to output/src files

2012-05-07 Thread fishdude
fishdude fishd...@gmx.net added the comment: i have to report that this issue also happens on Linux and Mac as well. no matter wether python 2.6 or 2.7 is used. -- components: +Macintosh nosy: +fishdude versions: +Python 2.6 ___ Python tracker

[issue4508] distutils compiler not handling spaces in path to output/src files

2012-05-07 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Thanks for the confirmation. Note that the versions field in this bug tracker indicates the versions that will get fixed, not all versions with the bug; 2.6 only gets security fixes now. Are you interested in updating the patch with a test

[issue4508] distutils compiler not handling spaces in path to output/src files

2011-11-18 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Ok, I found a similar problem with MMTK. I don’t know what that is. I am currently altering my distutils package to add a function called nt_quote_dir that adds quotes to paths with spaces and then applies it to each path if the platform

[issue4508] distutils compiler not handling spaces in path to output/src files

2011-11-16 Thread ipatrol
ipatrol ipatrol6...@yahoo.com added the comment: Ok, I found a similar problem with MMTK. I am currently altering my distutils package to add a function called nt_quote_dir that adds quotes to paths with spaces and then applies it to each path if the platform is win32. When I'm done I will

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Brian Thorne
Brian Thorne hardb...@gmail.com added the comment: Comments on the SciPy-Dev mailing list: While testing Scipy's weave on several different Windows installations, I came across some problems with spaces in paths that often prevent weave from working. I can see a change that could probably get

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I tried using a space in a directory rather than in the file name and it worked. Thorney, can you repost your example as plain text files (separate source files or a diff against an empty dir) or at worst in an archive format readable by free

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Brian Thorne
Brian Thorne hardb...@gmail.com added the comment: Sorry, here is the example as a diff against an empty directory. (I'm 100% sure the Ubuntu archiving program that I just used is free software though...) -- Added file: http://bugs.python.org/file18638/example.diff

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I can’t open the archive with unrar-free, and can’t apply the diff with patch (tried context mode and ed mode). Would you mind making it a unified diff this time? -- ___ Python tracker

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Brian Thorne
Changes by Brian Thorne hardb...@gmail.com: Removed file: http://bugs.python.org/file18638/example.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4508 ___

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Brian Thorne
Brian Thorne hardb...@gmail.com added the comment: Hopefully this works! Otherwise would a tar.gz or a zip archive be ok? -- Added file: http://bugs.python.org/file18640/4508example.diff ___ Python tracker rep...@bugs.python.org

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-08-24 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Thanks, this time it worked. I had to remove the example.i source file in setup.py since I don’t have swig installed, but apart from that, compiling “ex ample.c” or “ex ample/ex ample.c” worked. Next steps: - Write something similar to your

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-05-15 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- assignee: tarek - sjoerd components: +Distutils2 -Distutils nosy: +merwok, sjoerd versions: +Python 2.5, Python 3.2 -Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4508

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-05-15 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: (Fixing damn HTML form changing select values, really sorry) -- assignee: sjoerd - tarek nosy: -sjoerd ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4508

[issue4508] distutils compiler not handling spaces in path to output/src files

2010-05-15 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4508 ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4508] distutils compiler not handling spaces in path to output/src files

2009-03-18 Thread C. E. Ball
C. E. Ball ceb...@users.sf.net added the comment: I also found this bug while using SciPy's weave on Windows XP to compile some inline c/c++ code. Thorney's distutils_compiler_quoting.patch fixed the problem for me. Here is the relevant part of the traceback (I hope): Found executable

[issue4508] distutils compiler not handling spaces in path to output/src files

2009-01-17 Thread Tarek Ziadé
Tarek Ziadé ziade.ta...@gmail.com added the comment: I couldn't reproduce the problem yet, using your sample. I tried to compile on Mac OSX (Python 2.5 GCC) and Windows XP (Python 2.5 , MinGW 5.1.4 and SWIG 1.2.3) and it worked well. The output was right, (the .o file has a space, but the

[issue4508] distutils compiler not handling spaces in path to output/src files

2009-01-11 Thread Brian Thorne
Brian Thorne hardb...@gmail.com added the comment: Ok - this bug has nothing to do with weave itself. I think any extension written in C or C++ that has a space in the filename will raise the error in both windows and gnu/linux. Here is a simple c extension with and without spaces. The one with

[issue4508] distutils compiler not handling spaces in path to output/src files

2008-12-31 Thread Tarek Ziadé
Tarek Ziadé ziade.ta...@gmail.com added the comment: Hi. I am not familiar with weave. Could you provide a small sample of code that raises this issue. This way, I will be able to write the standalone test we can integrate in distutils together with your fix. -- assignee: - tarek nosy:

[issue4508] distutils compiler not handling spaces in path to output/src files

2008-12-10 Thread Martin v. Löwis
Martin v. Löwis [EMAIL PROTECTED] added the comment: The patch hasn't been accepted for the trunk, yet, so it is not a candidate for a 2.5 backport. -- nosy: +loewis versions: -Python 2.1.1, Python 2.1.2, Python 2.2, Python 2.2.1, Python 2.2.2, Python 2.2.3, Python 2.3, Python 2.4,

[issue4508] distutils compiler not handling spaces in path to output/src files

2008-12-03 Thread Brian Thorne
New submission from Brian Thorne [EMAIL PROTECTED]: I found this bug when using scipy's weave and having some inline C/C++ code. Weave uses distutils to compile the source in its own directory, python was installed under program files. Unfortunately it doesn't seem to handle spaces in the path