On Wed, Jul 7, 2010 at 9:24 PM, C. Titus Brown <ctb at msu.edu> wrote: > Hi all, > > over on the fellowship o' the packaging mailing list, one of our GSoC > students > (merwok) asked about how much formatting info should go into Python stdlib > docstrings. Right now the stdlib docstrings are primarily text, AFAIK; but > with the switch to Sphinx for the official Python docs, should we permit > ReST-general and/or Sphinx-specific markup in docstrings? > > Hmm, I don't actually see that the stdlib docstrings are imported into the > Python documentation anywhere, so maybe the use of Sphinx isn't that > relevant. But how about ReST in general? > So will we be able to use .__docs__ within python interpretor, which is quite handy feature. >>> print(os.getcwd.__doc__) getcwd() -> path Return a string representing the current working directory. Also some python interpretors like bpython uses it ; a snapshot here - h ttp://cl.ly/c5bb3be4a01d9d44732f So will it be ok to break them ? > > See > > http://sphinx.pocoo.org/markup/index.html > > for sphinx-specific markup constructs. > > thanks, > --titus > -- > C. Titus Brown, ctb at msu.edu > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100707/05d45492/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4