Show More
@@ -28,6 +28,10 b' Some guidelines on contributing to IPython:' | |||
|
28 | 28 | * Pull Requests should be tested, if feasible: |
|
29 | 29 | - bugfixes should include regression tests |
|
30 | 30 | - new behavior should at least get minimal exercise |
|
31 | * New features and backwards-incompatible changes should be documented by adding | |
|
32 | a new file to the [development](docs/source/whatsnew/development) directory, | |
|
33 | see [the README.md there](docs/source/whatsnew/development/README.md) for | |
|
34 | details. | |
|
31 | 35 | |
|
32 | 36 | [Travis](http://travis-ci.org/#!/ipython/ipython) does a pretty good job testing IPython and Pull Requests, |
|
33 | 37 | but it may make sense to manually perform tests (possibly with our `test_pr` script), |
@@ -4,6 +4,13 b'' | |||
|
4 | 4 | |
|
5 | 5 | This document describes in-flight development work. |
|
6 | 6 | |
|
7 | .. warning:: | |
|
8 | ||
|
9 | Please do not edit this file by hand (doing so will likely cause merge | |
|
10 | conflicts for other Pull Requests). Instead, create a new file in the | |
|
11 | `docs/source/whatsnew/pr` folder | |
|
12 | ||
|
13 | ||
|
7 | 14 | - `%%capture` cell magic now captures the rich display output, not just |
|
8 | 15 | stdout/stderr |
|
9 | 16 |
General Comments 0
You need to be logged in to leave comments.
Login now