Raymond Hettinger <raymond.hettin...@gmail.com> added the comment: -0 on making anything other than the doc change. For the most part, we avoid sweeping through the standard library to substitute-in new features and instead have a preference for code stability rather than code churn.
FWIW, the main rationale for introducing choices() was to support weighting. Existing code that calls choice() multiple times is still correct and clear. ---------- nosy: +rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33228> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
