Bugs item #1180392, was opened at 2005-04-10 17:55 Message generated for change (Comment added) made by rhettinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1180392&group_id=5470
Category: Documentation Group: Feature Request >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Leif K-Brooks (eurleif) Assigned to: Nobody/Anonymous (nobody) Summary: StringIO's docs should mention overwriting of initial value/ Initial Comment: StringIO's initial file position is always set to 0, rather than being set to the length of the initial text. This isn't mentioned in the documentation, which could cause confusion. I've attached some text the docs could use. ---------------------------------------------------------------------- >Comment By: Raymond Hettinger (rhettinger) Date: 2005-04-10 20:04 Message: Logged In: YES user_id=80475 Okay, I added an explicit comment that the initial file position is zero even when the object has been initialized with a string. FWIW, I recommend not using initialization when also using a write method. That will not allow a seemless conversion to cStringIO where intialized objects are read-only. A more scalable technique is to create an empty object and then call write() to initialize it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1180392&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
