warner/pycryptopp — comment on commit 0c79f21f3157aabfa8a3f376181441e24a34114f
File: README.ed25519 line 92
By warner:

(edited the previous comment to keep github from thinking that "ed25519" was a git revision id. That's kind of hilarious, actually).

I hear you. I didn't document it, but `create_keypair()` actually takes an `entropy=` argument which defaults to `os.urandom`. And you can create a `SigningKey` with any 32-byte string of your choice. So it's easy to use it in the way you describe.

I'm on the fence about whether to **require** people to use it that way. The original C code sought to prevent people from hurting themselves by hard-coding a read from `/dev/urandom`, and not allowing determinstic key generation at all. I had to change that to let it work on windows (where it still uses os.urandom), and to allow determinstic testing. I could imagine requiring a fixed-length seed as you suggest, although that would take it even further away from the original author's design.