| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
the files in doc/ and numpy/ were covered in previous commits
|
|\
| |
| | |
BLD: remove __NUMPY_SETUP__ from builtins at end of setup.py
|
| |
| |
| |
| | |
May help reduce the occurrence of gh-2434.
|
|/ |
|
| |
|
|
|
|
|
| |
Numpy 1.12.0 will support Python 2.7, 3.4 and 3.5 with support for
2.6, 3.2, and 3.3 dropped, so remove the latter.
|
| |
|
|
|
|
|
| |
Add note about wheels on pypi, and Windows wheels in particular. See
discussion at: https://github.com/numpy/numpy/issues/5479
|
|
|
|
|
| |
This was seriously broken. Setuptools does unwanted 'smart' things and
ignores MANIFEST.in. Closes gh-7127.
|
|
|
|
|
|
|
| |
* Drop testing of Python 2.6, 3.2, and 3.3
* Create 1.12.0-notes.rst and add to source/documentation.
* Update pavement.py to use 1.10.x as LOG_START
* Update version numpy in setup.py
|
|
|
|
| |
Address comments of @charris on gh-6895.
|
| |
|
|
|
|
|
| |
Also ignore setup.cfg: this file is created/modified by the
alias/setopt/saveopts commands, and therefore needs to be in .gitignore.
|
| |
|
| |
|
|
|
| |
Not only bdist_wheel needs setuptools
|
|\
| |
| | |
Fix use of __doc__ in setup.py for -OO mode
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Revert mingwpy modifications to distutils. They are causing problems
for non-windows builds and it is better to wait until mingypy is
further along.
This reverts commit 96abd32de241864ee97f30357234cbc9a96c43ae, reversing
changes made to 06af9918f6bf03b8d818ec834f9fb48db57d1489.
|
|
|
|
|
|
|
|
|
|
| |
Needed to build numpy with Microsoft Visual C++ Compiler for Python 2.7
Otherwise one gets an Unable to find vcvarsall.bat error
SET DISTUTILS_USE_SDK=1
SET MSSdk=1
triggers the same from distutils.
|
|
|
|
|
|
|
|
| |
Adds missing `Programming Language :: Python :: 3` to bento.info
Adds new `Programming Language :: Python :: {2..,3..,CPython..}` to both
These versions are correct for the 1.10.x and 1.11.x releases.
They reflect the commit b06dbc15d9db0e224d338c84ac98a925a7945d4c
|
|
|
|
|
|
|
|
| |
Create 1.11.0-notes.rst template.
Update version number in setup.py.
Update version number in numpyconfig.h.
Update version number in pavement.py.
Update version number in bento.info.
|
| |
|
| |
|
|
|
|
| |
e.g. 1.10.0.dev-243ab56 to 1.10.0.dev+243ab56
|
|\
| |
| | |
MAINT: start 1.10-devel.
|
| |
| |
| |
| |
| |
| | |
* Create 1.10.0-notes.
* Add 1.10.-notes to the generated documentation.
* Update version number in setup.py
|
|/
|
|
|
| |
Wheel build was not cythonizing sources, giving a compile error because
needed `numpy/random/mtrand/mtrand.c` was missing.
|
|
|
|
|
|
|
| |
Instead generate at build time. The generated sources are still part of
the sdist.
tools/cythonize.py is copied from SciPy with small changes to the
configuration.
|
|
|
|
| |
prevents broken source distributions due to not up to date submodules.
|
| |
|
|
|
|
| |
Numpy 1.9.0-devel opens.
|
|
|
|
|
|
|
|
|
|
| |
Because Numpy 1.8.0 will no longer supports Python versions < 2.6 we
no longer need to check for that and can also remove the code that is
specific to those earlier versions.
To make this a bit safer, the toplevel setup.py file now contains a
check of the Python version number and raises an error when run by an
unsupported version.
|
|
|
|
|
|
| |
The same code base now supports python versions 2.6-2.7 and 3.2-3.3.
Closes #3247.
|
|
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `imports` fixer deals with the standard packages that have been
renamed, removed, or methods that have moved.
cPickle -- removed, use pickle
commands -- removed, getoutput, getstatusoutput moved to subprocess
urlparse -- removed, urlparse moved to urllib.parse
cStringIO -- removed, use StringIO or io.StringIO
copy_reg -- renamed copyreg
_winreg -- renamed winreg
ConfigParser -- renamed configparser
__builtin__ -- renamed builtins
In the case of `cPickle`, it is imported as `pickle` when python < 3 and
performance may be a consideration, but otherwise plain old `pickle` is
used.
Dealing with `StringIO` is a bit tricky. There is an `io.StringIO`
function in the `io` module, available since Python 2.6, but it expects
unicode whereas `StringIO.StringIO` expects ascii. The Python 3
equivalent is then `io.BytesIO`. What I have done here is used BytesIO
for anything that is emulating a file for testing purposes. That is more
explicit than using a redefined StringIO as was done before we dropped
support for Python 2.4 and 2.5.
Closes #3180.
|
|
|
|
|
|
|
|
| |
This should be harmless, as we already are division clean. However,
placement of this import takes some care. In the future a script
can be used to append new features without worry, at least until
such time as it exceeds a single line. Having that ability will
make it easier to deal with absolute imports and printing updates.
|
|
|
|
|
| |
Generally, this involves using list comprehension, or explicit list
construction as `filter` is an iterator in Python 3.
|
| |
|
| |
|
|
|
|
| |
Closes Trac ticket 2243.
|
| |
|
| |
|
|
|
|
| |
Also works inside a virtualenv.
|
|
|
|
|
| |
Occurs only on Python 3.x when a version.py file is already present, due to
copying the whole tree into build/pyk3/.
|
|
|
|
|
| |
This is not a complete fix yet. Should be handled correctly in binary
installers.
|
|
|
|
|
| |
This was first fixed in commit 0131218 (but that broke the paver script), and
broken again in commit 13212a5d. Should now work in both cases.
|
| |
|
| |
|