WIP: preparing for numpy 1.9.4 release #6349
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
Point release notes to doc/release/1.9.0-notes.rst Set LOG_START to 'v1.8.1' Set LOG_END to 'maintenance/1.9.x' Set raise_warnings to "release" in NoseTester constructor.
merge master into 1.9 branch
DOC: add version added tag to new linspace dtype argument
e.g. doubles are only aligned to 4 bytes on i386 so one cannot peel them to 16 byte alignment. Closes numpygh-4853
Replaces the current method to zero items, from multiplication to using `np.where`.
Backports stuff from master to 1.9
ENH: avoid meshgrid and fancy indexing for 1d masked sort, for 1.9
DEP: deprecate float as axis argument to reductions, for 1.9
BUG: core: fix crash when unpickling data on Py3 under non-latin1 encoding
ENH: core: add hack enabling unpickling Py2 pickled scalars on Py3 under encoding='latin1'
BLD: fix build issues with MSVC10 on Windows. Closes numpygh-4245.
ENH: core: make unpickling with encoding='bytes' work
BUG: initialize object array of array on resize and zeros
BUG Masked recarray assignment with [row][record] does not work
BUG: object array np.conjugate, ndarray.conjugate inconsistent
TST: win32 also does not provide 16 byte alignment, for 1.9
documentation updates for 1.9
BUG: None comparison deprecation does not affect scalars
BUG: fix string type inconsistency between zeros and zeros_like, for 1.9
The ufunc override `__numpy_ufunc__` still has a few unresolved issues regarding its behavior towards Python operators see numpygh-4815. To avoid releasing numpy with an interface that might change in the next numpy version and to not further delay the 1.9 release it has been decided to disable the feature in 1.9.0.
disable ufunc override for 1.9 release
MAINT: also disable has_ufunc_attr
Charris pep8 numpy lib for 1.9
The error is in the StringConverter.upgrade docstring.
Pep8 numpy polynomial
BUG: Fix a reference leak in ufunc type resolution.
argpartition does not fail anymore on non-ndarray array-likes. Fix as implemented by @maniteja123.
…c regression test
BUG: Fixes ndarray.fill to accept maximum uint64 value
DOC: Describe return_counts keyword in np.unique docstring
more backports for 1.9.2
MAINT: distutils: LIBPATH with spaces is now supported Python 2.7+ and Win32
I'm not sure exactly when GzipFile.seek started supporting the whence= argument by default -- sometime around python 2.5 from the looks of http://bugs.python.org/issue1355023. But in 8000 any case it was definitely there by 2.6, which is now the earliest version we support, so there's no longer any need to monkeypatch it in. This also fixes an error in python 3.5b2, which I haven't bothered to track down further because these are the wages of monkeypatching.
Ensure that build_ext.include_dirs is the same physical list as build_ext.distribution.include_dirs. Conflicts: numpy/distutils/command/build_ext.py
The /Qlowercase and /us options has been deprecated in the Intel Visual Fortran Compiler since at least version 2013. Replace with /names:lowercase and /assume:underscore.
Update pavement.py and setup.py with changes to release versions.
allows pep 338 execution via python -mnumpy.f2py
Command `bdist_wheel` was generating a shebang line for f2py that uses the Python path for the building Python. If we are building a wheel or an egg, use the generic `#!python` shebang line for the f2py script instead, which setuptools will modify at install time. Closes numpygh-5812.
Add other binary distribution formats to list of build commands that should generate !python shebang lines.
bdist_mpkg is a very crude install method that will assume the path to Python, so we should not use the `#!python` form when installing scripts in bdist_mpkg.
Module tests whether we can run f2py and return correct version. Skip this test when running in-place (we don't install f2py in that case). Use our own virtualenvs in travis-ci to avoid picking up travis' numpy.
|
:) sorry forgot the base. |
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.
Add fix for f2py script installation from wheels into virtualenvs.