delta/python-packages/numpy.git/numpy/distutils/tests/test_fcompiler_gnu.py, branch pr/12889

MAINT: Remove all uses of run_module_suite.

2018-04-07T00:20:56+00:00

That function is nose specific and has not worked since `__init__` files
were added to the tests directories.

BUG: adjust gfortran version search regex

2017-09-20T20:35:48+00:00

Adjust the gfortran regex to require a '.' to be present in the version number.
This avoids matching a hash or text containing a '-' such as the version string
from the compilers produced by crosstool-NG.  For example:
GNU Fortran (crosstool-NG 8a21ab48) 7.2.0

TST: Remove unittest dependencies in numpy/distutils/tests

2017-07-17T17:58:20+00:00

Also rename some classes that should not begin 'Test'.

BLD: distutils: more robust gfortran version checking. Closes gh-5768.

2015-04-19T12:28:24+00:00

MAINT: distutils: fix gfortran version check when gfortran emits warnings.

2015-03-07T09:10:32+00:00

BLD: Change Fortran version flag and string check

2014-12-01T18:50:32+00:00

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.

BUG: Handle a version string from a custom-built mingw64.

2013-05-29T14:45:13+00:00

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.

2to3: Apply `print` fixer.

2013-04-06T19:25:26+00:00

Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.

Closes #3078.

2to3: Use absolute imports.

2013-03-28T14:43:26+00:00

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: Put `from future import division in every python file.

2013-03-01T18:22:47+00:00

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.