| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
http://cens.ioc.ee/projects/f2py2e/ is unavailable and links to NumPy and SciPy at https://web.archive.org/web/20140822061353/http://cens.ioc.ee:80/projects/f2py2e/ are too outdated.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Changqing Li <changqing.li@windriver.com>
|
|
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
|
|
|
| |
pip will itself call setup.py install with the rights options.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds entry_points for the f2py scripts. The installed scripts
differ between Windows and other environments.
* On Windows, the only script installed is 'f2py'. This works well in
that environment because each Python version is installed in its own
directory, making it easy to keep the differing script versions
separate.
* Otherwise, three scripts are installed, 'f2py', 'f2py' + 'minor', and
'f2py' + 'major.minor'. For instance, if Numpy is installed by
Python 2.7, then the installed scripts will be named 'f2py', 'f2py2',
and 'f2py2.7'. That naming scheme is used for back compatibility, and
also so that more than one Python version can be dealt with in a way
common to many Linux distros. Note that 'f2py' will always point to
the latest install and 'f2py(2|3)' to the latest Python (2|3) install
The script tests have been modified to check for the new environment
and the code previously used to install the scripts has been removed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Found via `codespell -q 3 -I ../numpy-whitelist.txt`
Whitelist consists of:
```
amin
ans
behaviour
cancellation
dum
initialise
ith
nd
ot
splitted
writeable
```
.
|
|
|
|
|
| |
Decided to bite the bullet on this one. The code is certainly more
readable, so should be easier to fix if we need to.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Add other binary distribution formats to list of build commands that
should generate !python shebang lines.
|
|
|
|
|
|
|
|
|
| |
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 gh-5812.
|
|
|
|
| |
allows pep 338 execution via python -mnumpy.f2py
|
|
|
|
|
| |
minimum requirement is python2.6, this allows removing a couple 2.3 and
2.4 checks.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following directories and files have been moved or deleted
numpy/lib/benchmarks
numpy/f2py/docs
numpy/f2py/f2py.1
This PR removes references to them from the relevant setup.py files.
Closes #5010.
|
|
|
|
|
|
|
| |
Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long
and will need to be broken at some point. OTOH, some lines were already
too long and need to be broken at some point. Now seems as good a time
as any to do this with open PRs at a minimum.
|
|
|
|
|
|
|
|
|
| |
The f2py executable has a shebang which uses the default python, rather
than the python it was compiled for. This causes issues for deployment
of numpy (+f2py) across systems which have different environments.
This fix uses sys.executable to determine the resulting hardcoded
python to use.
|
|
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to Lisandro Dalcin.
|
|
|
|
|
|
| |
Rewrite F2Py's test suite, so that it is run as a part of Numpy's tests.
These tests require compiling extension modules on-the-fly, so I added
a small helper module for that.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
extraneous whitespace
|
| |
|
| |
|
|
|