Author njs
Recipients Dima.Tisnek, christian.heimes, jmfrank63, jonozzz, njs, yan12125
Date 2018-12-20.08:13:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545293614.07.0.788709270274.issue34271@psf.upfronthosting.co.za>
In-reply-to
Content
It's confusing, but AFAICT what happened is that Mozilla started to disable it in release builds, but got a bunch of pushback from users and changed their minds and decided to keep it enabled. But then there was a snafu tracking the patch for that, so there ended up being a few releases where it was disabled, before everything got sorted out. But, it is enabled by default now. The very confusing thread is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1188657

And I don't see how this is any riskier than other envvars like PYTHONSTARTUP, which lets you name an arbitrary file that the interpreter will execute at startup.
History
Date User Action Args
2018-12-20 08:13:34njssetrecipients: + njs, christian.heimes, jonozzz, Dima.Tisnek, yan12125, jmfrank63
2018-12-20 08:13:34njssetmessageid: <1545293614.07.0.788709270274.issue34271@psf.upfronthosting.co.za>
2018-12-20 08:13:34njslinkissue34271 messages
2018-12-20 08:13:33njscreate