summaryrefslogtreecommitdiff
path: root/numpy/distutils/tests
Commit message (Collapse)AuthorAgeFilesLines
* Remove redundant codeIsuru Fernando2018-07-071-2/+0
|
* Use monkeypatch's setenv, getenvIsuru Fernando2018-07-071-8/+7
|
* Test distutils flags appendingIsuru Fernando2018-07-071-0/+47
|
* MAINT: Remove all uses of run_module_suite.Charles Harris2018-04-068-45/+10
| | | | | That function is nose specific and has not worked since `__init__` files were added to the tests directories.
* TST: Switch to using pytest markersCharles Harris2018-04-041-4/+6
| | | | | | | | | | | Use standard pytest markers everywhere in the numpy tests. At this point there should be no nose dependency. However, nose is required to test the legacy decorators if so desired. At this point, numpy test cannot be run in the way with runtests, rather installed numpy can be tested with `pytest --pyargs numpy` as long as that is not run from the repo. Run it from the tools directory or some such.
* MAINT: Remove use of unittest in NumPy tests.xoviat2018-03-211-1/+1
| | | | | | | | | | | | | | | | This removes a few left over uses of unittest. The main changes apart from removal of Test case are: * `setUp` replaced by nose and pytest compatible `setup` * `tearDown` replaced by nose and pytest compatible `teardown` * `assertRaises` replaced by `assert_raises` * `assertEqual` replaced by `assert_equal` The last two are in `numpy/testings/tests/test_utils.py`, so may seem a but circular, but at least are limited to those two functions. The use of `setup` and `teardown`, can be fixed up with the pytest equivalents after we have switched to pytest.
* BUG: distutils: Remove named templates from the output.Warren Weckesser2018-03-101-0/+48
| | | | | | | The code now does not copy the named templates found outside a function or subroutine to the output file. Fixes gh-10712.
* MAINT: distutils: trivial cleanupsxoviat2017-11-061-7/+4
|
* MAINT: made sure both compiler strings are included in testAndrew Lawson2017-10-231-11/+10
|
* TST: Improved tests for nag fortran compilerAndrew Lawson2017-10-201-12/+15
|
* ENH: Added compatability for the NAG Fortran compiler, nagforAndrew Lawson2017-10-191-0/+27
|
* Merge pull request #9645 from xoviat/appveyorCharles Harris2017-09-301-1/+1
|\ | | | | ENH: enable OpenBLAS on windows.
| * TST: fix failures:xoviat2017-09-041-1/+1
| | | | | | | | | | | | 1. fail tests related to DLL load failure as they were previously untested. 2. fix have_compiler to return false on old compilers 3. xfail some tests that were not working on old Python versions.
* | BUG: adjust gfortran version search regexJonathan Helmus2017-09-201-1/+2
|/ | | | | | | 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, MAINT: Add `__init__.py` files to tests directories.Charles Harris2017-08-061-0/+0
| | | | | | | | This allows pytest to run with duplicate test file names. Note that `python <path-to-test-file>` no longer works with this change, nor will a simple `pytest numpy`, because numpy is imported from the numpy repository. However, `python runtests.py` and `>>> numpy.test()` are still available.
* TST: Remove unittest dependencies in numpy/distutils/testsCharles Harris2017-07-176-82/+84
| | | | Also rename some classes that should not begin 'Test'.
* MAINT: Rearrange files in numpy/testing module.Charles Harris2017-07-041-5/+6
| | | | | | | | | | | | | | | | | The aim here is to separate out the nose dependent files prior to adding pytest support. This could be done by adding new files to the general numpy/testing directory, but I felt that it was to have the relevant files separated out as it makes it easier to completely remove nose dependencies when needed. Many places were accessing submodules in numpy/testing directly, and in some cases incorrectly. That presented a backwards compatibility problem. The solution adapted here is to have "dummy" files whose contents will depend on whether of not pytest is active. That way the module looks the same as before from the outside. In the case of numpy itself, direct accesses have been fixed. Having proper `__all__` lists in the submodules helped in that.
* BUG: KeyboardInterrupt is swallowed all over the placeEric Wieser2017-06-031-3/+3
| | | | Bare except is very rarely the right thing
* TST: fix test_basic failure on WindowsChristoph Gohlke2017-05-111-1/+1
| | | Echo is a command in the Windows command interpreter
* ENH: automatically determine compile dependenciesJulian Taylor2017-04-101-1/+2
| | | | | Use these dependencies to avoid unnecessary recompilations of unchanged files.
* TST: Respect compiler customizationsMarvin Schmidt2017-03-301-0/+3
| | | | | Without calling `compiler.customize(None)` customizations using environment variables like CC won't be honoured
* TST: move exec_command tests out of the file itselfJulian Taylor2017-03-241-0/+127
|
* MAINT: Remove shebang from test modulesSami Salonen2017-01-151-1/+0
|
* MAINT: Fix ResourceWarning new in Python 3.6.Charles Harris2016-10-191-0/+1
| | | | | | | | | In Python 2.6 the process destructor emits a ResourceWarning if the process has not terminated when destruction occurs. Fix by calling the wait method before return. The Popen class may be used as a context manager in Python 3.2+, unfortunately that does not include 2.7.
* MAINT: Close some filehandlers and PIPEs after being doneSebastian Berg2016-09-021-1/+3
| | | | | The PIPE in the tests caused a ResourceWarning during testing in python 3.
* BUG: fix issue on OS X with Python 3.x where npymath.ini was not installed.Ralf Gommers2016-06-121-1/+8
| | | | | Closes gh-7707. Happened for `pip install .` or another location (including a remote git repo).
* BUG: allow graceful recovery for no compilerMatthew Brett2016-04-141-6/+30
| | | | | | | | | | If there is no compiler on Linux, the error we were getting was CompileError rather than the OSError the test was expecting. This had the nasty side-effect of leaving us in a deleted temporary directory, causing later test failures. Try a check to see if we have a compiler and skip otherwise.
* MAINT: remove unused f2py and SWIG tests from numpy.distutils.Ralf Gommers2016-01-0623-291/+0
|
* MAINT: remove outdated Pyrex support from distutils (as far as possible).Ralf Gommers2016-01-065-52/+0
|
* MAINT: Simplify some tests using temppath context manager.Charles Harris2015-12-261-33/+21
| | | | | | | | | | | | | | | | | | | | | | | | This replaces code of the pattern ``` fd, name = tempfile.mkstemp(...) os.close(fd) try: do stuff with name finally: os.remove(name) ``` with ``` with temppath() as name: do stuff with name ``` A few more complicated cases are also handled. The remains some particularly gnarly code the could probably be refactored to use temppath, but that is a more demanding project.
* MAINT: Dictionary litteralRémy Léone2015-11-071-9/+8
|
* TST: use os.pathsep to separate library directoriesChristoph Gohlke2015-08-011-2/+3
|
* TST: skip gcc specific test when using msvcChristoph Gohlke2015-08-011-0/+2
|
* TST: alternatively assert existence of msvc .obj filesChristoph Gohlke2015-08-011-1/+2
| | | Fixes test_system_info.TestSystemInfoReading.test_compile1 failure on Windows
* STY: PEP8 and pyflakes fixes for numpy/distutils.Charles Harris2015-07-2510-36/+40
|
* Merge pull request #5597 from zerothi/ENH-distutilsCharles Harris2015-04-241-0/+203
|\ | | | | BLD, ENH: Reading of extra flags from site.cfg to extend flexibility
| * BUG: Had thought the defaults where made of lists, it is simply a str.Nick Papior Andersen2015-02-261-7/+7
| | | | | | | | Changed all lists to strings
| * ENH: rpath and runtime_library_dirs equivalentNick Papior Andersen2015-02-261-1/+5
| | | | | | | | | | | | | | | | | | The original distutils assumes runtime_library_dirs to be located in rpath, however, the internal structures assumes the keyword to be runtime_library_dirs. For now numpy.distutils handles both equivalently. The test has been updated to also test the rpath solution.
| * BUG: Python3 fixNick Papior Andersen2015-02-251-4/+5
| | | | | | | | | | | | Direct writing to files is not the same for 2vs3. Hence we now close the file handle, re-open it and write using the file.
| * BUG: PEP correctionsNick Papior Andersen2015-02-251-71/+79
| | | | | | | | | | | | | | | | | | | | | | More corrections pointed out by Ralf Changed the get_standard_file to a fully temporary file. This means that the __init__ diverges a bit from the system_info object. However, it only has to do with the setup for the test. All internal things regarding the object have not been altered. I have checked on my box that all files/directories are removed.
| * BUG: PEP corrections and streamlined with numpy dev lineNick Papior Andersen2015-02-251-41/+23
| | | | | | | | | | | | | | | | | | Changed self.assert* to assert_ instances through numpys own testing utilities. Fixes for the rst document. Removed unnecessary import statements in the test.
| * BUG: Trying to fix travis buildsNick Papior Andersen2015-02-241-5/+4
| | | | | | | | | | | | | | The error of getcwd on 2.6 was due to previous fault. We should not request include_dirs as they are not provided. For python 3 I forgot the top ascii writing.
| * BUG: Trying to fix travis buildsNick Papior Andersen2015-02-241-30/+36
| | | | | | | | | | | | | | The test on Travis does not allow getcwd on python 2.6 The test for python 3+ already is in unicode, hence the str representation was wrong.
| * ENH: Added tests to the extra options read inNick Papior Andersen2015-02-241-0/+203
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A simple test (distutils/testing/test_system_info.py) to check that the options are read in correctly has been added. This test has a few faults: A) It does not allow strict library checks as that can be _very_ system dependent. B) It compiles some simple C-programs but does currently not link them to a shared library. C) As such the test does not check that the flags are actually used. To circumvent this one should: A) Make a library of the compiled sources. B) Check that a runtime_library_dirs is working by checking with ldd C) Make a preprocessor flag to check the output of two commands which should differ according to the flags in each block I am not too much into the distutils compiler suite. So I have not endeavoured on this path. - The current test shows that the flags are read in by the standard system_info object and can thus be considered a "stable" solution. - Added note of the 1.10 release schedule. - Corrected the site.cfg.example, added runtime_library_dirs to the OpenBLAS example where it seems appropriate. - Bugfix for the site.cfg.example (the [DEFAULT] block should be name [ALL]) This might have lead to some confusion, but many of the libraries are linked explicitly by their own sections, hence it might not have been caught.
* | BLD: distutils: more robust gfortran version checking. Closes gh-5768.Ralf Gommers2015-04-191-1/+7
| |
* | MAINT: distutils: fix gfortran version check when gfortran emits warnings.Ralf Gommers2015-03-071-1/+6
|/
* BLD: Change Fortran version flag and string checkRyan Nelson2014-12-011-6/+2
| | | | | | | 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.
* Revert "Merge pull request #4421 from meltingwax/meltingwax/4382"Daniel da Silva2014-03-051-66/+9
| | | | Caused SciPy tests to fail when built with this NumPy.
* BUG: Fix support for builds in dirs with whitespaceDaniel da Silva2014-03-051-9/+66
| | | | | | Add escaping and quoting of dirs and enabled POSIX support in lexer. Closes #4382.
* STY: Giant comma spacing fixup.Charles Harris2013-08-1811-46/+46
| | | | | | | 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.