summaryrefslogtreecommitdiff
path: root/numpy/distutils/misc_util.py
Commit message (Collapse)AuthorAgeFilesLines
* BUG: fix config where PATH isn't set on win32xoviat2018-01-071-1/+2
|
* Merge branch 'master' into config-load-dllxoviat2017-12-301-2/+7
|\
| * BUG: distutils: use correct top-level package namexoviat2017-12-241-1/+1
| | | | | | | | | | | | | | | | Here, we align the extra-dll name to the one that auditwheel uses, and we handle the case where 1) there is more than one root package and 2) the root package name is different than the distribution name
| * ENH: distutils: set NPY_NUM_BUILD_JOBS to cpu_countxoviat2017-12-171-1/+6
| |
* | BUG: distutils: use AddDllDirectory where availablexoviat2017-12-171-2/+17
|/ | | | | | This should reduce some DLL hell scenarios, namely scipy/scipy#8064. partial credits to @carlkl
* Make system_info output reproducible (#9652)Chris Lamb2017-09-051-1/+1
| | | | | | | | | | | Whilst working on the Reproducible Builds effort [0], we noticed that python-numpy generates output that is not reproducible. This affects "downstream" packages such as numexpr. This occurs as it encodes the absolute pathname into the generated file. [0] https://reproducible-builds.org/ Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
* distutils: handle unlinkable object files in build_clib/build_ext, not gnuPauli Virtanen2017-09-021-19/+5
| | | | | | | | | | | | | | | | | | | | | | Add concept of unlinkable Fortran object files on the level of build_clib/build_ext. Make build_clib generate fake static libs when unlinkable object files are present, postponing the actual linkage to build_ext. This enables MSVC+gfortran DLL chaining to only involve those DLLs that are actually necessary for each .pyd file, rather than linking everything in to every file. Linking everything to everywhere has issues due to potential symbol clashes and the fact that library build order is unspecified. Record shared_libs on disk instead of in system_info. This is necessary for partial builds -- it is not guaranteed the compiler is actually called for all of the DLL files. Remove magic from openblas msvc detection. That this worked previously relied on the side effect that the generated openblas DLL would be added to shared_libs, and then being linked to all generated outputs.
* distutils: gnu: patch fcompilexoviat2017-09-021-0/+21
| | | | | | | | | | 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.
* MAINT: Remove unnecessary importsSrinivas Reddy Thatiparthy2017-08-261-4/+0
| | | | - Now that `set` datastructure has been added the `builtin` module, we do not need to explicitly import from `sets` module
* DOC: BLD: fix lots of Sphinx warnings/errors.Ralf Gommers2017-06-101-13/+15
|
* BUG: KeyboardInterrupt is swallowed all over the placeEric Wieser2017-06-031-3/+3
| | | | Bare except is very rarely the right thing
* BUG: check compiler flags to determine the need for a rebuildJulian Taylor2017-05-021-0/+12
| | | | | | | Some projects compile an extension multiple times with different flags. As it is not intended to get the extension name from the compiler object, store the last used flags in the dependency file and also check if they match the flags of the current build.
* DEP: Fix escaped string characters deprecated in Python 3.6.Charles Harris2016-12-141-1/+1
| | | | | | | 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.
* Merge pull request #8355 from rolk/8355_mingw_py35Charles Harris2016-12-121-11/+26
|\ | | | | Fix building extensions with MinGW for Python 3.5
| * ENH: Recognize C RTL used by Py3.5 on WinRoland Kaufmann2016-12-091-1/+5
| | | | | | | | | | | | | | | | Python 3.5 is built against vcruntime140 instead of msvcrXXX, and the internal version number reported by the version string is 1900. This cause building extensions to fail, complaining about a missing compiler. This patch adds the latest runtime library to the list.
| * MAINT: Isolate hardcoded RTL name and vers. on Win.Roland Kaufmann2016-12-091-11/+22
| | | | | | | | | | | | | | | | | | | | | | There are three concepts in the C runtime library used by Python on Windows (from the Microsoft Visual C compiler); the internal build number (e.g. 0x1600), the major version of the runtime (e.g. 10.0), and the name of the link library of the runtime (e.g. msvcr100). This patch separates getting these three values into separate functions so that other code can be relieved of parsing the string return value of the msvc_runtime_library function.
* | MAINT: Other cleanup Python < 2.7 and Python3 < 3.4Alexandr Shadchin2016-12-091-18/+1
|/
* ENH: Add stacklevel to all (or almost all) our function callsSebastian Berg2016-09-021-1/+1
|
* DOC: Corrected allowed keywords in add_(installed_)libraryOleksandr Pavlyk2016-08-261-4/+4
| | | | | | | | | | | Docstring listed extra_f77_compiler_args and extra_f90_compiler_args as allowed keywords, but per command/build_clib.py, lines 193-194 the recognized keywords are in fact extra_f77_compile_args and extra_f90_compile_args. The keyword extra_compiler_args, although non-confirmant both for fortran keywords and to the keywords of add_extension, is consistent with the implementation (see line 200 of build_clib.py).
* Merge pull request #7791 from bertrand-l/feature/f2py-issues-7683Charles Harris2016-07-181-7/+5
|\ | | | | f2py.compile issues (#7683)
| * MAINT,DOC: add to compat.py3k a function to load modules. Fix some doc for ↵bertrand2016-07-171-7/+5
| | | | | | | | f2py.compile (issue #7683)
* | numpy/distutils/misc_util.py fix for #7809: check that _tmpdirs is not NoneMario Emmenlauer2016-07-101-5/+6
|/
* BUG: fix issue on OS X with Python 3.x where npymath.ini was not installed.Ralf Gommers2016-06-121-6/+6
| | | | | Closes gh-7707. Happened for `pip install .` or another location (including a remote git repo).
* BUG: make distutils.misc_util.is_string recognize unicode.Ralf Gommers2016-01-161-1/+2
| | | | | | This was triggered by the numpy version string (which is unicde) being included in metadata. This could also solve other problems for external users of numpy.distutils.
* BUG: fix removing tempdirs created during buildJulian Taylor2015-11-171-17/+18
| | | | | | | Old code used the thread local storage wrong and also only deleted the directories created for the last parallel build section as the exit handler only knows about one of the directories. Fix by storing all created tempdirs to delete at exit.
* Revert "Merge pull request #6354 from mingwpy/mingwpy"Charles Harris2015-10-201-15/+2
| | | | | | | | | 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.
* BLD: mingwpy fixescarlkl2015-09-241-2/+15
|
* MAINT: adapt parallel build option names to python3.5Julian Taylor2015-07-161-5/+5
| | | | python3.5 uses --parallel instead of --jobs
* BUG: missing default None values in getattr(...)Alistair Muldal2014-11-191-3/+3
|
* ENH: support parallel compilation of extensionsJulian Taylor2014-10-281-7/+42
| | | | | | | | | | | | | | Allow extensions using numpy.distutils to compile in parallel. By passing `--jobs=n` or `-j n` to `setup.py build` the compilation of extensions is now performed in `n` parallel processes. Additionally the environment variable NPY_NUM_BUILD_JOBS is used as the default value, if its unset the default is serial compilation. The parallelization is limited to within the files of an extension, so only numpy multiarraymodule really profits but its still a nice improvement when you have 2-4 cores. Unfortunately Cython will not profit at all as it tends to build one module per file.
* Revert "Merge pull request #4421 from meltingwax/meltingwax/4382"Daniel da Silva2014-03-051-7/+1
| | | | Caused SciPy tests to fail when built with this NumPy.
* BUG: Fix support for builds in dirs with whitespaceDaniel da Silva2014-03-051-1/+7
| | | | | | Add escaping and quoting of dirs and enabled POSIX support in lexer. Closes #4382.
* DEP, MAINT: Remove references to numeric and numarray.Charles Harris2013-09-231-4/+0
| | | | | This covers those locations that either import or build numarray or numeric.
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-120/+120
| | | | | | | 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.
* MAINT: Remove msvc_on_amd64 functionChristoph Gohlke2013-05-221-11/+0
| | | | This function is no longer required for building with msvc on AMD64
* ENH: add possibility to add define_macros to extensionsJulian Taylor2013-05-091-1/+19
|
* BUG: hardcode some known shared library extensionsJulian Taylor2013-04-281-5/+23
| | | | | | | | the configuration variables are not a reliable mean to get the shared library extension. darwin, windows and debug linux are wrong in these variables. SHLIB_SUFFIX is also wrong as of python 3.3.1 closes #3057
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-7/+7
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* Merge pull request #3191 from charris/2to3-apply-imports-fixerCharles Harris2013-04-061-2/+6
|\ | | | | 2to3: Apply `imports` fixer.
| * 2to3: Apply `imports` fixer.Charles Harris2013-04-021-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `imports` fixer deals with the standard packages that have been renamed, removed, or methods that have moved. cPickle -- removed, use pickle commands -- removed, getoutput, getstatusoutput moved to subprocess urlparse -- removed, urlparse moved to urllib.parse cStringIO -- removed, use StringIO or io.StringIO copy_reg -- renamed copyreg _winreg -- renamed winreg ConfigParser -- renamed configparser __builtin__ -- renamed builtins In the case of `cPickle`, it is imported as `pickle` when python < 3 and performance may be a consideration, but otherwise plain old `pickle` is used. Dealing with `StringIO` is a bit tricky. There is an `io.StringIO` function in the `io` module, available since Python 2.6, but it expects unicode whereas `StringIO.StringIO` expects ascii. The Python 3 equivalent is then `io.BytesIO`. What I have done here is used BytesIO for anything that is emulating a file for testing purposes. That is more explicit than using a redefined StringIO as was done before we dropped support for Python 2.4 and 2.5. Closes #3180.
* | Merge pull request #460 from endolith/regex_formattingCharles Harris2013-04-031-30/+30
|\ \ | |/ |/| DOC: Formatting fixes using regex
| * DOC: Used regex to find colons missing spaces which render wrong online, ↵endolith2013-03-191-30/+30
| | | | | | | | also other spacing or formatting mistakes
* | 2to3: Use absolute imports.Charles Harris2013-03-281-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: Replace xrange by range and use list(range(...)) where neededCharles Harris2013-03-271-1/+1
|/ | | | | | | | | | | | | | | In python3 range is an iterator and `xrange` has been removed. This has two consequence for code: 1) Where a list is needed `list(range(...))` must be used. 2) `xrange` must be replaced by `range` Both of these changes also work in python2 and this patch makes both. There are three places fixed that do not need it, but I left them in so that the result would be `xrange` clean. Closes #3092
* 2to3: Remove xreadlines and replace f.readlines() by f where valid.Charles Harris2013-03-051-3/+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: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+2
| | | | | | | | 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.
* Merge pull request #3056 from charris/2to3-filterCharles Harris2013-03-011-4/+4
|\ | | | | 2to3: Apply `filter` fixes. Closes #3053.
| * REF: Replace filters with list comprehensions.Charles Harris2013-02-281-4/+4
| | | | | | | | | | | | 2to3 does a lot of list(filter(...)) sort of thing which can be avoided by using list comprehensions instead of filters. This also seems to clarify the code to a considerable degree.
| * 2to3: Apply `filter` fixes. Closes #3053.Charles Harris2013-02-281-4/+4
| | | | | | | | | | Generally, this involves using list comprehension, or explicit list construction as `filter` is an iterator in Python 3.
* | 2to3: Apply `funcattrs` fixer. Closes #3058.Charles Harris2013-02-281-1/+1
|/ | | | | This replaces the `b.func_xxxx` with newer `__xxxx__` attribute names For example, `f.__name__` replaces `f.func_name`
View Lorry Controller Status