You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
======================================================================
FAIL: test_process_cmdline (_windows.WindowsSpecificTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Users\user\Desktop\svn\psutil\test\_windows.py", line 96,
in test_process_cmdline
self.assertEqual(' '.join(p.cmdline), w.CommandLine)
AssertionError: 'C:\\Python27\\python.exe -c import time;
time.sleep(3600);' != u'C:\\Python27\\python.exe -c "import time; time.sleep(3600);"'
----------------------------------------------------------------------
Verified that both procexp and process hacker tools do not have this issue.
I took a look at process_info.c and didn't notice anything weird so I
have no clue on where I might look.
We're returning an array of process arguments, not a string... I
would think this is expected behavior. This is similar to what you
get from sys.argv where the arguments are already parsed, which is
what CommandLineToArgvW is supposed to do, and we return the
corresponding array of strings as a Python list.
Verified that the same thing happens on Linux and BSD/OSX.
Thinking back I guess it's ok to return strings without quotation
marks as well, also because that's what you would pass to
subprocess.Popen in case you want to attempt to restart the process, for example.
I'm going to close this out and modify the test case.
From g.rodola on October 17, 2010 22:17:27
Original issue: http://code.google.com/p/psutil/issues/detail?id=118
The text was updated successfully, but these errors were encountered: