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 r.david.murray
Recipients asvetlov, chris.jerdonek, ezio.melotti, gregory.p.smith, neologix, pitrou, r.david.murray, tim.golden
Date 2012-11-02.21:28:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351891715.41.0.501283846703.issue16353@psf.upfronthosting.co.za>
In-reply-to
Content
The "system default shell" (which should always be a /bin/sh workalike, I think) should always be the default.  Any other shell should be something that has to be specified explicitly.  At least, that's the way most posix programs work, I think.  As Chris said, different shells can use different syntax, so if you want to write portable code you want to be able to expect /bin/sh by default.

So at a minimum we want a function for the system default shell.  Anything else is a bonus :)
History
Date User Action Args
2012-11-02 21:28:35r.david.murraysetrecipients: + r.david.murray, gregory.p.smith, pitrou, tim.golden, ezio.melotti, asvetlov, chris.jerdonek, neologix
2012-11-02 21:28:35r.david.murraysetmessageid: <1351891715.41.0.501283846703.issue16353@psf.upfronthosting.co.za>
2012-11-02 21:28:35r.david.murraylinkissue16353 messages
2012-11-02 21:28:35r.david.murraycreate