PyPedia talk:Feature requests
I add the content here, so to help the discussion.
 Add versioning support in the python library
What is the most "pythonic way" to import a specific version of pypedia method? What other forms of "versioning" can you think of?
What do you think about User:Daniel Mietchen's idea?
- When referencing a piece of code using any standard piece of syntax, e.g. Hanoi towers, that link should be saved with its version number, which would be inherited when forking.
Status done: http://www.pypedia.com/index.php/Pypedia:Documentation#Forking_an_article . What do you think? Alexandros Kanterakis 13:27, 26 April 2012 (CEST)
 Integration with data
If data have been analyzed, it is important to keep track of
- which version (or set) of data has been analyzed
- what code has been used to process these data (ideally on what hardware/ OS/ configuration)
- what had been the outcomes
- how many attempts had been made at analyzing these data
I imagine that PyPedia would be in a good position to handle all four of these. --Daniel Mietchen 22:36, 19 March 2012 (UTC)
 A sandbox
A sandbox page in the user space is not editable. Nevertheless anone can create a Foo_user_<username> and do whatever he likes. So this can be conceived as a user-spaced sandbox. Any ideas?
 Executable papers!!
The foremost vision of reproducible science.. Comment from User:Daniel Mietchen:
- Fits very well with the Encyclopaedia of original research.
 PyPedia License
Current CC license maybe it is not very suitable for a code project. Take a look at the discussion in reddit. Any ideas?
- Status. DONE. License: Simplified BSD License.
 Add Latex / Math support
- Seems easy.. http://www.mediawiki.org/wiki/Manual:Math
- Status: DONE