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 asvetlov
Recipients asvetlov, chris.jerdonek, christian.heimes, eric.araujo, ezio.melotti, gregory.p.smith, lyapun, neologix, pitrou, r.david.murray, tim.golden
Date 2012-11-05.09:32:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352107924.54.0.847453174526.issue16353@psf.upfronthosting.co.za>
In-reply-to
Content
Christian,
Is there ``os.confstr`` supported by MaxOS X?
Is there using of environ['PATH'] makes sense as good callback if former is not present?

About COMSPEC. From my point of view it's useful if we need default path.
Or if we have Win9x, where shell is command.com (not supported by 3.4)

I guess to hardcode ``cmd.exe`` for Windows for the same reason as we hardcode ``sh`` for Unix systems.

I agree to moving code to ``os`` if we no need to use ``shutil.which``.
The function name is still the question: getdefaultshell, getshell, get_shell etc.

Adding shutil.getdefaultshell function is interesting suggestion. It function intended to return user shell (from SHELL env var or COMSPEC for Windows) and not used in subprocess if shell=True (but can be passed as executable param if need).
History
Date User Action Args
2012-11-05 09:32:04asvetlovsetrecipients: + asvetlov, gregory.p.smith, pitrou, christian.heimes, tim.golden, ezio.melotti, eric.araujo, r.david.murray, chris.jerdonek, neologix, lyapun
2012-11-05 09:32:04asvetlovsetmessageid: <1352107924.54.0.847453174526.issue16353@psf.upfronthosting.co.za>
2012-11-05 09:32:04asvetlovlinkissue16353 messages
2012-11-05 09:32:03asvetlovcreate