| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
This allows mingw's gfortran to work with MSVC. DLLs are
autogenerated using heuristics that should work with most
cases. In addition, a libopenblas DLL is compiled from
the static lib for use with MSVC.
All generated DLLs have randomized names so that no clashes
will occur.
|
|
|
|
| |
- Now that `set` datastructure has been added the `builtin` module, we do not need to explicitly import from `sets` module
|
|
|
|
|
| |
Note that this was discussed extensively in gh-7287, but removing
this -xhost flag was missed in the PR that closed that issue.
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes two problems:
* c compilers do not have a find_executables method.
* get_version return a LooseVersion instance, not string.
Closes #9278.
[ci skip]
|
|
|
|
|
|
|
|
|
| |
The '-openmp' option was deprecated in Intel version 15 and removed
in version 18. The replacement is '-qopenmp'.
Closes #8941.
[skip ci]
|
|
|
|
|
|
|
| |
In Python 3.6 a number of escape sequences that were previously accepted
-- for instance "\(" that was translated to "\\(" -- are deprecated. To
retain the previous behavior either raw strings must be used or the
backslash must be properly escaped itself.
|
|
|
|
|
|
| |
``-Wl,rpath=`` is Linux-specific, OS X needs a comma.
This addresses gh-6486, which was already closed but not actually addressed.
|
|
|
|
|
|
|
| |
The error snuk in with some other file closing fixes and found by
Warren Weckesser.
Closes gh-8013
|
| |
|
|
|
|
|
| |
The PIPE in the tests caused a ResourceWarning during testing in
python 3.
|
| |
|
|
|
|
|
|
|
| |
The consensus seems to be that hardcoding SSE4.2 results in poor code
for architectures lacking the feature.
Closes #7287.
|
| |
|
|
|
|
| |
Closes gh-647.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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 cda64938eb150b1af6677db4754da3be5fd7e483, reversing
changes made to 8cb3ec6ab804f594daf553e53e7cf7478656bebd.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
behavior affect at least python 3.5 and SciPy build and build failed.
During initialization <python>.distutils.MSVCCompiler replace Intel
environment('include' and 'lib' paths). This fix decorate 'initialize'
function in MSVCCompiler and extend 'lib' and 'include' environment
variables. Changed compilation keys: generate optimized code
specialized for Intel processors with SSE4.2 support.
|
|
|
|
| |
Reported in gh-6095.
|
|
|
|
| |
See https://software.intel.com/en-us/node/524904. Reported in gh-6095.
|
|\
| |
| | |
BLD, ENH: Reading of extra flags from site.cfg to extend flexibility
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This bug-fix only applies for non gnu-compilers.
The fortran compilers in numpy inherited the Ccompier class
which had the runtime library directories NotImplemented.
Hence the compilers need to define their own runtime library
path.
I have added that information to the intel/pgi/sun compilers.
The rest are either already implemented or I do not know them.
I have tested the bug-fix with intel compilers of numpy AND the
subsequent installation of scipy (which relies on the fortran
compilers). Hence this bug will only occur when linking with
the fortran compilers.
|
| | |
|
|\ \
| | |
| | | |
BLD: fix gfortran version check, and make distutils.test() work
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
Break long lines.
Spaces around operators.
Remove dead code.
|
|/ |
|
|
|
|
|
| |
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.
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
The "-Wl,-undefined,dynamic_lookup" flag is enough to make things work
with OS X bundles. On the mailing list an issue was reported with
Anaconda (non-framework build) where f2py was picking up the system framework
Python instead of the Anaconda one.
Thanks to Robert Kern for explaining how to fix this.
|
|
|
| |
Fixes scipy test failures.
|
|
|
|
| |
Caused SciPy tests to fail when built with this NumPy.
|
|
|
|
|
|
| |
Add escaping and quoting of dirs and enabled POSIX support in lexer.
Closes #4382.
|
|
|
|
|
|
|
|
| |
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
|
|
|
| |
The uppercase source extension '.FOR' is also commonly used.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The idioms fixer makes the following replacements.
1) int <- bool
2) comparison or identity of types <- isinstance
3) a.sort() <- sorted(a)
There were two problems that needed to be dealt with after the
application of the fixer. First, the replacement of comparison or
identity of types by isinstance was not always correct. The isinstance
function returns true for subtypes whereas many of the places where the
fixer made a substitution needed to check for exact type equality.
Second, the sorted function was applied to arrays, but because it treats
them as iterators and constructs a sorted list from the result, that is
the wrong thing to do.
Closes #3062.
|
| |
|
|
|
|
|
|
| |
Most of these are places where an iterator will work as well as a
list, but two fix places where `iterkeys` was introduced which is
a bug.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Python3 `dict.items()`, `dict.keys()`, and `dict.values()` are
iterators. This causes problems when a list is needed so the 2to3 fixer
explicitly constructs a list when is finds on of those functions.
However, that is usually not necessary, so a lot of the work here has
been cleaning up those places where the fix is not needed. The big
exception to that is the `numpy/f2py/crackfortran.py` file. The code
there makes extensive use of loops that modify the contents of the
dictionary being looped through, which raises an error. That together
with the obscurity of the code in that file made it safest to let the
`dict` fixer do its worst.
Closes #3050.
|
|
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|