Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | MAINT: Remove unnecessary 'from __future__ import ...' statements | Jon Dufresne | 2020-01-03 | 1 | -2/+0 |
| | | | | | As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior. | ||||
* | ENH: changes from review | mattip | 2019-05-11 | 1 | -25/+29 |
| | |||||
* | BUG: parametrize tests, fix for interaction of count, order | mattip | 2019-05-11 | 1 | -41/+69 |
| | |||||
* | ENH: add 'order' keyword to packbits, unpackbits | mattip | 2019-05-11 | 1 | -6/+21 |
| | |||||
* | ENH: Added count parameter to unpackbits | Joseph Fox-Rabinovitz | 2019-02-25 | 1 | -0/+63 |
| | | | | | | | | Tests are included. Couple of minor fixes: - Fixed packbits/unpackbits docs to reflect proper keyword names - Added .pytest_cache to .gitignore | ||||
* | MAINT: Remove all uses of run_module_suite. | Charles Harris | 2018-04-06 | 1 | -7/+1 |
| | | | | | That function is nose specific and has not worked since `__init__` files were added to the tests directories. | ||||
* | BUG: fix wrong odd determination in packbits | Julian Taylor | 2017-02-19 | 1 | -0/+9 |
| | | | | closes gh-8637 | ||||
* | TST: add extended packbits tests | Julian Taylor | 2017-01-12 | 1 | -1/+178 |
| | | | | | Larger data to account for future vectorization. Also add benchmarks for packbits and unpackbits | ||||
* | BUG: fix packbits and unpackbits to correctly handle empty arrays | Takuya Akiba | 2016-12-02 | 1 | -2/+63 |
| | |||||
* | MAINT: Include from __future__ boilerplate in some files missing it. | Charles Harris | 2015-12-05 | 1 | -1/+2 |
| | | | | | Some newer *.py files are missing the `from __future__` boilerplate that helps assure Python2 and Python3 compatibility. | ||||
* | ENH ensure np.packbits works on np.bool dtype | Lars Buitinck | 2014-11-30 | 1 | -6/+10 |
| | |||||
* | MAINT/TST: refactor and test packbits/unpackbits | Lars Buitinck | 2014-11-30 | 1 | -0/+22 |
Pushes the GIL release one loop outward. First test for these functions (!). Incorporates suggestions by @jaimefrio and @charris. |