summaryrefslogtreecommitdiff
path: root/numpy
Commit message (Collapse)AuthorAgeFilesLines
* Fix ndindex issueJay Bourque2013-01-091-5/+0
| | | | | Call to ndindex() with no arguments results in a ValueError exception, whereas before commit ca27396b, a call with no arguments was allowed. Issue is due to unneeded check for shape tuple size.
* Merge pull request #2838 from charris/test-numpy-constantsCharles Harris2013-01-061-0/+13
|\ | | | | TST: Add tests for constants.
| * TST: Add tests for constants.Charles Harris2012-12-161-0/+13
| | | | | | | | | | Test the values of np.pi, np.e, and np.euler_gamma to make sure they are correct to relative tolerance 1e-15.
* | Merge pull request #2882 from seberg/issue2503seberg2013-01-065-19/+77
|\ \ | | | | | | BUG: Fix CheckStrides and strides setter checks for available memory
| * | MAINT: Minor cleanupSebastian Berg2013-01-063-7/+6
| | | | | | | | | | | | Adding const and removing old comment.
| * | MAINT: Move offset calculations into special functionSebastian Berg2013-01-035-42/+61
| | | | | | | | | | | | | | | Also adds a test to check offset calculation is correct when setting strides for a base array with negative strides.
| * | BUG: Fix CheckStrides and strides setter checks for available memorySebastian Berg2013-01-033-15/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes the logic of PyArray_CheckStrides to really check the full extent the new array will have. It also changes the stride setting to calculate the full real extent of the underlying array without assuming (usually correctly) that the strides of the base array are regular. Add some tests for cases that previously failed. This "closes Issue gh-2503"
* | | Merge pull request #2888 from charris/fix-headersnjsmith2013-01-056-54/+27
|\ \ \ | | | | | | | | Fix headers
| * | | MAINT: Remove newly defined non-prefixed macros from noprefix.h.Charles Harris2013-01-051-15/+0
| | | | | | | | | | | | | | | | There was a chance that they could conflict with user defined macros.
| * | | BUG: Fixup use of undefined macros and remove redundant code.Charles Harris2013-01-051-18/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The npy_config.h file used SIZEOF_DOUBLE and SIZEOF_LONG_DOUBLE, neither of which was defined in the included config.h file. That was fixed by including numpyconfig.h. Doing so made the code dealing with Apple type sizes redundant as it is already present in numpyconfig.h, so it was removed.
| * | | MAINT: Remove tabs from numpyconfig.h.Charles Harris2013-01-051-9/+9
| | | |
| * | | MAINT: Gather NPY_SIZEOF* macros into one spot.Charles Harris2013-01-051-6/+9
| | | |
| * | | MAINT: Add some macros to noprefix.hCharles Harris2013-01-051-7/+22
| | | | | | | | | | | | | | | | | | | | | | | | Some of these are probably new unprefixed macros, but adding them makes for a bit more safety. The unprefixed macros will be deprecated at some point, so this probably has no side effects.
| * | | MAINT: Remove unneeded include from ndarraytypes.h.Charles Harris2013-01-051-3/+0
| | | |
| * | | MAINT: Remove unneeded comment form arrayobject.hCharles Harris2013-01-051-11/+0
| | | |
* | | | BUG: Replace unprefixed SIZEOF_* macros with prefixed versions.Charles Harris2013-01-059-26/+25
|/ / / | | | | | | | | | | | | | | | The sources don't define NPY_NO_PREFIX and consequently none of the unprefixed macros are defined. Using them can lead to some unexpected results.
* | | Merge pull request #2886 from seberg/complex256-byteswapCharles Harris2013-01-052-25/+28
|\ \ \ | | | | | | | | BUG: Fix byteswapping for complex scalars
| * | | BUG: Fix byteswapping for complex scalarsSebastian Berg2013-01-052-25/+28
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | During a cleanup, the fast paths were invalidated because SIZEOF_LONGDOUBLE was not defined anymore and needs to be replaced with NPY_SIZEOF_LONGDOUBLE. The other SIZEOF macros still existed however so only complex long double broke because it switched to the already broken fast path. This commit fixes the fast path, and replaces all SIZEOF_ macros within arraytypes.c.src with their corresponding NPY_SIZEOF_ macros.
* | | Fixed choice docstring, wrong default sizeJuan Luis Cano Rodríguez2013-01-041-1/+1
| | | | | | | | | Commit acf7421128b9d974d5153759650b7aaee3c2efec introduced a change in the handling of the `size` argument but the docstring wasn't updated accordingly. This commit fixes the issue.
* | | MAINT: remove painful to look at exec statement from np.errstate test.Ralf Gommers2013-01-021-28/+16
| | |
* | | TST: skip floating point warning test failures on ARM. Closes gh-413.Ralf Gommers2013-01-024-49/+54
|/ /
* | DOC: Add missing minus signOndřej Čertík2012-12-311-1/+1
| | | | | | | | | | The int64 data type allows numbers from -9223372036854775808 to 9223372036854775807. The minus sign was missing.
* | fix array interface documentation linksSandro Tosi2012-12-301-1/+1
| |
* | FIX: remove a spurious check in get_cast_transfer_functionNathaniel J. Smith2012-12-282-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At least, I hope it's spurious. Certainly it's creating a spurious error message, is unexpected by callers (one of whom specifically makes the *opposite* check before calling get_cast_transfer_function), and even if it is a useful check for some reason I can't see, it certainly doesn't belong in this function (which is otherwise just taking care of byte-swapping and alignment issues and doesn't know anything about dtypes). And worst case, we'll have turned an exception into a crash; even if I'm wrong, this shouldn't cause any code to go from working to not working, just from broken to slightly-more-broken. Test and original diagnosis by @cgohlke. Fixes gh-2798.
* | DOC: Add a blank line to multiline commentsOndřej Čertík2012-12-271-3/+6
| | | | | | | | Multiline comments should begin with a blank line. This patch fixes it.
* | DOC: Thoroughly document datetime issuesOndřej Čertík2012-12-271-11/+58
| | | | | | | | | | | | | | After understanding the issues with datetime (see gh-568), I have documented my understanding as comments in the code, so that the next time there are problems with datetime on some platform, one can quickly figure out what is going on from the code + comments.
* | FIX: Use the NPY_TIME_T macro everywhereOndřej Čertík2012-12-261-2/+2
| | | | | | | | | | | | | | | | | | | | Previously, two (critical) parts of the code used `time_t` instead of `NPY_TIME_T`. Due to the fact, that most of the time `NPY_TIME_T` was equal to `time_t`, this bug didn't show up. But in mingw, `NPY_TIME_T` is actually equal to `__time64_t` and then this causes 64 bit integers to be cast into 32 bit integers (thus becoming negative), which causes localtime() to fail in mingw. Fixes gh-568.
* | Add fix to unit test; remove debug loggingJay Bourque2012-12-262-11/+5
| | | | | | | | Add check to see if 12 bytes is a valid size for a long double
* | Add debug logging to figure out why unit test fails on TravisJay Bourque2012-12-261-0/+10
| |
* | Refactor unit tests and add DECREFJay Bourque2012-12-262-7/+11
| | | | | | | | | | - Refactor unit tests for invalid dtypes so that each test is on a separate line. This will make it easier to figure out which typestring is failing the unit test. - Add Py_DECREF for temp variable
* | Modify unit tests for 32 bit supportJay Bourque2012-12-261-2/+17
| |
* | Refactor to cover more cases; modify unit testsJay Bourque2012-12-263-30/+38
| |
* | Fix invalid typestring sizeJay Bourque2012-12-261-0/+22
| | | | | | | | Revert to pre numpy 1.7 behavior where invalid typestring size was ignored and isplay deprecate warning. This warning should eventually be changed to an error in future numpy versions.
* | Merge pull request #2800 from seberg/issue2755njsmith2012-12-212-2/+20
|\ \ | | | | | | BUG: Fix regression for in1d with non-array input
| * | TST: Add test for in1d ravellingSebastian Berg2012-12-161-0/+13
| | | | | | | | | | | | | | | | | | The behavior of in1d is not really defined here, but it should be at least consistent over different execution branches. This is what it has been for most usages.
| * | BUG: Fix regression for in1d with non-array inputSebastian Berg2012-12-082-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | There was a regression introduced by the speed improvement in commit 6441c2a. This fixes it, and generally ravels the arrays for np.in1d. However it can be argued that at least the first array should not be ravelled in the future. Fixes "Issue gh-2755"
* | | Merge pull request #2710 from jsalvatier/mapapi3njsmith2012-12-193-13/+29
|\ \ \ | | | | | | | | MapIter API 1d iteration fix and tests
| * \ \ goto fail betterJohn Salvatier2012-12-021-1/+1
| |\ \ \
| | * | | wrong error checkJohn Salvatier2012-11-192-5/+5
| | | | |
| | * | | gave PyArray_MapIterBind an error code on exitJohn Salvatier2012-11-191-9/+12
| | | | |
| | * | | tabs -> spacesJohn Salvatier2012-11-091-5/+5
| | | | |
| | * | | added a fix for 1d iteration which was failing and a test to test that caseJohn Salvatier2012-11-062-0/+12
| | | | |
| * | | | removed fancy check and added more informative messageJohn Salvatier2012-12-011-7/+8
| | | | |
| * | | | wrong error checkJohn Salvatier2012-12-012-5/+5
| | | | |
| * | | | gave PyArray_MapIterBind an error code on exitJohn Salvatier2012-12-011-9/+12
| | | | |
| * | | | tabs -> spacesJohn Salvatier2012-12-011-5/+5
| | | | |
| * | | | added a fix for 1d iteration which was failing and a test to test that caseJohn Salvatier2012-12-012-0/+12
| | | | |
* | | | | Merge pull request #2836 from cgohlke/patch-2Ralf Gommers2012-12-171-1/+13
|\ \ \ \ \ | | | | | | | | | | | | Fix unicode tests for flexible string representation on Python 3.3
| * | | | | Fix unicode tests for flexible string representation on Python 3.3cgohlke2012-12-161-1/+13
| | |_|_|/ | |/| | |
* | | | | Merge pull request #2818 from juliantaylor/spellingCharles Harris2012-12-171-1/+1
|\ \ \ \ \ | | | | | | | | | | | | fix a spelling error
View Lorry Controller Status