Differences between revisions 9 and 10
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
|
We make use of [http://trac.edgewall.org/ Trac] to do project management. There, you can see what we are currently working on, as well as file bug-reports (known as ''tickets''). |
We make use of Github and Trac to do project management. There, you can see what we are currently working on (Pull Requests), as well as file bug-reports (tickets). !NumPy development has already been moved over to Github completely, the SciPy bug tracker is still on Trac but will be moved at some point as well. |
| Line 6: | Line 5: |
| 1. Go to the relevant page: | |
| Line 7: | Line 7: |
| 1. Go to the relevant Trac page: | - [https://github.com/scipy/scipy/pulls SciPy pull requests] |
| Line 9: | Line 9: |
| - [http://projects.scipy.org/scipy SciPy Developer Page] | - [http://projects.scipy.org/scipy SciPy bug reports] |
| Line 11: | Line 11: |
| - [http://projects.scipy.org/numpy NumPy Developer Page] | - [https://github.com/numpy/numpy/pulls NumPy pull requests] |
| Line 13: | Line 13: |
| 2. Register your username (we require logins to prevent spam), by clicking on "register". You only need to do this once (i.e, SciPy and NumPy Developer Pages use the same login/password). |
- [https://github.com/numpy/numpy/issues NumPy bug reports] 2. On both Github and Trac you need to register an account the first time you use it. |
| Line 17: | Line 19: |
| 4. File your bug-report by clicking "New Ticket" ('''this link is only available once you've logged in'''). |
4. File your bug-report by clicking "New Issue" on Github or "New Ticket" on Trac ('''note that on Trac this link is only available once you've logged in'''). 5. Note that the bug trackers are mostly for actual bugs, if you want to propose an enhancement, then the mailing list is a better place to get feedback. |
Please help us by reporting any problems you find.
We make use of Github and Trac to do project management. There, you can see what we are currently working on (Pull Requests), as well as file bug-reports (tickets). NumPy development has already been moved over to Github completely, the SciPy bug tracker is still on Trac but will be moved at some point as well.
- Go to the relevant page:
- On both Github and Trac you need to register an account the first time you use it.
- Make sure the bug hasn't already been reported. Click on "Search". Then, type in some keywords, select "Tickets" and click "Search".
File your bug-report by clicking "New Issue" on Github or "New Ticket" on Trac (note that on Trac this link is only available once you've logged in).
- Note that the bug trackers are mostly for actual bugs, if you want to propose an enhancement, then the mailing list is a better place to get feedback.
Guidelines for submitting bugs
Provide a good description. We tend to ignore tickets named "SciPy is BROKEN!!!", and focus on ones that state the problem clearly, e.g. "scipy.ndimage ignores keyword 'axis'".
- Include a code snippet to illustrate the problem. Try to narrow it down to a few lines.
- If you experience segfaults or memory errors, give a GDB traceback:
$ gdb python GNU gdb 6.3.50-20050815 (Apple version gdb-573) (Fri Oct 20 15:50:43 GMT 2006) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-apple-darwin"...Reading symbols for shared libraries .. done (gdb) run -c "import scipy; scipy.test(10,10)" Starting program: /usr/local/bin/python -c "import scipy; scipy.test()" Reading symbols for shared libraries . done Program received signal SIGTRAP, Trace/breakpoint trap. 0x8fe01010 in __dyld__dyld_start () (gdb) c Continuing. Reading symbols for shared libraries . done Reading symbols for shared libraries . done ...
Then use the "bt" command after the segfault happens to get the backtrace. Alternatively, - Set the milestone to the next release.
Thank you for helping to make SciPy better!