| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
counterparts (#17222)
* DOC: redistribute docstring-only content from numpy/doc
* DOC: post-transition clean-up
* DOC, MAINT: reskip doctests, fix a few easy ones
|
| |
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
| |
|
|
| |
Relates to gh-6103
|
| | |
|
| | |
|
| |
|
|
|
|
| |
* DOC, MAINT: Misc. typo fixes
Found via `codespell`
|
| |
|
|
| |
Change `np.power` -> `numpy.power` to make it reference
the function's documentation
|
| | |
|
| |
|
|
|
|
|
| |
Unlike Python, NumPy integers have fixed sizes. This can lead to
confusion when a integer overflow occurs and users expect NumPy integer
types to behave similarily to Python integers. This commit explains
integer overflow, an example and potential work arounds.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The rst markup in numpy/doc/basics.py uses `\s`, which is interpreted by
python 3.6 as a deprecated escape sequence. Fix by escaping the `\`.
Closes #9551.
[ci skip]
|
| |\ |
|
| | |\
| | |
| | | |
DOC: correct formatting of basic.types.html
|
| | | | |
|
| | | |
| | |
| | |
| | | |
[ci-skip]
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the documentation for types allowed in numpy, missing spaces around
the backticks for fixed-width formatting cause code examples to appear
as plain text, or are causing plain text to appear as code. This commit
fixes back tick spacing in the 'Extended Precision' section of the
'Data Types' page.
|
| |/ / |
|
| |/ |
|
| | |
|
| |
|
|
| |
The strings in error messages were left untouched
|
| | |
|
| | |
|
| |
|
|
| |
Now is as good a time as any with open PR's at a low.
|
| |
|
|
|
| |
Also mention np.intp, which at least personally I think is not an
unimportant type.
|
| |
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
The int64 data type allows numbers from -9223372036854775808 to
9223372036854775807. The minus sign was missing.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
they are still an improvement)
|
| |
|
