summaryrefslogtreecommitdiff
path: root/doc/source
Commit message (Collapse)AuthorAgeFilesLines
* MAINT: Fix typos in docsDongjoon Hyun2016-01-258-8/+8
|
* REL: Update master branch after 1.12.x branch has been made.Charles Harris2016-01-191-0/+1
| | | | | | | * Drop testing of Python 2.6, 3.2, and 3.3 * Create 1.12.0-notes.rst and add to source/documentation. * Update pavement.py to use 1.10.x as LOG_START * Update version numpy in setup.py
* Merge pull request #6453 from shoyer/naive-datetime64Charles Harris2016-01-161-25/+37
|\ | | | | API: Make datetime64 timezone naive
| * API: Make datetime64 timezone naiveStephan Hoyer2016-01-151-25/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes GH3290 With apologies to mwiebe, this rips out most of the time zone parsing from the datetime64 type. I think we mostly sorted out the API design in discussions last year, but I'll be posting this to the mailing list shortly to get feedback. Old behavior: # string parsing and printing defaults to your local timezone :( >>> np.datetime64('2000-01-01T00') numpy.datetime64('2000-01-01T00:00-0800','h') New behavior: # datetime64 is parsed and printed as timezone naive >>> np.datetime64('2000-01-01T00') numpy.datetime64('2000-01-01T00','h') # you can still supply a timezone, but you get a deprecation warning >>> np.datetime64('2000-01-01T00Z') DeprecationWarning: parsing timezone aware datetimes is deprecated; this will raise an error in the future numpy.datetime64('2000-01-01T00','h')
* | DOC/BUG: textual improvements in install docs, and fix a typo in setup.pyRalf Gommers2016-01-161-4/+3
| | | | | | | | Address comments of @charris on gh-6895.
* | DOC: some tweaks to the install and build info in the user guide.Ralf Gommers2016-01-162-7/+2
| |
* | DOC: add NumpyVersion to the docs, and mention it in version.pyRalf Gommers2016-01-161-0/+7
| |
* | DOC: add Cython to list of dependencies in INSTALL.txt. Closes gh-6682.Ralf Gommers2016-01-161-0/+6
| |
* | BUG: fix TravisCI test issues when using setuptools unconditionally.Ralf Gommers2016-01-162-6/+7
|/ | | | Also remove all mentions of setupegg.py from the documentation.
* DOC: Clean up/fix several references to the "future" 1.10 releaseNathaniel J. Smith2016-01-141-2/+2
| | | | Fixes gh-7010
* ENH: moveaxis functionStephan Hoyer2016-01-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes GH2039 This function provides a much more intuitive interface than `np.rollaxis`, which has a confusing behavior with the position of the `start` argument: http://stackoverflow.com/questions/29891583/reason-why-numpy-rollaxis-is-so-confusing It was independently suggested several times over the years after discussions on the mailing list and GitHub (GH2039), but never made it into a pull request: https://mail.scipy.org/pipermail/numpy-discussion/2010-September/052882.html My version adds support for a sequence of axis arguments. I find this behavior to be very useful. It is often more intuitive than supplying a list of arguments to `transpose` and also nicely generalizes NumPy's existing axis manipulation routines, e.g., def transpose(a, order=None): if order is None: order = reversed(range(a.ndim)) return moveaxes(a, order, range(a.ndim)) def swapaxes(a, axis1, axis2): return moveaxes(a, [axis1, axis2], [axis2, axis1]) def rollaxis(a, axis, start=0): if axis < start: start -= 1 return moveaxes(a, axis, start)
* DOC: Sync 1.10.3 and 1.10.4 release notes, update reference doc.Charles Harris2016-01-061-0/+2
|
* DOC: add note not to run tests from repo root in devguide. Closes gh-6907.Ralf Gommers2015-12-311-0/+3
| | | | [ci skip]
* DOC: fix broken link in user guide. Closes gh-6906.Ralf Gommers2015-12-311-2/+2
| | | | [ci skip]
* Fix carriage return inside commented python codeVincent Legoll2015-12-261-2/+2
| | | This looks more conventionnal
* Merge pull request #6600 from mgeier/doc-ndarray-subclassesCharles Harris2015-12-181-6/+6
|\ | | | | DOC: fix method signatures in "array subclasses"
| * DOC: fix method signatures in "array subclasses"Matthias Geier2015-12-111-6/+6
| | | | | | | | | | | | * Change ".. function::" -> ".. method::" * Remove "self" argument * Change "self" to "obj" in __array_finalize__
* | STY: Break some long lines in numpy-for-matlab-users.rst.Charles Harris2015-12-171-34/+81
| |
* | DOC: change uses of `rank` for `dimension`Matthew Brett2015-12-161-25/+27
|/ | | | | | | We used to use ``rank`` to mean the number of axes in an array, but no more. Change these uses of rank to refer to dimensions. Closes gh-6839
* Merge pull request #6789 from njsmith/governance-title-tweakseberg2015-12-081-1/+1
|\ | | | | [doc] Fix title of governance section in docs
| * [doc] Fix title of governance section in docsNathaniel J. Smith2015-12-071-1/+1
| |
* | MAINT: Typo in arrays.indexing.rst Issue#6670floatingpointstack2015-11-121-1/+1
| |
* | DOC: A bit of copy-editing of the 'NumPy for Matlab Users' guide.Warren Weckesser2015-10-301-33/+35
| |
* | DOC: Fix an argument in 'Numpy for Matlab Users'.Warren Weckesser2015-10-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | I've seen at least three occurrences (a couple on stackoverflow, and one private email) of someone using the argument 'order=15' in a call to the 'set_integrator' method of 'scipy.integrate.ode'. Presumably this is because of the suggestion in the "NumPy for Matlab Users" guide to replace 'ode15s' with 'scipy.integrate.ode(f).set_integrator('vode', method='bdf', order=15)'. The stiff solver in 'vode'--presumably the solver of interest for someone using 'ode15s'--has a maximum order of 5, and the non-stiff solver has maximum order of 12. (The maximum order of 'ode15s' is also 5; the '15' in the name refers to the variable order ranging from 1 to 5.)
* | DOC: Release notes for Numpy 1.10.2.Charles Harris2015-10-291-0/+1
|/ | | | [ci skip]
* DOC: import "numpy for matlab users" from the wikiPauli Virtanen2015-10-252-0/+696
| | | | | | | Might be useful to someone. Excised too opinionated parts and replaced most links to specific software with the topical software page links.
* DOC: reorganize user guide a bit + import "tentative numpy tutorial" from wikiPauli Virtanen2015-10-258-204/+1580
| | | | | | | | The user guide was missing a quick tutorial --- the basics.* stuff is somewhat too complex already. The "building numpy" instructions also should not be "introductory material".
* DOC: remove placeholders and incompleteness warningsPauli Virtanen2015-10-254-28/+0
| | | | | Neither are useful, and will discourage both reading and editing of the material.
* DOC: typo in arrays.interface.rst #6516Alain2015-10-201-1/+1
|
* DOC: fixed #6525Yifan Li2015-10-191-8/+8
|
* Merge pull request #6529 from niccalle/fix_typoJaime2015-10-191-1/+1
|\ | | | | DOC: Fixed a typo at line 289 at c-api.array.rst
| * DOC: Fixed a typo at line 289 at c-api.array.rstNicolas Calle2015-10-191-1/+1
| | | | | | | | Fixes #6521
* | Merge pull request #6528 from jaimefrio/fix_typoJaime2015-10-191-3/+3
|\ \ | |/ |/| DOC: fixed typo in arrays.classes.rst
| * DOC: fixed typo in arrays.classes.rstJaime Fernandez2015-10-191-3/+3
| |
* | MAINT: Spellcheck doc/source/f2py/signature-file.rst.Charles Harris2015-10-161-5/+5
| |
* | BUG: allow extension of common blocks in numpy.f2pyAlexander Heger2015-10-161-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lack of this feature resulted in the generation of incorrect *.pyf files. For example, the pyf file created by: subroutine sub3 (some arguments) real a, b, c, d common /coeff/ a, b common /coeff/ c, d <do stuff> return end Should contain both common statements the declaration of all four variables a, b, c, and d. Closes #5876.
* | DOC: Create 1.10.1 release notes.Charles Harris2015-10-121-0/+1
| | | | | | | | [ci skip]
* | DOC: add lib.Arrayterator to reference guide. Closes gh-6404.Ralf Gommers2015-10-111-0/+1
| |
* | DEV: add CC-0 public domain dedication to governance documentNathaniel J. Smith2015-10-091-0/+9
| | | | | | | | | | | | | | | | We want to allow other projects to steal from us, like we stole from Jupyter/IPython :-). This relicensing / public domain dedication is possible because all text here is either by me (and thus copyright me) or else taken from the Jupyter/IPython document, and their document is also under CC-0 as per https://github.com/jupyter/governance/pull/9
* | DOC: typo: change NumFocus to NumFOCUS in one place in governance doc.Ralf Gommers2015-10-091-1/+1
|/
* Merge pull request #6406 from charris/update-gh-6310Charles Harris2015-10-061-10/+12
|\ | | | | DOC: Update gh-6310: Update docs for numpy.genfromtxt.
| * DOC: Cleanup genfromtxt documentation a bit.Charles Harris2015-10-041-10/+12
| |
| * DOC: Update docs for numpy.genfromtxt.jason king2015-10-041-3/+3
| | | | | | | | | | | | | | Note that a list of strings can be passed as the first parameter. The strings are treated as the lines in a file. Closes #6247
* | Merge pull request #6352 from njsmith/governanceCharles Harris2015-10-054-0/+456
|\ \ | | | | | | DEV: Governance document (draft)
| * | DEV: attempt to clarify rules for ending an Institutional PartnershipNathaniel J. Smith2015-10-041-3/+6
| | |
| * | DEV: governance: wording tweakNathaniel J. Smith2015-10-041-8/+8
| | |
| * | DEV: governance: Include links to current membership of each groupNathaniel J. Smith2015-10-042-0/+13
| | |
| * | DEV: for new council members, clarify order of voting and talking to themNathaniel J. Smith2015-10-041-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Original text seemed to imply that we would always ask the potential new Council Member whether they were interested *before* we actually decided whether to offer them a spot, which could create a sticky situation if someone ever got voted down. Rephrase to make clear that things do not have to occur in this order.
| * | DEV: remove draft markers from governance documentNathaniel J. Smith2015-10-032-4/+0
| | | | | | | | | | | | In preparation for merging.
| * | DEV: remove the interstitial notes on the seed steering councilNathaniel J. Smith2015-10-031-15/+0
| | | | | | | | | | | | | | | | | | Now that this seems to be settled, we don't need this cluttering up the main text. (For the record: the rule listed here is what we actually used.)
View Lorry Controller Status