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 ncoghlan
Recipients alex, barry, bkabrda, christian.heimes, doko, dstufft, janssen, lemburg, ncoghlan, pitrou, r.david.murray, rkuska, vstinner
Date 2015-10-14.15:20:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The rationale behind "platform_default" relates to what we put in the default config file in the RPM. If enable/disable are the only options, then as soon as the first version ships with "disable" as the default, affected systems will *never* switch to being enabled by default unless the system administrator changes it.

By contrast, if we put "platform_default" in the default configuration, then inattentive sysadmins could theoretically eventually have their defaults switched to "enable" at some point.

We don't know yet if we'd ever upgrade the "platform_default" setting, but I think it's worthwhile to retain the option.
Date User Action Args
2015-10-14 15:20:20ncoghlansetrecipients: + ncoghlan, lemburg, barry, doko, janssen, pitrou, vstinner, christian.heimes, alex, r.david.murray, bkabrda, dstufft, rkuska
2015-10-14 15:20:20ncoghlansetmessageid: <>
2015-10-14 15:20:20ncoghlanlinkissue23857 messages
2015-10-14 15:20:19ncoghlancreate