summaryrefslogtreecommitdiff
path: root/doc/source
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* DOC: fix doc/source/conf.py to work with Python 3Pauli Virtanen2013-02-271-2/+2
|
* MAINT: always use plot directive from Matplotlib, and prefer Sphinx linkcodePauli Virtanen2013-02-161-22/+3
|
* move to www.numpy.orgSandro Tosi2012-12-302-2/+2
|
* Merge pull request #455 from rgommers/devguide-updateCharles Harris2012-10-035-145/+67
|\ | | | | Devguide update
| * DOC: expand sections on commit messages and merging/rebasing in the devguide.Ralf Gommers2012-09-231-2/+16
| | | | | | | | This commit address comments from Charles on PR #455.
| * DOC: one more edit to the dev-guide.Ralf Gommers2012-09-221-1/+7
| | | | | | | | | | Recommend to update master before creating your feature branch. Thanks to Nicky van Foreest for feedback on the dev-guide.
| * DOC: remove section "Patching" from dev-guide.Ralf Gommers2012-09-224-133/+6
| | | | | | | | | | This section is outdated, and following it pretty much ensures that your patches will languish in Trac.
| * DOC: a few edits to make "Development Workflow" in the dev guide clearer.Ralf Gommers2012-09-221-12/+13
| |
| * DOC: document in dev-guide how to write a good commit message.Ralf Gommers2012-09-221-0/+28
| |
* | FIX: Transition scheme for safer in-place ufunc operationsNathaniel J. Smith2012-09-201-0/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Use PyMODINIT_FUNC and update docs accordingly.cgohlke2012-09-021-4/+4
| | | | See https://github.com/scipy/scipy/pull/279
* Added entries for assert_allclose, assert_array_almost_equal_nulp, and ↵Matt Davis2012-07-201-0/+3
| | | | assert_array_max_ulp into the numpy testing reference documentation.
* Merge pull request #350 from jayvius/get-view2Travis E. Oliphant2012-07-171-0/+10
|\ | | | | Add transition code for returning view when selecting subset of fields
| * change DeprecationWarning to FutureWarningJay Bourque2012-07-171-1/+1
| |
| * Updated reference docs for DeprecationWarningJay Bourque2012-07-171-0/+10
| |
* | Merge pull request #327 from teoliphant/restore_apiTravis E. Oliphant2012-07-171-22/+29
|\ \ | |/ |/| Restore ability to not include semi-colons.
| * DOC: Update API description with suggestions from charris.Travis E. Oliphant2012-07-171-8/+5
| |
| * DOC: update language of C-API deprecations.Travis E. Oliphant2012-07-171-5/+7
| |
| * Fix-up deprecations language.Travis E. Oliphant2012-07-111-5/+13
| |
| * Fix the deprecations language.Travis E. Oliphant2012-07-111-19/+19
| |
* | Merge pull request #332 from nouiz/fillwbyte_docCharles Harris2012-07-161-0/+1
|\ \ | | | | | | Add doc for PyArray_FILLWBYTE to tell the ndarray must be c contiguous.
| * | better new doc sentence following code review.Frederic2012-07-161-1/+1
| | |
| * | Add doc for PyArray_FILLWBYTE to tell the ndarray must be c contiguous.Frederic2012-07-061-0/+1
| |/
* | DOC: merge wiki edits. Add percentile to statistics routines (ML suggestion).Ralf Gommers2012-07-072-2/+4
| |
* | DOC: merge wiki docs - edits under doc/.Ralf Gommers2012-07-076-18/+51
|/
* Remove maskna API from ndarray, and all (and only) the code supporting itNathaniel J. Smith2012-06-167-1043/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original masked-NA-NEP branch contained a large number of changes in addition to the core NA support. For example: - ufunc.__call__ support for where= argument - nditer support for arbitrary masks (in support of where=) - ufunc.reduce support for simultaneous reduction over multiple axes - a new "array assignment API" - ndarray.diagonal() returning a view in all cases - bug-fixes in __array_priority__ handling - datetime test changes etc. There's no consensus yet on what should be done with the maskna-related part of this branch, but the rest is generally useful and uncontroversial, so the goal of this branch is to identify exactly which code changes are involved in maskna support. The basic strategy used to create this patch was: - Remove the new masking-related fields from ndarray, so no arrays are masked - Go through and remove all the code that this makes dead/inaccessible/irrelevant, in a largely mechanical fashion. So for example, if I saw 'if (PyArray_HASMASK(a)) { ... }' then that whole block was obviously just dead code if no arrays have masks, and I removed it. Likewise for function arguments like skipna that are useless if there aren't any NAs to skip. This changed the signature of a number of functions that were newly exposed in the numpy public API. I've removed all such functions from the public API, since releasing them with the NA-less signature in 1.7 would create pointless compatibility hassles later if and when we add back the NA-related functionality. Most such functions are removed by this commit; the exception is PyArray_ReduceWrapper, which requires more extensive surgery, and will be handled in followup commits. I also removed the new ndarray.setasflat method. Reason: a comment noted that the only reason this was added was to allow easier testing of one branch of PyArray_CopyAsFlat. That branch is now the main branch, so that isn't an issue. Nonetheless this function is arguably useful, so perhaps it should have remained, but I judged that since numpy's API is already hairier than we would like, it's not a good idea to add extra hair "just in case". (Also AFAICT the test for this method in test_maskna was actually incorrect, as noted here: https://github.com/njsmith/numpyNEP/blob/master/numpyNEP.py so I'm not confident that it ever worked in master, though I haven't had a chance to follow-up on this.) I also removed numpy.count_reduce_items, since without skipna it became trivial. I believe that these are the only exceptions to the "remove dead code" strategy.
* MAINT: port release notes and release script changes from 1.6.x.Ralf Gommers2012-05-201-0/+5
|
* Stress that all array creation C functions steals a reference to descr.Francesc Alted2012-05-041-0/+4
|
* DOC: Add a section documenting 1.6/1.7 datetime64 differencesMark Wiebe2012-05-011-0/+127
|
* DOC: Update documentation and release notes about C-API deprecationsMark Wiebe2012-04-062-0/+52
|
* ENH: Add module containing functions for padding n-dimensional arrays.tim cera2012-04-042-22/+32
| | | | | | | | | | | | | The various padding functions are exposed as options to a public 'pad' function. Example: pad(a, 5, mode='mean') Current modes are 'constant', 'edge', 'linear_ramp', 'maximum', 'mean', 'median', 'minimum', 'reflect', 'symmetric', 'wrap', and <function> This commit includes unit tests and doctests and is based on feature request ticket #655.
* DOC: label datetime support as experimental. Closes #2072.Ralf Gommers2012-03-301-0/+3
|
* DOC: label the current NA implementation as experimental in 1.7.xRalf Gommers2012-03-301-0/+5
| | | | This has been extensively discussed on the mailing list. See #2072.
* DOC: generate links to source codePauli Virtanen2012-03-111-0/+64
|
* DOC: merge wiki doc edits.Ralf Gommers2012-03-033-7/+9
|
* DOC: Replace references to macros in old_defines with new.Charles Harris2012-02-044-21/+21
| | | | | Also remove swig support for numpy < 1 from numpy.i since it expects the old macros.
* DOC: Improve numpy reference documentation of polynomial classes.Charles Harris2012-01-093-16/+26
| | | | | Add more explanation of what happens in polynomial substitution and also of its use in casting between types. Clean up some rst glitches.
* DOC: Document the use of the polynomial convenience classes.Charles Harris2012-01-091-10/+337
|
* DOC: Lower toc number of levels.Charles Harris2012-01-091-1/+1
|
* DOC: Add version added to some of the polynomial package modules.Charles Harris2012-01-097-0/+14
|
* BUG: Fix up links to classes.Charles Harris2012-01-096-12/+11
| | | | | The Sphinx markup was incorrect the documentation to the polynomial convenience classes wasn't being generated.
* DOC: Rearrange the polynomial documents.Charles Harris2012-01-099-14/+567
| | | | | This is the first step in cleaning up the polynomial documentation and writing an instructional section on the convenience classes.
* FIX: Changed named to choice, reverted other changes.Chris Jordan-Squire2011-12-171-0/+3
|
* ENH: New sample function, bugs in tests fixedChris Jordan-Squire2011-12-161-0/+1
|
* ENH: missingdata: Make PyArray_Converter and PyArray_OutputConverter safer ↵Mark Wiebe2011-08-273-4/+28
| | | | | | | | for legacy code These functions now reject inputs with NA, and there are alternative functions PyArray_AllowNAConverter and PyArray_OutputAllowNAConverter that functions should use when they intend to support NA.
* DOC: missingdata: Add a mention of the design NEP, and masks vs bitpatternsMark Wiebe2011-08-271-0/+8
|
* DOC: missingdata: Updates from pull request feedbackMark Wiebe2011-08-272-22/+28
| | | | From Chris Jordan-Squire
* DOC: missingdata: Updates based on pull request feedbackMark Wiebe2011-08-271-10/+34
| | | | From github users xscript and 87.
* DOC: missingdata: Also show what assigning a non-NA value does in each caseMark Wiebe2011-08-271-0/+23
| | | | Thanks to chebee7i for the feedback
View Lorry Controller Status