Pylint is doing something odd on my Windows box - something that shouldn't be possible. This isn't a question about fixing pylint, so much as fixing my understanding.
I have a typical install of the latest version of pylint, Python 2.6 and Windows Vista.
If I open a Command Prompt, and run pylint from the command line, it executes successfully, then when it gets to the end of the program, it doesn't merely exit to the command line again, but closes the entire Command Prompt window.
I had a brief look at the code online (which I assume is the code that is actually being run) and they are calling sys.exit() with various error levels, but my reading and testing suggests that should still just return to the command line with the appropriate error-level set.
Pylint is also run as part of my project's testing regime, and it works there, suggesting to me that if it is called as a Python method rather from the command-line, it doesn't have the same problem (probably no call to sys.exit() in this code path.)
By what mechanism could pylint close the "shell" that contained it?
If this a bug in Pylint? I don't see how. A bug in Python? A bug in Windows?