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 pitrou
Recipients Michael.Felt, Roman.Evstifeev, WanderingLogic, akira, asvetlov, cheryl.sabella, chris.jerdonek, christian.heimes, eric.araujo, eryksun, ezio.melotti, gregory.p.smith, lyapun, ncoghlan, ned.deily, neologix, pitrou, r.david.murray, serhiy.storchaka, xdegaye, yan12125
Date 2019-02-09.19:41:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549741285.87.0.371944916891.issue16353@roundup.psfhosted.org>
In-reply-to
Content
I think the functionality of getting either the system-wide default shell or the current user's default shell can be useful regardless of whether the specific subprocess issue was fixed.
History
Date User Action Args
2019-02-09 19:41:27pitrousetrecipients: + pitrou, gregory.p.smith, ncoghlan, christian.heimes, ned.deily, ezio.melotti, eric.araujo, r.david.murray, asvetlov, chris.jerdonek, neologix, akira, xdegaye, Roman.Evstifeev, serhiy.storchaka, eryksun, lyapun, WanderingLogic, Michael.Felt, yan12125, cheryl.sabella
2019-02-09 19:41:25pitrousetmessageid: <1549741285.87.0.371944916891.issue16353@roundup.psfhosted.org>
2019-02-09 19:41:25pitroulinkissue16353 messages
2019-02-09 19:41:25pitroucreate