summaryrefslogtreecommitdiff
path: root/numpy/lib/stride_tricks.py
Commit message (Collapse)AuthorAgeFilesLines
* ENH: allow single input argument in numpy.broadcastHolger Kohr2016-01-041-3/+0
|
* BUG: error in broadcast_arrays with as_strided arrayStephan Hoyer2015-10-241-3/+6
| | | | Fixes GH6491
* BUG: fix _broadcast_shape (and broadcast_array) for len(args) > 32Stephan Hoyer2015-05-151-0/+4
| | | | Fixes gh-5862
* DOC: note versionadded for broadcast_toEric Moore2015-05-061-0/+4
| | | | closes gh-5839
* Merge pull request #5519 from jaimefrio/array_interface_dtypeCharles Harris2015-03-121-2/+4
|\ | | | | ENH: PyArray_FromInterface checks descr if typestr is np.void
| * ENH: PyArray_FromInterface checks descr if typestr is np.voidjaimefrio2015-03-081-2/+4
| | | | | | | | | | | | | | | | | | | | When the 'typestr' member of the __array_interface__ dictionary defines a np.void dtype, check the 'descr' member, and if it is a valid dtype description and it is not the default one, use it to construct the dtype for the array to return. This fixes #5081, as as_strided no longer has to worry about changing the dtype of the return.
* | BUG: fix broadcast_to for reference typesStephan Hoyer2015-03-011-3/+3
|/
* ENH: add broadcast_to functionStephan Hoyer2015-02-261-55/+104
| | | | | | | | Per the mailing list discussion [1], I have implemented a new function `broadcast_to` that broadcasts an array to a given shape according to numpy's broadcasting rules. [1] http://mail.scipy.org/pipermail/numpy-discussion/2014-December/071796.html
* Convert as_strided input to array firstMarten van Kerkwijk2014-08-271-4/+8
|
* ENH: add subok flag to stride_tricks (and thus broadcast_arrays)Marten van Kerkwijk2014-08-251-5/+19
|
* STY: Make files in numpy/lib PEP8 compliant.Charles Harris2014-07-311-10/+12
| | | | The rules enforced are the same as those used for scipy.
* Fix stride_stricks.as_strided function for object arraysJay Bourque2014-02-261-1/+2
| | | | Currently, calling as_strided for object array results in 'TypeError: Cannot change data-type for object array.'. Fix so that dtype of new array is only set for void dtype, as originally intended.
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-1/+1
| | | | | | | Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long and will need to be broken at some point. OTOH, some lines were already too long and need to be broken at some point. Now seems as good a time as any to do this with open PRs at a minimum.
* Fix issue with broadcast_arrays() and user defined dtypesJay Bourque2013-05-101-1/+4
| | | | broadcast_arrays() does not handle struct and custom dtypes correctly. Dtype of returned broadcasted arrays is always '|V8'. Fix broadcast_arrays() so that dtype of returned arrays is correct dtype for user defined dtypes.
* 2to3: Apply `map` fixer.Charles Harris2013-04-101-2/+2
| | | | | | | | | | | | | | | | | | | In Python 3 `map` is an iterator while in Python 2 it returns a list. The simple fix applied by the fixer is to inclose all instances of map with `list(...)`. This is not needed in all cases, and even where appropriate list comprehensions may be preferred for their clarity. Consequently, this patch attempts to use list comprehensions where it makes sense. When the mapped function has two arguments there is another problem that can arise. In Python 3 map stops execution when the shortest argument list is exhausted, while in Python 2 it stops when the longest argument list is exhausted. Consequently the two argument case might need special care. However, we have been running Python3 converted versions of numpy since 1.5 without problems, so it is probably not something that affects us. Closes #3068
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Use absolute imports.Charles Harris2013-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+2
| | | | | | | | This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates.
* DOC: wiki merge, twodim_base and a few loose ones.rgommers2010-07-311-5/+5
|
* Docstring update: libPauli Virtanen2009-10-021-1/+6
|
* ran reindentJarrod Millman2008-08-081-2/+1
|
* Merge from documentation editor.Stefan van der Walt2008-08-051-2/+4
|
* ENH: Add broadcast_arrays() function to expose broadcasting to pure Python ↵Robert Kern2008-07-031-0/+109
functions that cannot be made to be ufuncs.
View Lorry Controller Status