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-or
Recipients josh.r, paul.moore, r-or, roufique7, steve.dower, tim.golden, zach.ware
Date 2019-02-01.06:00:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549000832.85.0.347675801664.issue35862@roundup.psfhosted.org>
In-reply-to
Content
Because sometimes when a process is implicitly started by some 3rd party library (i.e. COM via pythonwin here) the "old", unchanged environment is retained as the process itself doesn't care if os.environ was changed or not, the original environment cannot be modified.

This solution would give a lot of flexibility in that regard.

I think pythonwin is actually a special case as the problem here lies somewhere in the dispatch(.) call. The process creation should be handled somewhere within the COM interface, pywin does nothing there. 

But this solution effectively circumvents that issue.
History
Date User Action Args
2019-02-01 06:00:33r-orsetrecipients: + r-or, paul.moore, tim.golden, zach.ware, steve.dower, josh.r, roufique7
2019-02-01 06:00:32r-orsetmessageid: <1549000832.85.0.347675801664.issue35862@roundup.psfhosted.org>
2019-02-01 06:00:32r-orlinkissue35862 messages
2019-02-01 06:00:32r-orcreate