Bugs item #1711608, was opened at 2007-05-02 20:34 Message generated for change (Comment added) made by collinwinter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1711608&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Extension Modules Group: Python 2.5 Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Steve Cassidy (stevecassidy) Assigned to: Nobody/Anonymous (nobody) Summary: CGIHttpServer fails if python exe has spaces Initial Comment: In addition to the problem noted in #1436206 with spaces in the file names of scripts being executed, if Python has been installed in a directory with spaces (C:\Program Files\Python) the server will fail to execute the script because the name of the executable is not quoted properly. My attempts to fix this have failed since just putting quotes around the exe name "C:\\Program Files\..." doesn't work, however we have found that just quoting the part of the path with spaces 'C:\\"Program Files"\\...' will work. It seems a bit odd that this bug has persisted for so long. A fix would be nice since this module is really good to give to my students (doing python web development for the first time) so they don't have to worry about server installation issues. Steve ---------------------------------------------------------------------- >Comment By: Collin Winter (collinwinter) Date: 2007-06-05 19:37 Message: Logged In: YES user_id=1344176 Originator: NO I did not close this bug because it's unimportant; I closed it because it's already on file (#1436206), and there's no sense in having multiple tracker entries for the same issue. That said, problems on Windows are less likely to get fixed or noticed because relatively few core developers have access to Windows platforms. We would greatly appreciate a patch that fixes this. ---------------------------------------------------------------------- Comment By: Steve Cassidy (stevecassidy) Date: 2007-06-05 19:28 Message: Logged In: YES user_id=105411 Originator: YES I understand that the default install location is non-standard becuase Python has trouble at times with spaces in filenames. However, if this is an engineering decision is there a trace of the bugs that are avoided because of it? The user isn't warned on installation not to choose a location with spaces to avoid problems x y and z. A regular windows user will find it odd that Python wants to be installed in C:\Python and I would imagine that in many managed environments this won't be possible. So the response to this bug shouldn't be just to close it, maybe it needs a patch to warn people of the issue when installing python at the least. In the longer term though it seems really odd that Python can't solve this relatively simple problem that other envionments have no trouble with. Steve ---------------------------------------------------------------------- Comment By: Collin Winter (collinwinter) Date: 2007-06-05 13:56 Message: Logged In: YES user_id=1344176 Originator: NO This issue is a duplicate of #1436206. Closing. ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2007-05-08 15:11 Message: Logged In: YES user_id=21627 Originator: NO I don't find it odd that the bug persisted for so long: there is a reason that the default installation of Python does *not* go into "Program Files", as spaces in file names produce endless problems. Quoting the paths should work, though - don't forget to quote arguments as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1711608&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
