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 paul.moore
Recipients Anthony Sottile, blueyed, eryksun, jaraco, lazka, miss-islington, paul.moore, steve.dower, tim.golden, zach.ware
Date 2020-05-16.10:08:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Perhaps the best approach for the sake of POSIX compatibility is to set HOME on startup to the correct value? 

If Python starts setting `HOME`, that has the potential to affect programs called in a subprocess, possibly breaking them (making them not find the user's config, for example). Even if we only set `HOME` when it's not already set, we can get this issue. (Vim, for example, will break if you set HOME to somewhere other than where the user has their config stored).

Certainly, it's arguable that such programs are not respecting Windows conventions correctly, but in practical terms that's not really that relevant. The user will just see it as "Python can't call my program correctly".

This is a very real issue, that I used to hit a lot in the past, when native Windows support was a lot less common in open source code than it is now. And it was nearly always made worse by the programs that tried to be "too clever" about hiding the differences between Windows and Unix.

So I'm a strong -1 on Python doing anything with `HOME` here.
Date User Action Args
2020-05-16 10:08:43paul.mooresetrecipients: + paul.moore, jaraco, blueyed, tim.golden, zach.ware, eryksun, steve.dower, lazka, Anthony Sottile, miss-islington
2020-05-16 10:08:43paul.mooresetmessageid: <>
2020-05-16 10:08:43paul.moorelinkissue36264 messages
2020-05-16 10:08:42paul.moorecreate