| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | |
| | |
| | |
| | | |
importing MSVC
|
| | | |
|
|\ \ \
| |/ /
|/| | |
BLD: Remove fallback CBLAS detection looking for cblas.h.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This raises DistutilsPlatformError when mingw32 is used as the default
ccompiler is msvc. That is fixable, but does not seem worth the trouble
as looking for a cblas.h file for a last effort to detect cblas seems a
bit fragile in any case. I think it is better handled elsewhere on a
case by case basis in combination with site.cfg.
|
|/ /
| |
| | |
Warns on OS X with MacPorts Python because it doesn't recognize clang. There isn't actually a problem, though, as distutils.sysconfig has done its job just fine. Proposed fix.
|
| | |
|
|/
|
|
|
|
|
|
| |
- Fix an incorrect import
- Enable C99 complex support (Qstd=c99)
- Don't use MSVC complex types for Intel compilers
Thanks to Intel for this patch (contact: Yolanda Chen).
|
| |
|
| |
|
|
|
| |
Fixes test_system_info.TestSystemInfoReading.test_compile1 failure on Windows
|
|\
| |
| | |
Don't pass un-encodable env to spawn
|
| | |
|
| | |
|
|\ \
| | |
| | | |
BUG: Fix handling of dependencies between libraries
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
compiling with numpy.distutils. For example, something like this will now
work as a configuration function:
def configuration():
config = Configuration()
config.add_library('mylib1', sources=['mylib1.f'])
config.add_library('mylib2', sources=['mylib2.f'], libraries=['mylib1'])
config.add_extension('pymodule', sources=['pymodule.c'],
libraries=['mylib2'])
return config
Arbitrary handling of dependencies between libraries is still not
supported, but this should make some basic cases work properly.
|
| |/
|/| |
|
|/
|
|
| |
python3.5 uses --parallel instead of --jobs
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of these fixes involve putting blank lines around
.. versionadded:: x.x.x
and
.. deprecated:: x.x.x
Some of the examples were also fixed.
|
|
|
|
| |
Deprecated functions in numpy/distutils/command/config.py.
|
|
|
|
|
| |
Was in numpy/distutils/exec_command.py.
Update 1.10-notes.rst.
|
|
|
|
|
|
| |
This is to make it easier to find and remove deprecated features.
It would be a good idea if all deprecations were made with similar
comments.
|
|\
| |
| | |
MAINT: can't find Python.h when build_ext --include-dirs is set
|
| |
| |
| |
| |
| | |
Ensure that build_ext.include_dirs is the same physical list as
build_ext.distribution.include_dirs.
|
|/
|
|
|
|
|
|
| |
Thanks to the presence of
from __future__ import absolute_import
we don't need different code paths for Python 2/3.
|
|
|
|
| |
Snuck in in gh-5694.
|
|\
| |
| | |
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.
|
| |
| |
| |
| | |
Changed all lists to strings
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changed self.assert* to assert_ instances through numpys
own testing utilities.
Fixes for the rst document.
Removed unnecessary import statements in the test.
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Addition to the distutils module to be able
to read in more optional arguments and flags
from the site.cfg file.
Currently are these additional options read:
runtime_library_dirs:
It allows users to set the runtime
library directories so that LD_LIBRARY_PATH can be ignored.
This has the same format as the library_dirs option.
extra_compile_args:
This allows the user to add specific compiler
flags when compiling sources.
There will be no formatting/checking of these additional compile
flags, the compiler should complain if something is wrong.
extra_link_args:
This allows the user to add specific linker flags
when linking the .so objects.
There will be no formatting/checking of these additional compile
flags, the linker should complain if something is wrong.
When the config is runned it automatically prints out the
read in information, thereby allowing the user to see
what has been set and what has not.
Tested with and without flags to check that it builds correctly.
|
| | |
|
| |
| |
| |
| | |
Thanks to Intel for contributing this patch. Contact: Yolanda Chen.
|
|\ \
| | |
| | | |
BLD: fix gfortran version check, and make distutils.test() work
|
| | |
| | |
| | |
| | | |
Without this fix, _INSTALLED is False and distutils.test() is not available.
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
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.
|
|
|
|
| |
the output. (instead of a subsequent decode step).
|
| |
|
| |
|
| |
|