This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chuck
Recipients chuck, georg.brandl, rhettinger, sligocki
Date 2009-10-07.09:35:15
SpamBayes Score 4.535371e-07
Marked as misclassified No
Message-id <1254908130.41.0.75684863179.issue7076@psf.upfronthosting.co.za>
In-reply-to
Content
Depends on how verbose we want to be. It should say why one might want to 
use urandom() instead of random (if you decide you are interested you can 
still look up the documentation). I think it would be nice to say why 
random does not use urandom if urandom is better, so you end up with a 
very short pro/con of urandom, which should be appropriate for users who 
are seeking information on getting random numbers.

Unfortunately I don't know enough about random. I guess it's a 
speed/security tradeoff?
History
Date User Action Args
2009-10-07 09:35:30chucksetrecipients: + chuck, georg.brandl, rhettinger, sligocki
2009-10-07 09:35:30chucksetmessageid: <1254908130.41.0.75684863179.issue7076@psf.upfronthosting.co.za>
2009-10-07 09:35:16chucklinkissue7076 messages
2009-10-07 09:35:15chuckcreate