summaryrefslogtreecommitdiff
path: root/numpy/distutils/fcompiler
Commit message (Collapse)AuthorAgeFilesLines
* BUG: Handle a version string from a custom-built mingw64.mwtoews2013-05-291-1/+1
| | | | | | | | 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.
* MAINT: Apply 2to3 idioms fixer.Charles Harris2013-05-021-2/+1
| | | | | | | | | | | | | | | | | | | 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.
* ENH: remove obsolete ifort flags, ensure generated binaries work everywhere.David Cournapeau2013-04-231-14/+5
|
* MAINT: Fixup more dictionary fixer fixes.Charles Harris2013-04-071-2/+2
| | | | | | 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.
* 2to3: apply `dict` fixer.Charles Harris2013-04-061-2/+2
| | | | | | | | | | | | | | | 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.
* 2to3: Apply `print` fixer.Charles Harris2013-04-0616-19/+19
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Use absolute imports.Charles Harris2013-03-2816-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* 2to3: Remove xreadlines and replace f.readlines() by f where valid.Charles Harris2013-03-052-2/+2
| | | | | | | | | | An open file `f` has been an iterator since python2.3 and `f.xreadlines()` is no longer needed, so replace it with `f`. Also replace `f.readlines()` with `f` where an iterator will do. The replacement of `f.readlines()` is not critical because it is a list in both python2 and python3, but the code is a bit cleaner. Closes #3093
* 2to3:DEP: Remove interactive setup and gnu compiler configuration.Charles Harris2013-03-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | 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
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-0116-1/+26
| | | | | | | | 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.
* Style: use 4 spaces per indentation level as per PEP8cgohlke2012-09-161-26/+26
|
* Fix whitespace formattingcgohlke2012-09-161-1/+1
| | | Use spaces instead of tabs
* MAINT: update Intel Fortran compiler flags for the 21st century.Ralf Gommers2012-09-091-55/+16
| | | | | | Thanks to Intel for this contribution. Note that there's also an MKL application note which recommends these flags: http://software.intel.com/en-us/articles/numpyscipy-with-intel-mkl
* prefer gfortran over g77 and vendor compilers on OS X and LinuxAron Ahmadia2012-07-171-4/+4
|
* prefer gfortran (g95) over vendor compilers, g77 and g95 on OSX and Linux. ahmadia2012-06-281-8/+8
| | | Retain preference for g77 on Windows and vendor compilers on other platforms.
* BUG: '-framework Python' is not needed and can interfere.Robert Kern2012-05-311-1/+1
|
* BLD: Avoid repeatedly testing for the Fortran compiler when it is missingMark Wiebe2012-02-191-0/+8
|
* MAINT: update version match regexp for IBM AIX Fortran compilers.Carlos Valiente2011-12-051-1/+1
| | | | | | | | | | | The patched version correctly matches the output of ``xlf -qversion`` on my AIX platform: $ uname -a AIX c1t0101 3 5 00CF49B14C00 $ xlf -qversion IBM XL Fortran for AIX, V12.1 Version: 12.01.0000.0000 $
* ENH: Add 'pgfortran' as a valid compiler in the Portland Grouptim cera2011-10-231-10/+10
| | | | suite of fortran compilers. Adjust the version string command.
* ENH: Introduce new options extra_f77_compile_args and extra_f90_compile_args toPearu Peterson2011-08-201-1/+14
| | | | | | Configuration.add_extension. Configuration.add_library, and Extension. These options allow specifying extra compile options for compiling Fortran sources within a setup.py file.
* BUG: Revert commit that causes many tests not to run.Charles Harris2011-08-201-14/+1
| | | | | | Revert "Introduce new options extra_f77_compiler_args and extra_f90_compiler_args to Configuration.add_extension. Configuration.add_library, and Extension. These options allow specifying extra compile options for compiling Fortran sources within a setup.py file." This reverts commit 43862759384a86cb4a95e8adb4d39fa1522acb28.
* Introduce new options extra_f77_compiler_args and extra_f90_compiler_args to ↵Pearu Peterson2011-08-161-1/+14
| | | | Configuration.add_extension. Configuration.add_library, and Extension. These options allow specifying extra compile options for compiling Fortran sources within a setup.py file.
* BUG: deal with shared lib extension in a single place. Fix ctypes.load_library.rgommers2011-06-231-6/+5
| | | | | This is related to PEP 3149, tags in shared library extensions. Only applies to Linux (for now). See also #1749.
* BUG: numpy doesn't compile anymore with ifort using -O3, changing to -O1.Ralf Gommers2011-04-221-2/+2
| | | | Closes #1378. Thanks to Burkhard Neinhues and Christoph Gohlke.
* BUG: distutils: update HP compiler flags. Closes #1377.Ralf Gommers2011-03-301-3/+3
|
* BUG: distutils: change compile flag on AIX from -O5 to -O3. See #1261.Ralf Gommers2011-03-251-1/+1
|
* BUG: fix 64-bit Intel Fortran compiler detection. Closes #1448.rgommers2011-03-091-4/+4
|
* BUG: fix up shared library extension, which changed in Python 3.2. Closes #1749.rgommers2011-03-021-1/+4
|
* ENH: add support for the PathScale compilers on Linux. Closes #1043.rgommers2010-12-022-1/+37
| | | | Thanks to R. Perez.
* BUG: fix issue with incorrect Fortran arch flags. Closes #1399.rgommers2010-11-071-1/+31
| | | | | 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.
* BUG: on Windows the sysconfig module does not contain CFLAGS info.rgommers2010-10-171-1/+4
|
* UPDATE: gcc-4 series do not support -mno-cygwin option.Pearu Peterson2010-10-161-7/+11
|
* BF - get fortran arch flags from C arch flags if availableMatthew Brett2010-10-161-25/+11
|
* Added Portland Group compiler support for Darwin platform (thanks to Josef ↵Pearu Peterson2010-10-062-4/+23
| | | | Koller).
* ENH: Update absoft fortran flags for v11.0.Charles Harris2010-09-251-1/+3
|
* BUG: distutils: make is_free_format et al. not choke on non-ascii Fortran filesPauli Virtanen2010-09-111-3/+5
|
* BUG: Enable compiling Fortran code on OS X for ppc64 arch.rgommers2010-06-021-8/+8
| | | | Thanks to David Warde-Farley. Fixes #1399.
* BUG: Fix #1376, indentation problem.Travis Oliphant2010-02-041-2/+2
|
* Apply ifort.patch from ticket #1372 to allow Intel Fortran Compiler 11.1 to ↵Travis Oliphant2010-01-242-4/+17
| | | | be called by numpy.distutils.
* BUG: fix 1087, thanks to Leek for the fix.David Cournapeau2009-12-101-16/+17
|
* 3K: distutils: remove unnecessary non-ascii characters in intel.pyPauli Virtanen2009-12-061-8/+0
|
* 3K: distutils: ordering between None and str is undefined in Py3K, so ↵Pauli Virtanen2009-12-061-1/+4
| | | | fcompiler should raise CompilerNotFound when version is undefined
* 3K: distutils: there is no types.InstanceType in Py3, so don't use itPauli Virtanen2009-12-061-1/+2
|
* Py3k: Fix comparison when version is None.David Cournapeau2009-12-031-2/+5
|
* Fix version comparison when version is None.David Cournapeau2009-12-031-1/+1
|
* BUG: fix mixed tab/space indentation.David Cournapeau2009-12-031-10/+10
|
* Py3k: make fcompiler.compaq py3k-importable.David Cournapeau2009-12-031-5/+9
|
* Py3k: make fcompiler module py3k-importable.David Cournapeau2009-12-031-12/+16
|
* Fix print statements in fcompiler for python3.David Cournapeau2009-12-0315-25/+25
|
* Apply fix for sun compilation from beffa. Closes ticket #1248.Charles Harris2009-11-031-1/+1
|
View Lorry Controller Status