HardwareRandom should be renamed OSRandom

[trevp]

BPO	1027105
Nosy	@rhettinger

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2004-09-13.22:23:26.000>
created_at = <Date 2004-09-13.08:50:24.000>
labels = ['extension-modules']
title = 'HardwareRandom should be renamed OSRandom'
updated_at = <Date 2004-09-13.22:23:26.000>
user = 'https://bugs.python.org/trevp'

bugs.python.org fields:

activity = <Date 2004-09-13.22:23:26.000>
actor = 'rhettinger'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2004-09-13.08:50:24.000>
creator = 'trevp'
dependencies = []
files = []
hgrepos = []
issue_num = 1027105
keywords = []
message_count = 2.0
messages = ['22435', '22436']
nosy_count = 2.0
nosy_names = ['rhettinger', 'trevp']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1027105'
versions = ['Python 2.4']

[trevp]

The new random.HardwareRandom class is probably better
called "OSRandom" . Calling it HardwareRandom might
lead people to think it's using special
randomness-generating hardware (which exists on some
chips, for example). But in actuality it might be
getting randomness from thread racing, OS data
structures, network statistics, time-of-day, etc...

[rhettinger]

Logged In: YES
user_id=80475

Renamed to SystemRandom.