delta/python-packages/numpy.git - github.com: numpy/numpy.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	2to3: Apply `print` fixer.	Charles Harris	2013-04-06	1	-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 Harris	2013-03-28	1	-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 Harris	2013-03-01	1	-0/+3
\| \| \| \| \| \| \| \|	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.
*	FIX: fix doctest error with empty output	Matthew Brett	2011-08-16	1	-0/+18
\| \| \| \| \| \| \| \| \| \| \|	The numpy doctest extension generates an error with empty doctest output; this most often comes about with the +SKIP option. The numpy doctest plugin exposed a nose bug because it accidentally used a different default for the 'doctest-result-variable'. nose bug report here: http://code.google.com/p/python-nose/issues/detail?id=445
*	ENH: move doctest tests to own file with ifmain	Matthew Brett	2011-08-16	1	-0/+35
	The doctesting tests were in the code file, and (for me) rather difficult to run without running lots of other tests. With this change you can run the doctest tests in isolation by executing the test_doctesting.py file.