| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
Break long lines.
Spaces around operators.
Remove dead code.
|
|/ |
|
|
|
| |
Closes #3405
|
|
|
|
|
|
|
| |
The version check flag for GnuFCompiler and Gnu95FCompiler were changed from
`--version` to `-dumpversion`. This simplifies the gnu_version_match code for
gfortran, and makes it possible to drop much of the check code for g77 as
well. This fix addresses issue #5315 and #5321.
|
|\
| |
| |
| | |
support rpath for GNU Fortran compiler.
|
| | |
|
|/
|
|
| |
Similar to C builds which always have debug info.
|
|
|
|
|
|
|
|
| |
Cray and other HPC vendors provide patched versions of the GNU compilers
with modified version strings. Use re.search instead of re.match in the
version detection scripts to account for modified version strings.
Ref: https://github.com/numpy/numpy/issues/4259
|
|
|
|
|
|
|
| |
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 custom build compiler "GNU Fortran (rubenvb-4.8.0) 4.8.0" was
incorrectly parsed as version '-4.8.0' and the flag "-mno-cygwin" was
added to the compilation.
See http://cens.ioc.ee/pipermail/f2py-users/2010-October/002092.html.
|
|
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new import `absolute_import` is added the `from __future__ import`
statement and The 2to3 `import` fixer is run to make the imports
compatible. There are several things that need to be dealt with to make
this work.
1) Files meant to be run as scripts run in a different environment than
files imported as part of a package, and so changes to those files need
to be skipped. The affected script files are:
* all setup.py files
* numpy/core/code_generators/generate_umath.py
* numpy/core/code_generators/generate_numpy_api.py
* numpy/core/code_generators/generate_ufunc_api.py
2) Some imported modules are not available as they are created during
the build process and consequently 2to3 is unable to handle them
correctly. Files that import those modules need a bit of extra work.
The affected files are:
* core/__init__.py,
* core/numeric.py,
* core/_internal.py,
* core/arrayprint.py,
* core/fromnumeric.py,
* numpy/__init__.py,
* lib/npyio.py,
* lib/function_base.py,
* fft/fftpack.py,
* random/__init__.py
Closes #3172
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These havn't been deprecated, but I think few have heard of them, much
less used them. Before this change, running setup.py without any
arguments would result in interactive help. This patch removes that
interactive help and lets setup print its usual list of commands and
options.
All the script uses of the numpy/distutils/fcompiler compilers look
quite broken to me, but I have tried to maintain compatibility with the
earlier version of gnu.py after the removal of `raw_input`.
These removals solve an incompatibility between Python3 and Python2.
The current interactive setup help uses `raw_input`, which has been
removed in python3 and replaced by `input`. However, python2 already
has an `input` that has different semantics. Rather than deal with
this, I think it simpler to keep both `raw_input` and `input` out of
numpy.
Closes #3063
Closes #3079
|
|
|
|
|
|
|
|
| |
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.
|
|
|
| |
Use spaces instead of tabs
|
|
|
|
|
| |
The basic idea here is to compare arch flags the Fortran compiler supports with
the ones the C compiler receives, and throw out any superfluous ones.
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to David Warde-Farley. Fixes #1399.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Gfortran does not append a leading underscore anymore, so the
-fno-leading-underscore is not necessary anymore.
|
| |
|
|
|
|
|
|
|
| |
We don't link the gfortran runtime when built with MS compilers: there are some
incompatibilities between libgfortran and dependent libraries (mingwex, etc..)
and the MS C runtime. Instead, we will implement the needed function from
libgfortran and compile it with MS compiler, with the MS C runtime.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Arch flags were detected and set for both linkers and compiler. Since they both
used the compiler_f90 as the underlying command, arch flags were added twice to
the compiler command for universal detection, which rendered the verbose output
of gfortran useless.
|
|
|
|
| |
Granger].
|
| |
|
|
|
|
| |
use fortran and are built with gfortran+MS compiler.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
are too fragile, and are more likely not that useful anyway.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
handle spaces in program path. This fixes building
numpy/scipy on Windows using mingw32 g77 with full
path=C:\Program Files\MinGW\g77.exe.
|
|
|
|
| |
- 'g77' for gnu, 'gfortran' for gnu95, 'ifort' for intel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove FCompiler.get_version_cmd, FCompiler.get_flags_version,
FCompiler.get_linker_so_cmd, and FCompiler.get_linker_exe_cmd;
subclasses should do this in FCompiler.update_executables()
* FCompiler attributes .compiler_f77, .version_cmd, etc., are now
properties that read from the .executables dictionary.
* Update intel.py and absoft.py for above
* Add extra asserts for defensive programming. Most of our problems
here seem to come from bad values being generated, and the error not
being caught until later.
* must call FCompiler.customize() before FCompiler.get_version();
command/build_ext.py and command/config.py updated
* verify that commands make sense earlier -- must be None or
lists of strings
Also,
* add IA-32 as another pattern to search for in 32-bit Intel
compiler version.
* minor formatting
* add debugging helpers to environment.py:EnvironmentConfig class
|
| |
|