summaryrefslogtreecommitdiff
path: root/numpy
Commit message (Collapse)AuthorAgeFilesLines
...
* | | 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
| * | | | | fix a spelling errorJulian Taylor2012-12-141-1/+1
| | | | | |
* | | | | | Merge pull request #2833 from charris/fix-deprecation-testsCharles Harris2012-12-161-110/+133
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | MAINT: Refactor test_deprecations.py
| * | | | | MAINT: test_deprecations.py cleanups.Charles Harris2012-12-161-34/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removed unneeded imports, corrected spelling, and put C function references in double back-ticks.
| * | | | | MAINT: Refactor test_deprecations.pyCharles Harris2012-12-151-89/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove an unwanted print statement and make the verbose test output more readable.
* | | | | | Merge pull request #2779 from charris/add-eulerCharles Harris2012-12-161-1/+3
|\ \ \ \ \ \ | | | | | | | | | | | | | | Expose the Euler-Mascheroni constant
| * | | | | | MAINT: Use NPY_E to expose 'e'.Charles Harris2012-12-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously 'e' was defined as exp(1.)
| * | | | | | ENH: Expose Euler-Mascheroni constant.Charles Harris2012-12-021-0/+2
| | |_|/ / / | |/| | | | | | | | | | | | | | | | This closes issue gh-2753.
* | | | | | FIX: Fixes the segfault in PyArray_FromScalarOndřej Čertík2012-12-151-4/+8
| |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The problem was that PyArray_NewFromDescr() steals a reference to typecode and so any further usage of it is undefined. Apparently this bug only appeared in debug version of Python 3.2. The fix is to simply INCREF typecode and then carefully DECREF it at each possible exit from the function. Fixes gh-2738.
* | | | | Merge pull request #2823 from seberg/random-choice-statenjsmith2012-12-153-1260/+1076
|\ \ \ \ \ | | | | | | | | | | | | BUG: internal call fix in random.choice
| * | | | | BUG: internal call fix in random.choiceSebastian Berg2012-12-153-1260/+1076
| | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | An random.random call from within mtrand was done by a call to np.random.random instead of inside the class. This can possibly lead to non-deterministic results after seeding.
* | | | | Merge pull request #2812 from dwf/deprecate_scalar_floatCharles Harris2012-12-144-39/+297
|\ \ \ \ \ | |/ / / / |/| | | | Deprecate non-integer scalar indices and slice parameters
| * | | | DOC: Comments about deprecation timeframe.David Warde-Farley2012-12-141-0/+16
| | | | |
| * | | | DOC: Deprecation info for float-slicing.David Warde-Farley2012-12-141-7/+22
| | | | |
| * | | | ENH: DeprecationWarning for non-int slice indices.David Warde-Farley2012-12-141-2/+35
| | | | |
| * | | | TST: Add tests for non-int slice deprecation.David Warde-Farley2012-12-141-3/+68
| | | | |
| * | | | TST: disable DeprecationWarning tests in 2.4David Warde-Farley2012-12-141-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | These DeprecationWarnings use a Python 2.5+ feature (PyIndex_Check) and don't fire for 2.4 (support for which will be dropped shortly anyway).
View Lorry Controller Status