summaryrefslogtreecommitdiff
path: root/doc/sphinxext/numpydoc/tests
Commit message (Collapse)AuthorAgeFilesLines
* BLD: remove submodule doc/sphinxext that pointed to numpydocsmattip2020-09-161-0/+0
|
* MAINT: Bumpy numpydoc version.Ross Barnowski2020-05-201-0/+0
| | | | | | | Fixes problem with citation (reference) anchors in rendered docs. Actual fix was in numpy/numpydoc@7c42883, but this bumps to latest (unreleased) numpydoc version.
* DOC: update numpydoc to latest mastermattip2019-04-091-0/+0
|
* BUILD: update numpydocs to latest versionmattip2019-03-201-0/+0
|
* update submodule numpydoc for changes due to this branchmattip2018-04-121-0/+0
|
* DOC: Update sphinxext submodule hash.Charles Harris2018-02-151-0/+0
|
* DOC: update sphinxext to numpydoc 0.6.0Ralf Gommers2016-02-131-0/+0
|
* DOC: update numpydoc to tag v0.5Julian Taylor2014-06-111-0/+0
|
* Add Numpydoc as a git submodulePauli Virtanen2013-07-251-0/+0
|
* Move numpydoc to a separate repositoryPauli Virtanen2013-07-255-787/+0
|
* ENH: Allow unnamed return values in Returns section of doc stringRob Ruana2013-06-251-8/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | Developers usually only need the type of a return value followed by a brief description. However, in some cases providing a name for a return value can make the documentation clearer. This enhancement changes the format of the Returns section such that the type is required, and the name is optional: Returns ------- int Description of anonymous integer return value. x : str Description of string return value named `x`. With this change, if a colon is not present, then the entire line is interpreted as the return type. In all other cases, the Returns section is interpreted according to the current rules. Consistent with the current format, if a colon is present, then the text to the left of the colon is interpreted as the name; and the text to the right of the colon is interpreted as the type. This makes the proposed change backwards compatible with existing documentation.
* BUG: sphinxext: fix sphinx extensions broken recentlyPauli Virtanen2013-05-011-8/+5
|
* 2to3: Apply unicode fixer.Charles Harris2013-04-211-23/+28
| | | | | | | | | | | | | | | | | | | | | | | | The unicode fixer strips the u from u'hi' and converts the unicode type to str. The first won't work for Python 2 and instead we replace the u prefix with the sixu function borrowed from the six compatibility package. That function calls the unicode constructor with the 'unicode_escape' encoder so that the many tests using escaped unicode characters like u'\u0900' will be handled correctly. That makes the sixu function a bit different from the asunicode function currently in numpy.compat and also provides a target that can be converted back to the u prefix when support for Python 3.2 is dropped. Python 3.3 reintroduced the u prefix for compatibility. The unicode fixer also replaces 'unicode' with 'str' as 'unicode' is no longer a builtin in Python 3. For code compatibility, 'unicode' is defined either as 'str' or 'unicode' in numpy.compat so that checks like if isinstance(x, unicode): ... will work properly for all python versions. Closes #3089.
* 2to3: Apply `print` fixer.Charles Harris2013-04-065-5/+5
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* Merge pull request #460 from endolith/regex_formattingCharles Harris2013-04-031-3/+2
|\ | | | | DOC: Formatting fixes using regex
| * DOC: Used regex to find colons missing spaces which render wrong online, ↵endolith2013-03-191-3/+2
| | | | | | | | also other spacing or formatting mistakes
* | 2to3: Add `from __future__ import ...` to new files.Charles Harris2013-03-284-0/+8
| | | | | | | | | | | | The new files that came in when doc/sphinxext/numpydoc was restructured as a package with test stubs did not have `from __future__ import ...`. This fixes that omission.
* | 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/+1
| | | | | | | | 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.
* BUG: numpydoc: check that it works with sub-classesPauli Virtanen2013-02-161-0/+4
|
* TST: numpydoc: more class testsPauli Virtanen2013-02-161-2/+114
|
* TST: numpydoc: add stub test files, to check that files at least importPauli Virtanen2013-02-164-0/+12
|
* ENH: numpydoc: Python 2 & 3 in single codebase, restructure as a packagePauli Virtanen2013-02-161-0/+632