- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message69047
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 | mark |
|---|---|
| Recipients | mark |
| Date | 2008-07-01.15:39:11 |
| SpamBayes Score | 0.026122583 |
| Marked as misclassified | No |
| Message-id | <1214926752.5.0.120483296731.issue3252@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I know it is almost certainly too late, but I think a lot of people will be confused by str.decode() and bytes.encode() (or was that the other way around)? Calling the methods str.tobytes() and bytes.tostr() (or nicer, str.to_bytes() and bytes.to_str()) would be hard to confuse and IMO will lead to fewer bug reports and complaints once Python 3.0 final comes out. And there is a kind of precedent in that threading.isDaemon() became threading.is_daemon() between 30a5 and 30b1. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-07-01 15:39:12 | mark | set | spambayes_score: 0.0261226 -> 0.026122583 recipients: + mark |
| 2008-07-01 15:39:12 | mark | set | spambayes_score: 0.0261226 -> 0.0261226 messageid: <1214926752.5.0.120483296731.issue3252@psf.upfronthosting.co.za> |
| 2008-07-01 15:39:11 | mark | link | issue3252 messages |
| 2008-07-01 15:39:11 | mark | create | |

