| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the seed sequence interface more public facing by:
1. Adding `BitGenerator.seed_seq` to give clear access to `_seed_seq`
2. Add `spawn()` to both the generator and the bit generator as
convenience methods for spawning new instances.
I somewhat remember that we always meant to consider making this
more public and adding such convenient methods, but did not do
so originally.
So, now, I do wonder whether it is time to make this fully public?
It would be nice to follow up at some point with a bit of best practices.
This also doesn't add it to the `RandomState`, although doing it via
`RandomState._bit_generator` is of course valid.
Can we define as this kind of access as stable enough that downstream
libraries could use it? I fear that backcompat with `RandomState`
might make adopting newer things like spawning hard for libraries?
|
|
|
|
| |
i.e. `numpy.typing` and `numpy._typing`
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add tests for lower level components
Correct errors found in testing
Improve specificity of tests
Other small fixes to docs and typing
|
|
|
|
| |
Correct specific typing and general typing
|
|
|
|
| |
Update with latest suggestions
|
|
|
|
| |
Update using TypedDict for state
|
| |
|
|
|
|
|
| |
Add typing for remaining core bit generators
Clean up remaining files
|
|
|
|
| |
Add initial typing for select bit generators
|
|
|
|
|
| |
Fix initial bugs
Add _Interface named tuple
|
|
Add typing to the lowest-level building blocks on random
|