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/+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. | ||||
* | fix a minor mistake in the previous commit | Darren Dale | 2009-08-25 | 1 | -1/+1 |
| | |||||
* | add comment about __array_prepare__ to 1.4 release notes | Darren Dale | 2009-08-25 | 1 | -2/+2 |
| | |||||
* | add support for __array_prepare__ | Darren Dale | 2009-08-23 | 1 | -13/+25 |
| | |||||
* | Fixing internal links | Matthew Brett | 2009-07-23 | 1 | -1/+2 |
| | |||||
* | After thinking, a more general understanding of slicing etc | Matthew Brett | 2009-07-23 | 1 | -45/+71 |
| | |||||
* | and more tiny doc typos | Matthew Brett | 2009-07-23 | 1 | -2/+1 |
| | |||||
* | Experimenting with __array_wrap__ | Matthew Brett | 2009-07-23 | 1 | -39/+106 |
| | |||||
* | Tiny doc rearrangement | Matthew Brett | 2009-07-23 | 1 | -4/+4 |
| | |||||
* | Further extension of doctests for inheritance | Matthew Brett | 2009-07-23 | 1 | -55/+97 |
| | |||||
* | Small edits to subclassing doc to make classes more explicit | Matthew Brett | 2009-07-23 | 1 | -14/+14 |
| | |||||
* | Moving more to doctests, more explanation of views, slices | Matthew Brett | 2009-07-23 | 1 | -95/+96 |
| | |||||
* | Moving some examples to doctest format; removed debugging cruft in example | Matthew Brett | 2009-07-22 | 1 | -53/+46 |
| | |||||
* | Some clearer explanation of __array_finalize__ | Matthew Brett | 2009-07-22 | 1 | -45/+171 |
| | |||||
* | Import documentation from doc wiki (part 2, work-in-progress docstrings, but ↵ | Pauli Virtanen | 2008-10-28 | 1 | -11/+12 |
| | | | | they are still an improvement) | ||||
* | reindenting prior to release | Jarrod Millman | 2008-09-02 | 1 | -41/+41 |
| | |||||
* | Point to example | Matthew Brett | 2008-08-27 | 1 | -3/+3 |
| | |||||
* | Document on subclassing | Matthew Brett | 2008-08-27 | 1 | -0/+291 |