|
Size: 875
Comment:
|
Size: 1489
Comment: +SubclassingDictionaries
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Beginners: | ==== Beginners ==== ''Join the fun and start learning today!'' |
| Line 7: | Line 8: |
| Other: | ==== Topic guides ==== ''Development-Guides-R-Us!'' * WebProgramming * GuiProgramming * ThreadProgramming * DatabaseProgramming * DistributedProgramming * SoYouWanna - Python solutions to software problems * PythonDevWisdom - Useful snippets for advanced Python programmers * WritingExceptionClasses * SubclassingDictionaries ==== Other ==== |
| Line 9: | Line 23: |
| * FrequentlyAskedQuestions | * PythonBooks * PythonPapers * PythonQuestions * PythonPhilosophy * LanguageComparisons |
| Line 15: | Line 33: |
Like the [http://www.php.net/manual/en/ PHP Manual] at [http://www.php.net/]. For css see: [http://www.css-stuff.com/ CSS stuff] |
A guide and a discussion page for PythonDocumentation.
Beginners
Join the fun and start learning today!
[http://www.python.org/doc/Newbies.html Python for Beginners]
Topic guides
Development-Guides-R-Us!
SoYouWanna - Python solutions to software problems
PythonDevWisdom - Useful snippets for advanced Python programmers
Other
[http://www.python.org/doc/ Documentation Central]
Discussion:
Please!! get a wiki running side-by-side with the docs eg: 1 corresponding wikiable page for every page here in the pydocs. The startup data is simply that of the docs, so just mirror their structure. Then after the wiki docs start offering lots of useful information, the actual doc writers can incorporate this. To summarize, I think Python's documentation (like the library reference) is basically a big melange of api data and some snippets of useful info. This wiki will help replace those places that just use API data to fill up space, and turn it into something better.
Like the [http://www.php.net/manual/en/ PHP Manual] at [http://www.php.net/]. For css see: [http://www.css-stuff.com/ CSS stuff]