| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Replaces the
raise Exception, msg:
form with
raise Exception(msg):
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There were some conflicts with the 2to3 work in numpy. I think I got the
fixes right.
* enh-numpydoc:
DOC: fix doc/source/conf.py to work with Python 3
BUG: numpydoc: check that it works with sub-classes
TST: numpydoc: more class tests
BUG: numpydoc: fix bugs in attribute docstring extraction + improve presentation
TST: numpydoc: add stub test files, to check that files at least import
MAINT: always use plot directive from Matplotlib, and prefer Sphinx linkcode
ENH: numpydoc: Python 2 & 3 in single codebase, restructure as a package
ENH: numpydoc: deal with duplicated signatures
DOC: numpydoc/linkcode: mention that the extension will be in Sphinx upstream
BUG: numpydoc/linkcode: do not detect linkcode config changes
Conflicts:
doc/sphinxext/numpydoc/docscrape.py
doc/sphinxext/numpydoc/docscrape_sphinx.py
doc/sphinxext/numpydoc/linkcode.py
doc/sphinxext/numpydoc/phantom_import.py
doc/sphinxext/numpydoc/traitsdoc.py
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Since the linkcode_resolve is a function, it triggers configuration
change on each rebuild, resulting to full rebuild always. It's better
to make it not do that.
|
|\ \
| | |
| | | |
2to3: Fix callable.
|
| | | |
|
|\ \ \
| | | |
| | | | |
2to3: Apply `funcattrs` fixer. Closes #3058.
|
| |/ /
| | |
| | |
| | |
| | | |
This replaces the `b.func_xxxx` with newer `__xxxx__` attribute names
For example, `f.__name__` replaces `f.func_name`
|
|/ /
| |
| |
| | |
This changes the `exec` command to the `exec` function.
|
|\ \
| | |
| | | |
2to3: Remove `has_key` use that was missed.
|
| |/
| |
| |
| |
| | |
The files not in the numpy/ directory were missed. This gets them
all (I hope).
|
|/
|
|
| |
This should finish the updating of the exception syntax.
|
|
|
|
|
|
| |
There were some changes in the release branch that were not put into master.
After this commit, the file 1.7.0-notes.rst is synchronised with the release
branch.
|
| |
|
|\
| |
| | |
ENH: Allow 0-d indexes in np.take
|
| |
| |
| |
| |
| |
| |
| | |
The TakeFrom already supported this. This removes the check which
made it not possible and adds some tests for take.
Also add documentation and information to the release notes.
|
| |
| |
| |
| |
| |
| |
| | |
PyFile_Check and PyInstance_Check have been removed from the C API
for python 3. This removes calls to those two functions from
numpy.i for PY_MAJOR_VERSION >= 3 so that it builds with a
python 3 Python.h.
|
| |
| |
| |
| |
| |
| |
| | |
These references were in MANIFEST.in, doc/summarize.py, release.sh, and
numpy/testing/noseclasses.py and involved scons files that have been
removed, mostly setupscons.py and setupsconsegg.py that were in the top
level.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
This removes files and code supporting scons builds. After this change
numpy will only support builds using distutils or bento. The removal of
scons has been discussed on the list several times and a decision has been
made that scons support is no longer needed. This was originally discussed
for numpy 1.7 and because the distutils and bento methods are still
available we are skipping the usual deprecation period.
|
| |
|
| |
|
|
|
|
| |
Forwardport gh-2737.
|
|\
| |
| | |
MAINT: Cleanup 1.8.0-notes.rst.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Remove contents of 1.7.0-notes that were left when it was copied,
note that support for Python 2.4 - 2.5 has been dropped, and note
deprecation of non-integer indices.
|
|/
|
|
|
|
|
| |
The master branch version had diverged from the release branch. This
brings them back into sync, adds a mention that Python 2.4 - 2.5 support
has been dropped, corrects spelling errors, does some reformatting, and
removes trailing whitespace.
|
| |
|
|
|
| |
and some other small changes
|
| |
|
|\
| |
| | |
Devguide update
|
| |
| |
| |
| | |
This commit address comments from Charles on PR #455.
|
| |
| |
| |
| |
| | |
Recommend to update master before creating your feature branch.
Thanks to Nicky van Foreest for feedback on the dev-guide.
|
| |
| |
| |
| |
| | |
This section is outdated, and following it pretty much ensures that your
patches will languish in Trac.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In numpy 1.6 and earlier, if you do
np.add(int_arr, float_arr, out=int_arr)
or
int_arr += float_arr
then the result will be silently truncated to integer values. This
often produces bugs, because it's easy to accidentally end up with an
integer array and not realize it.
Therefore, there seems to be consensus that we should switch to using
same_kind casting by default for in-place ufunc operations. However,
just switching this (as was done initially during the 1.7 development
cycle) breaks a lot of code, which is rude and violates our
deprecation policy.
This commit instead adds a special temporary casting rule which acts
like "unsafe", but also checks whether each operation would be allowed
under "same_kind" rules and issues a DeprecationWarning if not.
It also moves NPY_DEFAULT_ASSIGN_CASTING into the formal API instead
of leaving it as a #define. This way we can change it later, and any
code which references it and is compiled against this version of numpy
will automatically switch to whatever we change it too. This avoids
the situation where we want to remove the temporary magic value we're
using to create DeprecationWarnings now, but can't because it would be
an ABI break.
|
|
|
|
| |
See https://github.com/scipy/scipy/pull/279
|
|
|
|
| |
assert_array_max_ulp into the numpy testing reference documentation.
|
| |
|
|\
| |
| | |
Add transition code for returning view when selecting subset of fields
|