Mailman 3 February 2019 - NumPy-Discussion

Adding count parameter to unpackbits (PR-10855)
by Sebastian Berg 22 Feb '19

22 Feb '19

Hi all, I was about to merge it, but was noot sure it was really discussed before (and it would be a long time ago). The pull requests: https://github.com/numpy/numpy/pull/10855 Proposes to add a count parameter to unpackbits: ``count`` allows subsetting the number of bits that will be unpacked up-front, rather than reshaping and subsetting later, making the ``packbits`` operation invertible, and the unpacking less wasteful. Counts larger than the number of available bits add zero padding. Negative counts trim bits off the end instead of counting from the beginning. None counts implement the existing behavior of unpacking everything. This seems like a pretty small API addition, but I thought I would ping the list again before merging in case anyone objects to it or feels it should be modified. In other words, the count parameter is much the same as indexing the result: np.unpackbits(x)[:count] although it will zero pad if count is out of bounds. Which is necessary if it is to invert a `np.packbits` when less than 8 bits are packed. If no one speaks up, I plan to merge it soon. Best, Sebastian

1 0

Re: [Numpy-discussion] [SciPy-User] Why slicing Pandas column and then subtract gives NaN?
by Avi Gross 18 Feb '19

18 Feb '19

Changing horses mid-stream is not generally a good idea. But python is easy to extend so there may be other choices out there. The reality is that what matters more than what choices a language makes is consistency across the language. If you can learn the choices and even quirks and work with them, you can get things done. I have used languages where vectors or lists are zero-based and some where they are one-based. Both work, albeit you may need to adjust an algorithm to add or subtract one from the index you use or leave the first entry empty. If you use a pandas data structure without specifying your own index, you get stuck with the default behavior. If you wanted a 1 or 0 based index, you could add that carefully and so on. In theory, you could create an alternate numpy or alternate pandas just like many of the alternate modules you can find which often have very different designs for graphics and there probably already are some out there. Integrating them with other tools may not be as simple. If you want to use the machine learning tools available, some functions demand they be given the data as a pandas DataFrame or a numpy array. Giving them something else like a python list, even if it is just an object extended from the above, may well break things. This makes it very hard to port some things to or from other languages with different design constraints as an algorithm that looks straightforward in one because it goes with the overall grain of the language may need major surgery to fit into the other and perhaps might best be rewritten using some other algorithm that fits better. A different discussion elsewhere about errors was instructive. Many programmers used to write complex code that checks for all kinds of errors or conditions. Some python programmers take an approach of expecting errors to be something you catch so why bother checking for things like an array index being non-existent. Well, if an error you expect in pandas is not caught, consider checking before using software that does not enforce it. And some "errors" are not errors. As mentioned, in R it is NOT a design error that using an NA value in a calculation silently propagates the NA. Throughout the language you must either check if there is an NA using the is.na() function or by telling routines to drop/ignore any NA as in sum(something, na.rm=TRUE). There are many design decisions you make this way. So, if your language does something you don't want when it uses an implicit index, fine. Give it an explicit index. If it does not properly check the range you provide for validity, do it yourself. And if the language is so unsuitable for your needs, you can often switch. In particular, there are now even ways you can start your code in one language like python or R and then shunt some data structures across a divide where the other language can do things another way and if needed, shunt it back and repeat. That may not work well for your application and, as noted, switching rides in midstream has its dangers. From: NumPy-Discussion <numpy-discussion-bounces+avigross=verizon.net(a)python.org> On Behalf Of Robert Kern Sent: Sunday, February 17, 2019 3:15 PM To: Discussion of Numerical Python <numpy-discussion(a)python.org> Subject: Re: [Numpy-discussion] [SciPy-User] Why slicing Pandas column and then subtract gives NaN? On Sat, Feb 16, 2019 at 8:42 PM C W <tmrsg11(a)gmail.com <mailto:tmrsg11@gmail.com> > wrote: Dan, No one here is trying to convince you to use Python. If you don't like it, don't use it. The problem is not me, it's the language. No need to take it out on me personally. I've used other languages, Python is lacking in this area. I'm being very frank here, just think about it. No one was taking it out on you personally. We're just stating that we're not interested in having a discussion about which semantics are best, much less convincing you that Python's choice is the right one. They have been that way for a long time, and the time for making those decisions is long past. We could not change them now if we wanted to. Empirically, I've been on these lists for about 20 years now, and I have not seen this pop up as a frequent issue causing bugs in real code, so I would submit that if there is a lack (or benefit) compared to other languages, it is small That said, Python is not alone here. Perl and Ruby have Python's semantics. R introduces NaNs but does not raise an error. Matlab and Julia do raise errors. -- Robert Kern

1 0

Re: [Numpy-discussion] [SciPy-User] Why slicing Pandas column and then subtract gives NaN?
by Mike C 18 Feb '19

18 Feb '19

Thanks a lot, Thomas. I don’t have index when I read in the data. I just want to slice two series to the same length, and subtract. That’s it! I also don’t what numpy methods wrapped within methods. They work, but hard do understand. How would you do it? In Matlab or R, it’s very simple, one line. ________________________________ From: SciPy-User <scipy-user-bounces+tmrsg11=gmail.com(a)python.org> on behalf of Thomas Kluyver <takowl(a)gmail.com> Sent: Thursday, February 14, 2019 4:54 PM To: SciPy Users List Cc: Discussion of Numerical Python Subject: Re: [SciPy-User] [Numpy-discussion] Why slicing Pandas column and then subtract gives NaN? Maybe it's useful to look a bit more at what pandas is doing and why. The 'index' on a series or dataframe labels each row - e.g. if your series is measuring total sales for each day, its index would be the dates. When you combine (e.g. subtract) two series, pandas automatically lines up the indices. So it will join up the numbers for February 14th, even if they're not in the same position in the data. In your example, you haven't specified an index, so pandas generates an integer index which doesn't really mean anything, and aligning on it doesn't do what you want. What are you trying to do? If Numpy does exactly what you want, then the answer might be to use Numpy. > Isn't Numpy built on top of Pandas? It's the other way round: pandas is built on Numpy. Pandas indices are an extra layer of functionality on top of what Numpy does. On Thu, 14 Feb 2019 at 20:22, C W <tmrsg11(a)gmail.com<mailto:tmrsg11@gmail.com>> wrote: Hi Paul, Thanks for your response! I did not find a Pandas list for users, only for developers. I'd love to be on there. result = a.subtract(b.shift()).dropna() This seems verbose, several layers of parenthesis follow by a dot method. I'm new to Python, I thought Python code would be pity and short. Is this what everyone will write? Thank you! On Wed, Feb 13, 2019 at 6:50 PM Paul Hobson <pmhobson(a)gmail.com<mailto:pmhobson@gmail.com>> wrote: This is more a question for the pandas list, but since i'm here i'll take a crack. * numpy aligns arrays by position. * pandas aligns by label. So what you did in pandas is roughly equivalent to the following: a = pandas.Series([85, 86, 87, 86], name='a').iloc[1:4].to_frame() b = pandas.Series([15, 72, 2, 3], name='b').iloc[0:3].to_frame() result = a.join(b,how='outer').assign(diff=lambda df: df['a'] - df['b']) print(result) a b diff 0 NaN 15.0 NaN 1 86.0 72.0 14.0 2 87.0 2.0 85.0 3 86.0 NaN NaN So what I think you want would be the following: a = pandas.Series([85, 86, 87, 86], name='a') b = pandas.Series([15, 72, 2, 3], name='b') result = a.subtract(b.shift()).dropna() print(result) 1 71.0 2 15.0 3 84.0 dtype: float64 On Wed, Feb 13, 2019 at 2:51 PM C W <tmrsg11(a)gmail.com<mailto:tmrsg11@gmail.com>> wrote: Dear list, I have the following to Pandas Series: a, b. I want to slice and then subtract. Like this: a[1:4] - b[0:3]. Why does it give me NaN? But it works in Numpy. Example 1: did not work >>>a = pd.Series([85, 86, 87, 86]) >>>b = pd.Series([15, 72, 2, 3]) >>> a[1:4]-b[0:3] 0 NaN 1 14.0 2 85.0 3 NaN >>> type(a[1:4]) <class 'pandas.core.series.Series'> Example 2: worked If I use values() method, it's converted to a Numpy object. And it works! >>> a.values[1:4]-b.values[0:3] array([71, 15, 84]) >>> type(a.values[1:4]) <class 'numpy.ndarray'> What's the reason that Pandas in example 1 did not work? Isn't Numpy built on top of Pandas? So, why is everything ok in Numpy, but not in Pandas? Thanks in advance! _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion(a)python.org<mailto:NumPy-Discussion@python.org> https://mail.python.org/mailman/listinfo/numpy-discussion _______________________________________________ SciPy-User mailing list SciPy-User(a)python.org<mailto:SciPy-User@python.org> https://mail.python.org/mailman/listinfo/scipy-user _______________________________________________ SciPy-User mailing list SciPy-User(a)python.org<mailto:SciPy-User@python.org> https://mail.python.org/mailman/listinfo/scipy-user

7 8

Reminder: weekly status meeting Tues Feb 19 12:00 PST
by Matti Picus 17 Feb '19

17 Feb '19

This week the status meeting will be on Tues Feb 19 at 12:00 PST, not at the usual time The draft agenda is at https://hackmd.io/TtqnUDvPQgaGeej7zR8seA?both Everyone is invited to join. Matti, Tyler and Stefan

1 0

Why slicing Pandas column and then subtract gives NaN?
by C W 15 Feb '19

15 Feb '19

Dear list, I have the following to Pandas Series: a, b. I want to slice and then subtract. Like this: a[1:4] - b[0:3]. Why does it give me NaN? But it works in Numpy. Example 1: did not work >>>a = pd.Series([85, 86, 87, 86]) >>>b = pd.Series([15, 72, 2, 3]) >>> a[1:4]-b[0:3] 0 NaN 1 14.0 2 85.0 3 NaN >>> type(a[1:4]) <class 'pandas.core.series.Series'> Example 2: worked If I use values() method, it's converted to a Numpy object. And it works! >>> a.values[1:4]-b.values[0:3] array([71, 15, 84]) >>> type(a.values[1:4]) <class 'numpy.ndarray'> What's the reason that Pandas in example 1 did not work? Isn't Numpy built on top of Pandas? So, why is everything ok in Numpy, but not in Pandas? Thanks in advance!

2 2

'nansqrt' function?
by Mauro Cavalcanti 14 Feb '19

14 Feb '19

Dear ALL, In the process of porting an existing (but abandoned) package to the latest version of Numpy, I stumbled upon a call to a 'numpy.nansqrt' function, which seems not to exist. Here is the specific code: def normTrans(y): denom = np.nansqrt(np.nansum(y**2)) return y/denom As far as I could find, there is no such 'nansqrt' function in the current version of Numpy, so I suspect that the above code has not been properly tested. Am I right, or that function had existed in some past version of Numpy? Thanks in advance for any comments or suggestions. Best regards,

4 9

Porting code for Numpy 1.13+ to get rid of "boolean index did not match indexed array along dimension 1" error
by Mauro Cavalcanti 13 Feb '19

13 Feb '19

Dear ALL, I am trying to port an eigenalysis function that runs smoothly on Numpy 1.12 but fail miserably on Numpy 1.13 or higher with the dreadful error "boolean index did not match indexed array along dimension 1". Here is a fragment of the code, where the error occurrs: evals, evecs = np.linalg.eig(Syy) idx = evals.argsort()[::-1] evals = np.real(evals[idx]) U = np.real(evecs[:, idx]) evals = evals[evals > tolerance] U = U[:, evals > tolerance] # Here is where the error occurs So, I ask: is there a way out of this? Thanks in advance for any assistance you can provide.

2 2

Reminder: weekly status meeting Feb. 13 at 12:00 Pacific Time
by Tyler Reddy 13 Feb '19

13 Feb '19

Draft agenda: https://hackmd.io/f_e6dnssTkuIC0Pa0TEV6w?view There is a section for community suggested topics, feel free to join the conversation and add in topics that need attention. BIDS team

1 0

ANN: SciPy 1.2.1
by Tyler Reddy 09 Feb '19

09 Feb '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, On behalf of the SciPy development team I'm pleased to announce the release of SciPy 1.2.1, which is a bug fix release. Sources and binary wheels can be found at: https://pypi.org/project/scipy/ and at: https://github.com/scipy/scipy/releases/tag/v1.2.1 One of a few ways to install this release with pip: pip install scipy==1.2.1 ========================== SciPy 1.2.1 Release Notes ========================== SciPy 1.2.1 is a bug-fix release with no new features compared to 1.2.0. Most importantly, it solves the issue that 1.2.0 cannot be installed from source on Python 2.7 because of non-ASCII character issues. It is also notable that SciPy 1.2.1 wheels were built with OpenBLAS 0.3.5.dev, which may alleviate some linear algebra issues observed in SciPy 1.2.0. Authors ======= * Eric Larson * Mark Mikofski * Evgeni Burovski * Ralf Gommers * Eric Moore * Tyler Reddy Issues closed for 1.2.1 ------------------------ * `#9606 <https://github.com/scipy/scipy/issues/9606>`__: SyntaxError: Non-ASCII character '\xe2' in file scipy/stats/_continuous_distns.py on line 3346, but no encoding declared * `#9608 <https://github.com/scipy/scipy/issues/9608>`__: Version 1.2.0 introduces `too many indices for array` error in... * `#9709 <https://github.com/scipy/scipy/issues/9709>`__: scipy.stats.gaussian_kde normalizes the weights keyword argument... * `#9733 <https://github.com/scipy/scipy/issues/9733>`__: scipy.linalg.qr_update gives NaN result * `#9724 <https://github.com/scipy/scipy/issues/9724>`__: CI: Is scipy.scipy Windows Python36-32bit-full working? Pull requests for 1.2.1 ------------------------ * `#9612 <https://github.com/scipy/scipy/pull/9612>`__: BUG: don't use array newton unless size is greater than 1 * `#9615 <https://github.com/scipy/scipy/pull/9615>`__: ENH: Add test for encoding * `#9720 <https://github.com/scipy/scipy/pull/9720>`__: BUG: stats: weighted KDE does not modify the weights array * `#9739 <https://github.com/scipy/scipy/pull/9739>`__: BUG: qr_updates fails if u is exactly in span Q * `#9725 <https://github.com/scipy/scipy/pull/9725>`__: TST: pin mingw for Azure Win CI * `#9736 <https://github.com/scipy/scipy/pull/9736>`__: TST: adjust to vmImage dispatch in Azure * `#9681 <https://github.com/scipy/scipy/pull/9681>`__: BUG: Fix failing stats tests (partial backport) * `#9662 <https://github.com/scipy/scipy/pull/9662>`__: TST: interpolate: avoid pytest deprecations Checksums ========= MD5 ~~~ 982810997da9daab2e512a6c27918889 scipy-1.2.1-cp27-cp27m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 9500cad49b7eac9786c90cba146ad357 scipy-1.2.1-cp27-cp27m-manylinux1_i686.whl fe9ba7f16e0e7f7c9cd59d39ea8e9545 scipy-1.2.1-cp27-cp27m-manylinux1_x86_64.whl f1823b26b2afda2027f78df427791700 scipy-1.2.1-cp27-cp27m-win32.whl c0692c60b4baaafd99fb2bf0c689bbf1 scipy-1.2.1-cp27-cp27m-win_amd64.whl b5a5b9b146bac064a7921c5121d5e19c scipy-1.2.1-cp27-cp27mu-manylinux1_i686.whl fd637f4dc4308ae9cf7655e3e5f3a27d scipy-1.2.1-cp27-cp27mu-manylinux1_x86_64.whl 8faae90250009230cd2f7845ba4735f2 scipy-1.2.1-cp34-cp34m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl a28a93cb20987666f788d43c50e2ab79 scipy-1.2.1-cp34-cp34m-manylinux1_i686.whl 26264ebb568728065e3ef73b5419793a scipy-1.2.1-cp34-cp34m-manylinux1_x86_64.whl fbb79da3d5823ba0f23b0f8d50023bfd scipy-1.2.1-cp34-cp34m-win32.whl f82cf6834e4e2a2e4008fec5da2f4b0b scipy-1.2.1-cp34-cp34m-win_amd64.whl cc248fd969b11589d98bcb550330e08d scipy-1.2.1-cp35-cp35m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 3b5e8eb89a49fb7bc506cf17a54b926b scipy-1.2.1-cp35-cp35m-manylinux1_i686.whl 0cd66785fd9f8390494f42beb499f56a scipy-1.2.1-cp35-cp35m-manylinux1_x86_64.whl 379d37ae932af2096e037b4defd4cf60 scipy-1.2.1-cp35-cp35m-win32.whl 5dd4c47c501c96dc0c20b72521058133 scipy-1.2.1-cp35-cp35m-win_amd64.whl 6fa013443295e55c96eb174578dcffee scipy-1.2.1-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 5069317ab38e3dfbb8923341c2b23a69 scipy-1.2.1-cp36-cp36m-manylinux1_i686.whl 8e6a1fd1354428074d8457fe46cd4f7c scipy-1.2.1-cp36-cp36m-manylinux1_x86_64.whl 27142bff898a18368032165c27c11466 scipy-1.2.1-cp36-cp36m-win32.whl 489fd885aefd07bded69a8e0452c16b0 scipy-1.2.1-cp36-cp36m-win_amd64.whl 84ef33013d9871f23db0ecad25552636 scipy-1.2.1-cp37-cp37m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 7b7ae846b70e60188b3d772e9d60d3d2 scipy-1.2.1-cp37-cp37m-manylinux1_i686.whl 21b29788cd2c037366d2ff5d54ae7517 scipy-1.2.1-cp37-cp37m-manylinux1_x86_64.whl e11ce933d012481ea27fe49314b606aa scipy-1.2.1-cp37-cp37m-win32.whl 23424815af8e69f945bb406a0c1be6c6 scipy-1.2.1-cp37-cp37m-win_amd64.whl fe88877767563e50078df86dadf7b1f4 scipy-1.2.1.tar.gz 312110f3ea37269003e587207eb72855 scipy-1.2.1.tar.xz b4e2b70f7885a746618e8bcdf77857d7 scipy-1.2.1.zip SHA256 ~~~~~~ f06819b028b8ef9010281e74c59cb35483933583043091ed6b261bb1540f11cc scipy-1.2.1-cp27-cp27m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 70e37cec0ac0fe95c85b74ca4e0620169590fd5d3f44765f3c3a532cedb0e5fd scipy-1.2.1-cp27-cp27m-manylinux1_i686.whl 9726791484f08e394af0b59eb80489ad94d0a53bbb58ab1837dcad4d58489863 scipy-1.2.1-cp27-cp27m-manylinux1_x86_64.whl 790cbd3c8d09f3a6d9c47c4558841e25bac34eb7a0864a9def8f26be0b8706af scipy-1.2.1-cp27-cp27m-win32.whl 014cb900c003b5ac81a53f2403294e8ecf37aedc315b59a6b9370dce0aa7627a scipy-1.2.1-cp27-cp27m-win_amd64.whl 78e12972e144da47326958ac40c2bd1c1cca908edc8b01c26a36f9ffd3dce466 scipy-1.2.1-cp27-cp27mu-manylinux1_i686.whl f15f2d60a11c306de7700ee9f65df7e9e463848dbea9c8051e293b704038da60 scipy-1.2.1-cp27-cp27mu-manylinux1_x86_64.whl e2cfcbab37c082a5087aba5ff00209999053260441caadd4f0e8f4c2d6b72088 scipy-1.2.1-cp34-cp34m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl b86ae13c597fca087cb8c193870507c8916cefb21e52e1897da320b5a35075e5 scipy-1.2.1-cp34-cp34m-manylinux1_i686.whl 865afedf35aaef6df6344bee0de391ee5e99d6e802950a237f9fb9b13e441f91 scipy-1.2.1-cp34-cp34m-manylinux1_x86_64.whl e742f1f5dcaf222e8471c37ee3d1fd561568a16bb52e031c25674ff1cf9702d5 scipy-1.2.1-cp34-cp34m-win32.whl f6b88c8d302c3dac8dff7766955e38d670c82e0d79edfc7eae47d6bb2c186594 scipy-1.2.1-cp34-cp34m-win_amd64.whl 7274735fb6fb5d67d3789ddec2cd53ed6362539b41aa6cc0d33a06c003aaa390 scipy-1.2.1-cp35-cp35m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 963815c226b29b0176d5e3d37fc9de46e2778ce4636a5a7af11a48122ef2577c scipy-1.2.1-cp35-cp35m-manylinux1_i686.whl 281a34da34a5e0de42d26aed692ab710141cad9d5d218b20643a9cb538ace976 scipy-1.2.1-cp35-cp35m-manylinux1_x86_64.whl 5a10661accd36b6e2e8855addcf3d675d6222006a15795420a39c040362def66 scipy-1.2.1-cp35-cp35m-win32.whl def0e5d681dd3eb562b059d355ae8bebe27f5cc455ab7c2b6655586b63d3a8ea scipy-1.2.1-cp35-cp35m-win_amd64.whl 79792c8fe8e9d06ebc50fe23266522c8c89f20aa94ac8e80472917ecdce1e5ba scipy-1.2.1-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 6dcc43a88e25b815c2dea1c6fac7339779fc988f5df8396e1de01610604a7c38 scipy-1.2.1-cp36-cp36m-manylinux1_i686.whl f31338ee269d201abe76083a990905473987371ff6f3fdb76a3f9073a361cf37 scipy-1.2.1-cp36-cp36m-manylinux1_x86_64.whl 9de84a71bb7979aa8c089c4fb0ea0e2ed3917df3fb2a287a41aaea54bbad7f5d scipy-1.2.1-cp36-cp36m-win32.whl b2c324ddc5d6dbd3f13680ad16a29425841876a84a1de23a984236d1afff4fa6 scipy-1.2.1-cp36-cp36m-win_amd64.whl 588f9cc4bfab04c45fbd19c1354b5ade377a8124d6151d511c83730a9b6b2338 scipy-1.2.1-cp37-cp37m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl 628f60be272512ca1123524969649a8cb5ae8b31cca349f7c6f8903daf9034d7 scipy-1.2.1-cp37-cp37m-manylinux1_i686.whl 870fd401ec7b64a895cff8e206ee16569158db00254b2f7157b4c9a5db72c722 scipy-1.2.1-cp37-cp37m-manylinux1_x86_64.whl d78702af4102a3a4e23bb7372cec283e78f32f5573d92091aa6aaba870370fe1 scipy-1.2.1-cp37-cp37m-win32.whl ba0488d4dbba2af5bf9596b849873102d612e49a118c512d9d302ceafa36e01a scipy-1.2.1-cp37-cp37m-win_amd64.whl e085d1babcb419bbe58e2e805ac61924dac4ca45a07c9fa081144739e500aa3c scipy-1.2.1.tar.gz be0e1b322b4b9f2ab88a35db32c494f12639937cf671d4cc210238feb8d5a89d scipy-1.2.1.tar.xz 8140810cf19707c732f330ba6e54968bc85160768850bfbf38d995193e597e2e scipy-1.2.1.zip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJcXk5KAAoJELD/41ZX0J71zZ0P/3/6ZgXpYGEA013LKNh+/PrV YSA2G7b4jGYExim4cgFHDrwBPoFwiVcfdBTPMxSYn8mtvuqyn4TlcmxqGKQkOwoS zdOEUHdxPFLt8nAy5rWjiCYHzC4qCpGnt+3ROVzRjGA2BLSdzqBg+njT2+9FKNrH 5UoZP4s3TCA8Yn4z2bYV+2viHTAXFsEhHFraNuK5MQu045E57gt5VwYm+ylEeE3Q npcO2U8vio7Hr8ARVOyvQqL8HsQy5/8q8lGTBLbBAP+ujPXi3lRwdb2KqPl3ojfE 7afkEdC3W44CCxPoJfLOdwFnsaOUGVtFeNKmcS2YNWregMpjeG68AjjHO1vCeM34 twNXrwhO2gROwYnp6Q22TTiMsPTTUvce+qGmAyD1d4osOG5zz1A/YQWxHw8Runl0 LPrVt46aOUJTvjCAFs6c7McY04j6lILMyGZlxpyGwLEkP9YAABGvbOtHDMBBWvJs CFxLAo4gEWfJKcJ0bnAKQ9HNeJ45JJ3PQLD5eEmOl+TOQjl0nzY4c7D4LYB0wpl2 NY7tr/TcASX7TlwbjzmlccJUDmNhekcZVTbx65NFjmb2/nUgqAB9ZVjJKyQDpZng rLXZitBmd8IRb8xXp5Smbgt0VccwbMfJF4fulnrVokwILhsIbwZlYQDCG6KOPV27 mObh7S2ZazRQ76Gd4rcu =HBJ8 -----END PGP SIGNATURE-----

1 0

New sorting routines.
by Charles R Harris 08 Feb '19

08 Feb '19

Hi All, I've put up gh-12945 <https://github.com/numpy/numpy/pull/12945> that preserves forward compatibility of NumPy after the addition of timsort by reusing the mergesort slot in PyArray_ArrFuncs for stable sorts in general, not just mergesort. The same method can be used when we add radixsort for integer types. See the discussion at the PR link for more details on the nature of the problem and considerations for the dtype proposals. I'm waiting on agreement that this is the way to go before proceeding. Chuck

1 0