This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients eric.araujo, eric.smith, niemeyer, robodan
Date 2011-11-25.17:01:18
SpamBayes Score 1.0697431e-08
Marked as misclassified No
Message-id <1322240479.95.0.427549844498.issue1521950@psf.upfronthosting.co.za>
In-reply-to
Content
> Of course, that's how it's used.  That's all it can do right now.
:) What I meant is that it is *meant* to be used in this way.

> I was was splitting and combining commands (using ;, &&, and ||) and then running the resulting
> (mega) one liners over ssh.  It still gets run by a shell, but I was specifying the control flow.
Thank you for the reply.  It is indeed a valuable use case to pass a command line as one string to ssh, and the split/quote combo should round-trip and be useful for this usage.

> I'll see if I can come up with a reference case and maybe a unittest this weekend
Great!  A new argument (with a default value which gets us the previous behavior) will probably be needed, to preserve backward compatibility.
History
Date User Action Args
2011-11-25 17:01:20eric.araujosetrecipients: + eric.araujo, niemeyer, eric.smith, robodan
2011-11-25 17:01:19eric.araujosetmessageid: <1322240479.95.0.427549844498.issue1521950@psf.upfronthosting.co.za>
2011-11-25 17:01:19eric.araujolinkissue1521950 messages
2011-11-25 17:01:19eric.araujocreate