R. David Murray <rdmur...@bitdance.com> added the comment: Unless you can point to a place where the behavior that was fixed is actually documented, this is classed as an implementation detail that was changed (or, more likely, a bug that was fixed). If this were less obscure or had been in existence for longer, there might be an argument for documenting it, but I'm surprised that anyone noticed this variable, since its existence is not in keeping with how Python works in general. In fact, it goes completely against my Python intuition that it worked at all. (I suppose that someone newer to Python would be more likely to find it by accident...)
That said, it is certainly not obvious from Misc/NEWS that this variable went away, so it was presumably fixed as part of some other change. Given that we *do* have a bug report about it, we should consider if it should be documented somewhere; perhaps an addendum to the relevant Misc/NEWS entry, and then the What's New author can decide whether or not to include it. (As an aside, note that What's New is not kept up to date, it generally only gets filled in closer to the release date.) ---------- nosy: +r.david.murray _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12530> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
