BUG: Concatenate with empty sequences, fixes #1586 #6224
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
80aaa59 to
7d1f87a
Compare
|
I'd suggest ignoring empty tuples and arrays. The only information that they carry is dimensionality, which we might want to check, but otherwise they should have no effect. |
may return something else than one or zero and npy_bool is unfortunately an int8 not a c99 bool
…to a common type.
…into a common type.
…Object_Repr`. Also, do a better job of handling any errors raised while constructing the error message.
…nspose and calls `PyArray_MatrixProduct2`.
This add benchmarks randint. There is one set of benchmarks for the default dtype, 'l', that can be tracked back, and another set for the new dtypes 'bool', 'uint8', 'uint16', 'uint32', and 'uint64'.
Added functions are - cacos - cacosf - cacosl - cacosh - cacoshf - cacoshl Closes numpy#6063.
Fix issue numpy#6723. Given an exotic masked structured array, where one of the fields has a multidimensional dtype, make sure that, when accessing this field, the fill_value still makes sense. As it stands prior to this commit, the fill_value will end up being multidimensional, possibly with a shape incompatible with the mother array, which leads to broadcasting errors in methods such as .filled(). This commit uses the first element of this multidimensional fill value as the new fill value. When more than one unique value existed in fill_value, a warning is issued. Also add a test to verify that fill_value.ndim remains 0 after indexing.
empty strings are the default for the new rpath, extra_compile_args and extra_link_args sections
I have found that there are two missing numbers in a sequence in the documentation. http://docs.scipy.org/doc/numpy/user/misc.html#interfacing-to-c It goes 1,2,3,5,7,8 with missing 4 and 6.
Fixes GH6452
There are two types of datetime64/timedelta64 objects with generic times
units:
* NaT
* unit-less timedelta64 objects
Both of these should be safely castable to any more specific dtype. However,
more specific dtypes should not be safely castable to generic units.
Otherwise, the result of `np.datetime64('NaT')` or `np.timedelta(1)` is
entirely useless, because they can't be used in any arithmetic operations or
comparisons.
This is a regression from NumPy 1.9, where these sort of operations worked
because the default casting rules with ufuncs were less strict.
Now, NaT compares like NaN: - NaT != NaT -> True - NaT == NaT (and all other comparisons) -> False We discussed this on the mailing list back in October: https://mail.scipy.org/pipermail/numpy-discussion/2015-October/073968.html
Adds the 'order' parameter to the __new__ override in MaskedArray construction, enabling it to be enforced in methods like np.ma.core.array and np.ma.core.asarray. Closes numpygh-6646.
np.put and np.place do something only when the first argument is an instance of np.ndarray. These changes will cause a TypeError to be thrown in either function should that requirement not be satisfied.
…nnot be cast to a common type.
… behavior of `MaskedArray`'s masks is changing.
… of their masks when they are also returning views of their data.
...to hstack, vstack, stack, hsplit, vsplit, dsplit, dstack that check that they raise exceptions.
The identity for bitwise_xor is zero.
Current value is 1, which only works for the low order bit. Use -1 instead. Closes numpy#7060.
- test values - test identity for bitwise_or, bitwise_xor, bitwise_and
The identity has changed from 1 to -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]
Add note about wheels on pypi, and Windows wheels in particular. See discussion at: numpy#5479
Not everyone might recognize Travis status
Give hook to allow platform-specific installs to modify the initialization of numpy. Particular use-case is to allow check for SSE2 on Windows when shipping with ATLAS wheel.
Add description of ``numpy/_distribution_init.py`` file and init hook to release notes for 1.12.0.
Found this while reading a docstring.
This was otherwise undocumented, so the nanprod.rst page wasn't being generated.
DEP: Depreca 67E6 ted using a float index in linspace DEP: Deprecated using a float index in linspace DEP: Deprecated using a float index in linspace DEP: Deprecated using a float index in linspace DEP: Deprecated using a float index in linspace DEP: Release notes for PR#7328
Completely rewrote binary_repr method to use the Python's built-in 'bin' function to generate binary representations quickly. Fixed the behaviour for negative numbers in which insufficient widths resulted in outputs of all zero's for the two's complement. Now, it will return the two's complement with width equal to the minimum number of bits needed to represent the complement. Closes numpygh-7168.
The input arrays are documented to have ndim <=2, so check for that and raise a ValueError on failure.
The non-nan elements of the result of corrcoef should satisfy the inequality abs(x) <= 1 and the non-nan elements of the diagonal should be exactly one. We can't guarantee those results due to roundoff, but clipping the real and imaginary parts to the interval [-1, 1] improves things to a small degree. Closes numpy#7392.
This doesn't actually test much, as we don't have any inputs where that was not already the case. But at least it is there and perhaps a fuzz test can be added at a later date.
Empty non-arrays no longer participate in determining the dtype of the concatenated array. Have also refactored the code to unify as much as possible the logic for flattened and non-flattened paths, unifying the error checks and adding a few more tests, both for the fixed bug and for other functionality.
6f55325 to
943e6cf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is still WIP, as I may be complicating things more than needed. And tests are still missing.
The code avoids empty sequences in
concatenatebeing converted to the defaultfloat64type, which causes a typically undesired behavior:To do so, it remembers the last dtype it got, either from an ndarray, of from a non-ndarray that was converted to a non-empty ndarray, and casts non-ndarrays that convert to empty ndarrays to that dtype. Since at the beginning there is no dtype to remember, leading non-ndarrays that convert to empty ndarrays are discarded in the first pass, and converted again in a second pass.
Because we are using the size of the resulting ndarray as the criterion for emptiness, it also works with nested empty sequences, i.e. both of these produce arguably correct results:
The second case was not contemplated in the original #1586 issue, and the code can probably be simplified a little if only strictly empty sequences trigger the cast. But it is probably a good thing that
[[]]behaves the same as[], right?Thoughts on this are very welcome in order to write some meaningful tests.