On 13 September 2017 at 09:46, Eric Snow <ericsnowcurrently@gmail.com> wrote:
The sys module is a rather special case as far as modules go. It is effectively a "console" into the interpreter's internal state and that includes some mutable state. Since it is a module, we don't have much of an opportunity to:
* validate values assigned to its attributes [1] * issue DeprecationWarning for deprecated attrs [2] * alias attrs [2] * replace get (and get/set) functions with properties * re-organize sys [3]
+1 from me, specifically because there are edge cases we don't generally test (e.g. folks rebinding sys.modules to nonsense), and it would be nice to be able to upgrade those from "don't do that" to "the obvious way of doing that just plain isn't allowed". Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia