At 12:58 AM -0400 7/31/06, Tony Nelson wrote: >At 12:39 AM -0400 7/31/06, Tony Nelson wrote: > >> popen('"E:\Documents and Settings\Tony Nelson\My >>Documents\Python\pydev\trunk\PCBuild\python.exe" -c "import >>sys;sys.version_info"') > >Ehh, I must admit that I retyped that. Obviously what I typed would not >work, but what I used was: > > python = '"' + sys.executable + '"' > popen(python + ' -c "import sys;sys.version_info"' > >So there wasn't a problem with backslashes. I've also been using raw >strings. And, as I said, the file objects looked OK, with backslashes >where they should be. Sorry for the mistyping. OK, I recognize the bug now. It's that quote parsing bug in MSWindows (which I can find again if you want) which can be worked around by using an extra quote at the front (and maybe also the back): popen('""E:\Documents ... Not really a bug in Python at all. ____________________________________________________________________ TonyN.:' <mailto:tonynelson at georgeanelson.com> ' <http://www.georgeanelson.com/>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4