➜

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 vstinner
Recipients brett.cannon, docs@python, eric.snow, ezio.melotti, joshpurvis, ncoghlan, r.david.murray, vstinner
Date 2016-06-27.16:50:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZdHRPEDfFCAL_wW19kHMXZcycSSBJAcdNDYDBPvjJ0AA@mail.gmail.com>
In-reply-to <1467045221.68.0.297559326706.issue27387@psf.upfronthosting.co.za>
Content 
> Maybe it is worth adding a warning to that section of the 2.7 docs about implicit imports in general and encode/decode in particular?

Ok to add a note to str.encode and str.decode methods to explain that
an import is needed the first time that an encoding is used.

I'm not ok for a warning, we should not discourage developers to use
these methods! They are not dangerous by themself.
History
Date User Action Args
2016-06-27 16:50:39vstinnersetrecipients: + vstinner, brett.cannon, ncoghlan, ezio.melotti, r.david.murray, docs@python, eric.snow, joshpurvis
2016-06-27 16:50:39vstinnerlinkissue27387 messages
2016-06-27 16:50:39vstinnercreate