[issue33910] update random.Random 's parameter to have a proper name.

Matthias Bussonnier added the comment: Thanks @rhettinger, this is a perfectly valid position, and one of the respons I was expecting. > That said, it doesn't seem to have ever caused a problem in practice (this > API has been around for a very long time) I have myself not found a lot of

[issue33910] update random.Random 's parameter to have a proper name.

Raymond Hettinger added the comment: Thanks for the suggestion. You are right about *x*, *n*, or *a* being the best possible parameter name. That said, it doesn't seem to have ever caused a problem in practice (this API has been around for a very long time), so I'm reluctant to create

[issue33910] update random.Random 's parameter to have a proper name.

Change by Serhiy Storchaka : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue33910] update random.Random 's parameter to have a proper name.

Change by Matthias Bussonnier : -- keywords: +patch pull_requests: +7427 stage: -> patch review ___ Python tracker ___ ___

[issue33910] update random.Random 's parameter to have a proper name.

New submission from Matthias Bussonnier : Docs of random.Random always refer to it with Random([seed]) (`lib/random.py`), tough the parameter is actually named `x` making it : - non obvious what it does. - hard to search for. - hard to remember when using kwargs. Obviously changing the