SEPs: Spyder Enhancement Proposals

Adapted from https://github.com/ipython/ipython/wiki/IPEPs:-IPython-Enhancement-Proposals

This page serves to index the various Spyder Enhancement Proposals that we have set and are using to guide Spyder development. Developers are encouraged to author SEPs for any development in Spyder that the community needs to discuss before code is written. Currently, our protocol for SEPs is relatively simple.

The SEP author should:

1. Create a new wiki page with the title "SEP N: Title" where "N" is the next consecutive SEP number and "Title" is an appropriate title for the SEP.
2. Link to that wiki page from this page.
3. Create a GitHub issue for the SEP.
4. Notify that you have created the SEP and inform them that discussion is taking place on this issue (provide links to the SEP and issue).
5. Discussion should continue until consensus is reached.
6. At that point, a pull request or issue should be opened to track the actual implementation.
7. The SEP wiki page should be updated with information about the discussion and implementation.

Each SEP should have a table/area at the top with the following information:

Status	Active | Deferred | Accepted | Rejected | Implemented
Author	Full Name <[email protected]>
Created	February 24, 2015
Updated	February 30, 2015
Discussion	link to the issue where the SEP is being discussed
Implementation	link to the PR

Index of SEPs

• SEP 0: SEP Template -- Accepted
• SEP 1: Version Control -- Active
• SEP 2: Interactive Tutorial Content -- Active
• SEP 3: Projects -- Active
• SEP 4: Pip Conda Installable Plugins -- Active
• SEP 5: Core Extension Plugins -- Active
• SEP 6: Spyder API -- Active
• SEP 7: Generic Plugin Subsystem -- Active