summaryrefslogtreecommitdiff
path: root/numpy/distutils/environment.py
Commit message (Collapse)AuthorAgeFilesLines
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | 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-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.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.
* STY: Replace remaining old style classes with classes subclassing object.Charles Harris2011-04-051-1/+1
|
* Fix print statements in numpy.distutils.environmentDavid Cournapeau2009-12-031-4/+4
|
* In site.cfg, change DEFAULT section to ALL to accommodate building on Python ↵Stefan van der Walt2008-03-191-1/+1
| | | | 2.6.
* Better version handling in fcompilercookedm2007-06-151-0/+19
| | | | | | | | | | | | | | | | | | | | | | * Remove FCompiler.get_version_cmd, FCompiler.get_flags_version, FCompiler.get_linker_so_cmd, and FCompiler.get_linker_exe_cmd; subclasses should do this in FCompiler.update_executables() * FCompiler attributes .compiler_f77, .version_cmd, etc., are now properties that read from the .executables dictionary. * Update intel.py and absoft.py for above * Add extra asserts for defensive programming. Most of our problems here seem to come from bad values being generated, and the error not being caught until later. * must call FCompiler.customize() before FCompiler.get_version(); command/build_ext.py and command/config.py updated * verify that commands make sense earlier -- must be None or lists of strings Also, * add IA-32 as another pattern to search for in 32-bit Intel compiler version. * minor formatting * add debugging helpers to environment.py:EnvironmentConfig class
* Add a convert procedure to the flag-getting logic in fcompiler and environment.cookedm2007-05-291-1/+3
| | | | | Otherwise, flags (for instance) from environment variables or setup.cfg are are strings, where lists are expected.
* merge from distutils-revamp branch (step 2)cookedm2007-05-251-0/+49
- fcompiler changes. All flags, executables, etc., should be overridable by the user with config_fc (either command line or setup.cfg) or by environment variables
View Lorry Controller Status