Message 66040 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	amaury.forgeotdarc
Recipients	amaury.forgeotdarc, tempname1234
Date	2008-05-01.20:33:05
SpamBayes Score	0.01177615
Marked as misclassified	No
Message-id	<1209673989.98.0.922020409866.issue2730@psf.upfronthosting.co.za>
In-reply-to

Content
This is a duplicate of issue1394612, which was closed as "invalid". See the discussion there: - "in standard C mixing reads with writes yields undefined behavior [...] If you want defined behavior, then, for example, add >>> f.seek(0) between your write() and read() calls.""" BTW, python 3.0 has a new implementation of the I/O stack, which does not use fopen, and does not have this problem.

This is a duplicate of issue1394612, which was closed as "invalid". See
the discussion there:

- "in standard C mixing reads with writes yields undefined behavior [...]
If you want defined behavior, then, for example, add
>>> f.seek(0)
between your write() and read() calls."""

BTW, python 3.0 has a new implementation of the I/O stack, which does
not use fopen, and does not have this problem.

History
Date	User	Action	Args
2008-05-01 20:33:11	amaury.forgeotdarc	set	spambayes_score: 0.0117762 -> 0.01177615 recipients: + amaury.forgeotdarc, tempname1234
2008-05-01 20:33:10	amaury.forgeotdarc	set	spambayes_score: 0.0117762 -> 0.0117762 messageid: <1209673989.98.0.922020409866.issue2730@psf.upfronthosting.co.za>
2008-05-01 20:33:07	amaury.forgeotdarc	link	issue2730 messages
2008-05-01 20:33:06	amaury.forgeotdarc	create