summaryrefslogtreecommitdiff
path: root/numpy/random
AgeCommit message (Collapse)AuthorFilesLines
2017-05-09BUG: Buttress handling of extreme values in randintgfyoung3-15/+60
2017-04-26Merge pull request #8962 from MSeifert04/random_choice_docsEric Wieser1-2/+2
DOC: Wrong return type of np.random.choice and wrong variable name in parameter description.
2017-04-26[DOC] use of * instead of ` to refer to a function parameter.Matthias Bussonnier1-2/+2
It's funny because it's fine in EXAMPLE_DOCSTRING.rst.txt that uses the same example.
2017-04-20DOC: Wrong return type of np.random.choice and wrong variable nameMichael Seifert1-2/+2
in parameter description. [ci skip]
2017-04-10MAINT: avoid memcpy when i == jYu Feng1-0/+1
Valgrind complains about memcpy with overlapping address in mtrand.c It happens when i == j in this loop. Closer inspection the i == j iteration is not needed (it is a swap). So, skip it and avoid depending on undefined behavior of memcpy. related read: https://sourceware.org/bugzilla/show_bug.cgi?id=12518
2017-04-02BUG: Check for errors when PyInt_AsLong is called in np.randomSimon Gibbons2-9/+16
After #8883 was merged it was noticed that the same problem was occuring with calls to PyInt_AsLong. Namely that PyErr_Occoured wasn't being checked if it returned -1 indicating an exception could have been thrown. This PR adds those checks as well as a regression test.
2017-04-01Fix testSimon Gibbons1-1/+1
2017-04-01BUG: Ensure Errors are correctly checked when PyFloat_AsDouble is called.Simon Gibbons2-1/+15
There was an error in np.random.uniform where if np.random.uniform were called with a type that throwed exceptions when it was converted to a float this exception wouldn't be raised. This bug was due to an issue where PyFloat_AsDouble was called but no check for PyErr_Occurred was performed after. This PR fixes the issue by ensuring that Cython will always emit a call to PyErr_Occurred if PyFloat_AsDouble returns -1.0 Fixes: #8865
2017-03-26DOC: update docs and comments for move of mailing list to python.orgRalf Gommers1-1/+1
2017-03-25MAINT: Remove asbytes where a b prefix would sufficeEric Wieser1-2/+1
Since we only need to support python 2, we can remove any case where we just pass a single string literal and use the b prefix instead. What we can't do is transform asbytes("tests %d" % num), because %-formatting fails on bytes in python 3.x < 3.5.
2017-03-13Revert gh-8570.Charles Harris2-42/+1
BUG: fix issue #8250 where np.random.permutation fail. This reverts commit 7a73bad2d9c04e4f16e87dbed9d7b627327fe814. Closes #8776.
2017-03-12Merge pull request #8570 from evanlimanto/random-permutation-shuffle-fixEric Wieser2-1/+42
BUG: fix issue #8250 when np.array gets called on an invalid sequence
2017-03-10BUG: fix issue #8250 where np.random.permutation fails when np.array gets ↵Evan Limanto2-1/+42
called on an invalid sequence.
2017-02-28BUG: Fix assert statements in random.choice testsMarein Könings1-5/+5
Unless I am very much mistaken these 'assert_(x,y)' calls should really be 'assert_equal(x,y)'.
2017-01-17TST: work around isfinite inconsistency on i386Julian Taylor1-1/+3
inlined isfinite on i386 does not work for DBL_MAX / 1e17 + DBL_MAX as with extended precision this is not smaller equal than DBL_MAX.
2017-01-06TST: remove a duplicate test. Closes gh-8447.Ralf Gommers1-4/+0
2017-01-03single too argument + mention in release docs.Oscar Villellas1-9/+5
2017-01-03Documentation fix and proper handling of toleranceOscar Villellas1-10/+15
2017-01-03fixed merged testOscar Villellas1-14/+8
2017-01-03Merge remote-tracking branch 'numpy-org/master' into mult-normOscar Villellas14-840/+2145
2016-12-13DOC: Fixed minor typoMikhail Pak1-1/+1
2016-11-02BUG: Better check for invalid bounds in np.random.uniform.Alistair Muldal2-0/+6
Also check for invalid bounds when low= and high= are arraylike rather than scalar (closes #8226)
2016-10-28DOC: Clean up lomax and genpareto references.wrwrwr1-3/+3
2016-10-28MAINT, DOC: Update some scipy.stats references.wrwrwr1-27/+27
Closes #5813.
2016-10-22Merge pull request #8173 from aixtools/issue8118Charles Harris1-3/+6
BLD: Enable build on AIX
2016-10-22STY: Fix indentation to follow PEP8Charles Harris1-2/+2
2016-10-21commit BLD: AIX uses the flag _LARGE_FILES to ensure proper prototype ↵Michael Felt1-1/+4
declarations The problem this fix resolves is to ensure that 32-bit and 64-bit functions (e.g., fclear() and fclear64()) to access/manipulate "large files" are defined properly - much as GNU and other platforms use one or more of the defines _FILE_OFFSET_BITS, _LARGEFILE_SOURCE, and _LARGEFILE64_SOURCE. Without this fix the numpy code only defines flags that are not recognized in the AIX environment and have no effect in anyway. The fix applies the AIX convention and does not "export" any of the flags currently exported. For all other platforms the current flags: _FILE_OFFSET_BITS, _LARGEFILE_SOURCE, and _LARGEFILE64_SOURCE are "exported". This fix should not have any impact or side-effect based on the version of python used. History: Starting around 1997 AIX started supporting so-called "large files", i.e., length > signed 32-bit. In the period 1997-1998 the flag _LARGE_FILES was established to simplify porting 32-bit applications to 64-bit. The convention is to define _LARGE_FILES before including any "system include files" either as an argument to ${CC} (e.g., in ${CFLAGS} or as the first #define in every source file. This is to ensure that that no relevant function calls would be redefined later in the build process.
2016-10-20DOC: 'highest' is exclusive for randint()Ben North1-2/+2
2016-09-23MAINT: Remove duplicate randint helpers code.gfyoung1-277/+0
Continuation of gh-8071 by removing the duplicate randint Cython code that is not generated via Tempita.
2016-09-20MAINT: Add Tempita to randint helpersgfyoung2-0/+78
Refactors the randint helpers to use a Tempita template. This will reduce technical debt in the long run.
2016-09-07DOC: change version references from x.y to x.y.zPierre de Buyl1-1/+1
2016-09-06DOC: change Numpy to NumPy in dosctrings and commentsPierre de Buyl1-1/+1
The strings in error messages were left untouched
2016-09-02TST: Use new warnings context manager in all testsSebastian Berg1-11/+15
In some places, just remove aparently unnecessary filters. After this, all cases of ignore filters should be removed from the tests, making testing (even multiple runs) normally fully predictable.
2016-06-22Merge pull request #5822 from anntzer/0-scale-distributionsNathaniel J. Smith2-60/+88
Allow many distributions to have a scale of 0.
2016-06-13DOC: add reference to poisson rngJulian Taylor1-0/+5
[ci skip]
2016-06-10BUG: Fix segfaults in np.random.shuffleSimon Gibbons2-1/+34
np.random.shuffle will allocate a buffer based on the size of the first element of an array of strings. If the first element is smaller than another in the array this buffer will overflow, causing a segfault when garbage is collected. Additionally if the array contains objects then one would be left in the buffer and have it's refcount erroniously decrimented on function exit, causing that object to be deallocated too early. To fix this we change the buffer to be an array of int8 of the the size of the array's dtype, which sidesteps both issues. Fixes #7710
2016-06-09Don't allow -0. as distribution shape parameter.Antony Lee2-24/+34
At least the gamma generator doesn't support it.
2016-05-05DOC: fix incorrect Gamma distribution parameterization commentsstevenjkern1-2/+2
2016-04-10MAINT: Ignore DeprecationWarning for random_integers in tests.Charles Harris1-9/+13
The warning turned up when the numpy/randome/tests were run using $ python runtests.py -t numpy/random/tests/ It doesn't show when all the tests are run.
2016-04-10MAINT: Always use PyCapsule instead of PyCObject in mtrand.pyx.Charles Harris4-98/+11
Python 2.7 has a backport of PyCapsule so we no longer need to support PyCObject. This PR makes that change and removes the no longer needed mt_compat.h file.
2016-04-06Allow many distributions to have a scale of 0.Antony Lee2-60/+78
(in which case a stream of 0's is usually returned (or 1's)). See #5818.
2016-02-27DOC: Clarify the valid range of integers passed to random.seed.Charles Harris1-6/+6
2016-02-27DOC: Update random.seed in mtrand.pyx.Oren Amsalem1-1/+1
I know int is between 0 and 4294967295, but I think many people that do not know that will benefit from this comment. [ci skip]
2016-02-23Merge pull request #7279 from madphysicist/percentile-testsJulian Taylor1-2/+5
TST: Fixed elements being shuffled
2016-02-22TST: Fixed shuffle axis in tests.Joseph Fox-Rabinovitz1-2/+5
Since shuffle only works along the first dimension, it must be done before reshape to get reasonable looking data. Did not affect the current tests. I noticed while working on some scipy code. Also, made a couple of doc changes to np.random.shuffle.
2016-02-22BUG: Remove data race in mtrand: two threads could mutate the state.Devin Jeanpierre1-9/+27
E.g.: np.random.random_sample() uses the GIL for synchronization np.random.random_sample(1) releases the GIL and uses a separate lock. This means that both can run simultaneously, causing a data race when mutating the random number generator's state, which could lead to buffer overflow (from incrementing state->pos). The fix here is to always use the separate lock, so that exactly one thread at a time is mutating the random number generator's state.
2016-02-19BUG: Make randint backwards compatible with pandasgfyoung2-9/+24
The 'pandas' library expects Python integers to be returned, so this commit changes the API so that the default is 'np.int' which converts to native Python integer types when a singleton is being generated with this function. Closes gh-7284.
2016-02-16BUG: Enforce dtype for randint singletonsgfyoung2-9/+18
Closes gh-7203.
2016-02-13DOC: fix a number of reST formatting issues in docstrings.Ralf Gommers1-3/+5
2016-02-02Update Wikipedia references for mtrand.pyxArne de Laat1-12/+12
Specifically the 'Logarithmic distribution' link is fixed. For others the links or article names are updated.