[issue10025] random.seed not initialized as advertised

Raymond Hettinger added the comment: Removed the inaccurate description. See r86053. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue10025] random.seed not initialized as advertised

Raymond Hettinger added the comment: Perhaps replace equivalent with "based on" or some such. This is a very minor nit and likely of interest to no one except the OP. -- priority: normal -> low ___ Python tracker

[issue10025] random.seed not initialized as advertised

Terry J. Reedy added the comment: 3.1 has the same problem (and the same results as above) Assuming behavior is not changed, please suggest a specific rewording that you would be happy with and that is not too verbose. -- components: +Documentation nosy: +terry.reedy stage: -> needs

[issue10025] random.seed not initialized as advertised

Changes by Raymond Hettinger : -- assignee: -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue10025] random.seed not initialized as advertised

Changes by R. David Murray : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10025] random.seed not initialized as advertised

New submission from Tom Goddard : In Python 2.7, random.seed() with a string argument is documented as being equivalent to random.seed() with argument equal to the hash of the string argument. This is not the actual behavior. Reading the _random C code reveals it in fact casts the signed has