summaryrefslogtreecommitdiff
path: root/numpy
Commit message (Collapse)AuthorAgeFilesLines
* FIX: simplify the import statementOndřej Čertík2012-08-311-2/+1
|
* Fix returned copyJay Bourque2012-08-312-1/+10
| | | | Fix returned copy so that copy of view with offsets copies only fields in view, not all the fields from original array. Also add unit tests to make sure this doesn't break when copy is fully deprecated in favor of returning a view.
* MAINT: silence DeprecationWarning in np.safe_eval().Ralf Gommers2012-08-221-4/+14
| | | | | It comes from the Python compiler package, which isn't available on Python 3.x. We already handle that issue by instead importing the ast module.
* BUG: fix bento build.David Cournapeau2012-08-111-1/+1
|
* Merge pull request #373 from cianci/concatenate_leak_fixCharles Harris2012-08-041-0/+2
|\ | | | | Fix memory leak in concatenate.
| * Fix memory leak in concatenate.Chris2012-08-031-0/+2
| | | | | | | | Temporary array was not being freed after use.
* | Use PyUnicode_DecodeUTF32()Ondrej Certik2012-08-031-18/+11
| | | | | | | | | | This function handles the swapping automatically and it returns a unicode object in one of: UCS1, UCS2 or UCS4 internal Python format.
* | Follow the C guidelinesOndrej Certik2012-08-031-2/+4
| |
* | FIX: Make sure the tests produce valid unicodeOndrej Certik2012-08-031-2/+4
| | | | | | | | | | The tests are testing byte order for unicode, so we can only use such unicode data, so that both versions (swapped and unswapped) are valid unicode.
* | FIX: Fixes the PyUnicodeObject problem in py-3.3Ondrej Certik2012-08-032-0/+40
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously NumPy did not compile in Python 3.3 due to the changes in PEP 393. This patch simply calls PyUnicode_FromKindAndData() from the new Python 3.3 API and possibly swaps the data before calling it if needed. The data in NumPy is always UCS4 and the PyUnicode_FromKindAndData() internally converts it to UCS1, UCS2 or UCS4 depending on the maximum code point. The following tests now fail, because they produce invalid unicode in the process (will be fixed in the next patch): ====================================================================== ERROR: Check byteorder of 0-dimensional objects ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ondrej/py33/lib/python3.3/site-packages/numpy/core/tests/test_unicode.py", line 277, in test_values0D self.assertTrue(ua[()] != ua2[()]) SystemError: invalid maximum character passed to PyUnicode_New ====================================================================== ERROR: Check byteorder of multi-dimensional objects ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ondrej/py33/lib/python3.3/site-packages/numpy/core/tests/test_unicode.py", line 297, in test_valuesMD self.assertTrue(ua[0,0,0] != ua2[0,0,0]) SystemError: invalid maximum character passed to PyUnicode_New ====================================================================== ERROR: Check byteorder of single-dimensional objects ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ondrej/py33/lib/python3.3/site-packages/numpy/core/tests/test_unicode.py", line 286, in test_valuesSD self.assertTrue(ua[0] != ua2[0]) SystemError: invalid maximum character passed to PyUnicode_New ====================================================================== ERROR: Check byteorder of 0-dimensional objects ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ondrej/py33/lib/python3.3/site-packages/numpy/core/tests/test_unicode.py", line 277, in test_values0D self.assertTrue(ua[()] != ua2[()]) SystemError: invalid maximum character passed to PyUnicode_New ====================================================================== ERROR: Check byteorder of multi-dimensional objects ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ondrej/py33/lib/python3.3/site-packages/numpy/core/tests/test_unicode.py", line 297, in test_valuesMD self.assertTrue(ua[0,0,0] != ua2[0,0,0]) SystemError: invalid maximum character passed to PyUnicode_New ====================================================================== ERROR: Check byteorder of single-dimensional objects ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ondrej/py33/lib/python3.3/site-packages/numpy/core/tests/test_unicode.py", line 286, in test_valuesSD self.assertTrue(ua[0] != ua2[0]) SystemError: invalid maximum character passed to PyUnicode_New
* Merge pull request #371 from rlamy/bytes-pickleTravis E. Oliphant2012-08-022-2/+11
|\ | | | | Copy bytes object for small arrays when unpickling an array
| * Re-enable unpickling optimization for large py3k bytes objects.Ronan Lamy2012-08-031-2/+3
| | | | | | | | | | Mutating a bytes object is theoretically unsafe, but doesn't cause any problem in any existing version of CPython.
| * Copy bytes object when unpickling an arrayRonan Lamy2012-07-312-2/+10
| |
* | Fix tests for empty shape, strides and suboffsets on Python 3.3cgohlke2012-07-281-7/+16
|/
* [FIX] Add missing header so separate compilation works againNathaniel J. Smith2012-07-181-0/+1
| | | | | | (Broken by PR #350.) Should be applied to maintenance/1.7.x as well.
* Merge pull request #325 from ahmadia/patch-2Travis E. Oliphant2012-07-171-4/+4
|\ | | | | prefer gfortran (gnu95) over vendor compilers, g77, g95 on OSX & Linux
| * prefer gfortran over g77 and vendor compilers on OS X and LinuxAron Ahmadia2012-07-171-4/+4
| |
| * Merge branch 'master' of https://github.com/numpy/numpy into patch-2Aron Ahmadia2012-07-1790-3395/+5258
| |\
| * | prefer gfortran (g95) over vendor compilers, g77 and g95 on OSX and Linux. ahmadia2012-06-281-8/+8
| | | | | | | | | Retain preference for g77 on Windows and vendor compilers on other platforms.
* | | BUG: Fix some tests in PR #192Travis E. Oliphant2012-07-171-8/+8
| | |
* | | Fix-up logic so that it is more readable.Travis E. Oliphant2012-07-171-9/+12
| | |
* | | Merge remote-tracking branch 'hackerschool/2028fix'Travis E. Oliphant2012-07-172-1/+33
|\ \ \
| * | | Added cast to error check, and fixed indentation.Eric Fode2012-07-151-2/+3
| | | |
| * | | more tabs removed (hunting for c formatter to take care of this next time)Eric Fode2012-07-151-8/+8
| | | |
| * | | Tab FixEric Fode2012-07-141-1/+1
| | | |
| * | | Style FixEric Fode2012-07-141-5/+7
| | | |
| * | | BUG: ticket #2028: When min_scalar was not checking to see if numbers could ↵Eric Fode2012-07-142-2/+31
| | | | | | | | | | | | | | | | fit into unsigned long longs. This was fixed by adding an extra case to function to check if the passed number could fit into a unsigned long long if it could not fit into anything else. Additionaly, regression tests were added.
* | | | Merge pull request #350 from jayvius/get-view2Travis E. Oliphant2012-07-174-18/+69
|\ \ \ \ | | | | | | | | | | Add transition code for returning view when selecting subset of fields
| * | | | change DeprecationWarning to FutureWarningJay Bourque2012-07-171-2/+2
| | | | |
| * | | | Add tests for record array indexingJay Bourque2012-07-171-6/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - add tests for record array indexing with multiple field names - add tests for DeprecationWarning when writing to array returned by record array indexing with multiple field names
| * | | | Updated reference docs for DeprecationWarningJay Bourque2012-07-171-3/+4
| | | | |
| * | | | Call view object's copy methodjayvius2012-07-171-2/+1
| | | | |
| * | | | Change WARN_ON_WRITE Deprecation Warningjayvius2012-07-171-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | Change WARN_ON_WRITE Deprecation Warning to include returning a copy when selecting muultiple fields of a structured array.
| * | | | fix previous commit to return copy of view instead of viewjayvius2012-07-172-14/+8
| | | | |
| * | | | Add ability to get view when selecting subset of fields.jayvius2012-07-172-0/+8
| | |_|/ | |/| | | | | | | | | | | | | | | | | | Add ability to get view when selecting subset of fields in a struct array, for numpy 1.8.0. Currently a copy is still returned - set WARN_ON_WRITE flag which will be removed in a future version of numpy.
* | | | Merge pull request #352 from HackerSchool12/bugfix808Travis E. Oliphant2012-07-172-14/+9
|\ \ \ \ | | | | | | | | | | BF bug #808
| * | | | BUG: Ticket #808: Insert was not performing properly when an integer wasLoftie Ellis2012-07-152-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the argument passed to be used as the item to be insterted, and a list was passed as the positions. This was fixed by simply duplicating the item to be inserted so that it was a list of equal length and then control was passed to the already exsisting code to handel this case
* | | | | Merge pull request #192 from rgommers/meshgrid3dTravis E. Oliphant2012-07-172-33/+134
|\ \ \ \ \ | | | | | | | | | | | | Meshgrid enhancements (>2-D, sparse grids, matrix indexing)
| * | | | | STY: meshgrid: some minor changes to address review comments.Ralf Gommers2012-02-052-5/+2
| | | | | |
| * | | | | TST: meshgrid: test expected shapes for Cartesian and matrix indexing.Ralf Gommers2011-12-282-6/+23
| | | | | |
| * | | | | BUG: meshgrid: raise error on single input.Ralf Gommers2011-12-282-4/+9
| | | | | |
| * | | | | MAINT: clean up docstring and some minor items in meshgrid. Remove ndgrid.Ralf Gommers2011-12-132-44/+36
| | | | | |
| * | | | | ENH: enhance meshgrid to generate 3D grids, sparse grids, matrix indexing.Per A. Brodtkorb2011-12-132-34/+124
| | | | | |
* | | | | | Merge pull request #327 from teoliphant/restore_apiTravis E. Oliphant2012-07-172-10/+10
|\ \ \ \ \ \ | | | | | | | | | | | | | | Restore ability to not include semi-colons.
| * | | | | | API: Restore ability to not use semicolons.Travis E. Oliphant2012-06-281-2/+2
| | | | | | |
| * | | | | | Restore ability to not include semi-colons.Travis E. Oliphant2012-06-251-8/+8
| | | | | | |
* | | | | | | Merge pull request #348 from njsmith/fix-shufflenjsmith2012-07-175-8416/+7874
|\ \ \ \ \ \ \ | |_|_|_|/ / / |/| | | | | | [FIX] Make np.random.shuffle less brain-dead
| * | | | | | [FIX] Make np.random.shuffle less brain-deadNathaniel J. Smith2012-07-175-8416/+7874
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The logic in np.random.shuffle was... not very sensible. Fixes trac ticket #2074. This patch also exposes a completely unrelated issue in numpy.testing. Filed as Github issue #347 and marked as knownfail for now.
* | | | | | | Switch WARN_ON_WRITE to issuing FutureWarnings instead of DeprecationWarningsNathaniel J. Smith2012-07-174-13/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FutureWarnings are displayed by default, so they should be used whenever a future change will change the semantics of existing code (as opposed to making existing code simply stop working). List discussion: http://www.mail-archive.com/numpy-discussion@scipy.org/msg37500.html
* | | | | | | Fix `WindowsError: [Error 32]` in test_not_closing_opened_fid ↵cgohlke2012-07-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (test_io.TestSavezLoad)