Reinhold Birkenfeld wrote: > > I can only speak for my own experience, but maybe it will help. I > > once tried to help fix a piece of the python docs. The description > > of Py_UNICODE on <http://docs.python.org/api/unicodeObjects.html> was > > -- and still is -- incorrect. > > The current docs were released on September 28. They are not updated until > the next Python release, so that's probably why your patch doesn't show up there. > > That may not be a good thing. Documentation fixes should go online much > quicker than with every Python release, or am I mistaken? as was noted at the top of this thread, the "trunk" documentation on python.org is even older. a bit further down the thread, Trent Mick came to the rescue: http://trentm.com/python/ </F>
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