Scott David Daniels wrote:
I find I have a need in randomized testing for a shorter version
of getstate, even if it _is_ slower to restore. When running
exhaustive tests, a failure report should show the start state
of the generator. Unfortunately, our current state includes a
625-element array
On Sat, Aug 15, 2009 at 8:54 PM, Scott David
Daniels wrote:
> [...] input to .setstate: old, new-short, and new-long. In trying to
> get this to work, I found what might be a bug:
> code says
> mt[0] = 0x8000UL; /* MSB is 1; assuring non-zero initial array */
> but probably should be:
> mt[0
[Scott David Daniels]
I find I have a need in randomized testing for a shorter version
of getstate, even if it _is_ slower to restore. When running
exhaustive tests, a failure report should show the start state
of the generator. Unfortunately, our current state includes a
625-element array. I
Please do not cross-post to python-dev. This discussion has been taken
to the distutils SIG.
On Fri, Aug 14, 2009 at 17:59, David Lyon wrote:
>
> Hi Tarek,
>
> What is needed is to remove/refactor the hardcoding of paths that
> currently exists within distutils and replace it with the ability to
>
I find I have a need in randomized testing for a shorter version
of getstate, even if it _is_ slower to restore. When running
exhaustive tests, a failure report should show the start state
of the generator. Unfortunately, our current state includes a
625-element array. I want a state that can b
Hello,
Jacob Rus gmail.com> writes:
>
> Okay, I made another patch,
>
> http://bugs.python.org/issue6626
>
> That adds some deprecation warnings to many of the functions/methods
> in the module.
After a fair amount of discussion on Rietveld, I think you should post another
patch without the d
