Raymond Hettinger added the comment: The bar is rather high for changing the current algorithm which is well studied, has a long period, and is reasonably fast. I do not recommend jumping straight into making a patch before we get agreement that we really want another PRNG when the current one is stable, well-studied, performant, and has been working well for its intended purpose.
Note, we guarantee that the current method will always be available, so this would be just another option. If we were to add another generator, I prefer that we add one with some completely different characteristics (such as being cryptographically strong). I don't want to take the default generator and periodically switch it out with the "flavor of the month" (people are always coming up with more PRNGs that make various trade-offs between speed, size of stored state, period, etc). ---------- assignee: -> rhettinger nosy: +rhettinger priority: normal -> low _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18386> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
