Yeah, it's to allow for whitespace characters. Otherwise, it's not possible to do expressions or any other sort of content containing whitespace. The whitespace will only end up in the value if explicitly quoted on the shell.

I looked through the other command line arguments and didn't see any that seemed they would be impacted by this change, and sys.argv already handles whitespace between arguments. I may have missed something important though.