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 jafo
Recipients gvanrossum, jafo
Date 2007-09-17.10:48:14
SpamBayes Score 0.0042105475
Marked as misclassified No
Message-id <1190026095.63.0.197250105942.issue1150@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is a patch that fixes "writeable".  I'm thinking, close this if
the patch looks ok, and open another for a general "identify
non-englishisms" ticket, once they're identified a ticket could be
opened to fix them.

I fixed only the PyBUF instances but also documents and comments and doc
strings and printfs where it occurred.  Yes?  Let me know if it looks
good to commit.

Does this need a fix in 2to3?
Files
File name Uploaded
py3k-trunk-writeable.patch jafo, 2007-09-17.10:48:14
History
Date User Action Args
2007-09-17 10:48:15jafosetspambayes_score: 0.00421055 -> 0.0042105475
recipients: + jafo, gvanrossum
2007-09-17 10:48:15jafosetspambayes_score: 0.00421055 -> 0.00421055
messageid: <1190026095.63.0.197250105942.issue1150@psf.upfronthosting.co.za>
2007-09-17 10:48:15jafolinkissue1150 messages
2007-09-17 10:48:14jafocreate