This is a common issue and originates from when Python changed some of its string mechanics from version 2 to 3. This error occurs when you try to base64 encode or decode a string instead of an appropriate bytes-like object. > encoded = base64.TypeError: a bytes-like object is required, not 'str' encodestring() returns a string containing one or more lines of base64-encoded data always including an extra trailing newline ( '\n').Īn example usage of the module: > import base64 base64.encodestring(s)Įncode the string s, which can contain arbitrary binary data, and return a string containing one or more lines of base64-encoded data.
#BASE64 ENCODING PYTHON PLUS#
encode() returns the encoded data plus a trailing newline character ( '\n'). input will be read until input.read() returns an empty string. input and output must either be file objects or objects that mimic the file object interface. base64.encode(input, output)Įncode the contents of the input file and write the resulting base64 encoded data to the output file. codestring(s)ĭecode the string s, which must contain one or more lines of base64 encoded data, and return a string containing the resulting binary data.
The legacy interface: code(input, output)ĭecode the contents of the input file and write the resulting binary data to the output file. A TypeError is raised if s were incorrectly padded or if there are non-alphabet characters present in the string. A TypeError is raised if s is incorrectly padded or if there are non-alphabet characters present in the string. For security purposes the default is None, so that 0 and 1 are not allowed in the input. The optional argument map01 when not None, specifies which letter the digit 1 should be mapped to (when map01 is not None, the digit 0 is always mapped to the letter O). RFC 3548 allows for optional mapping of the digit 0 (zero) to the letter O (oh), and for optional mapping of the digit 1 (one) to either the letter I (eye) or letter L (el). For security purposes, the default is False. Optional casefold is a flag specifying whether a lowercase alphabet is acceptable as input. base64.b32encode(s)Įncode a string using Base32. base64.urlsafe_b64decode(s)ĭecode string s using the URL- and filesystem-safe alphabet, which substitutes - instead of + and _ instead of / in the standard Base64 alphabet. base64.urlsafe_b64encode(s)Įncode string s using the URL- and filesystem-safe alphabet, which substitutes - instead of + and _ instead of / in the standard Base64 alphabet. base64.standard_b64decode(s)ĭecode string s using the standard Base64 alphabet. base64.standard_b64encode(s)Įncode string s using the standard Base64 alphabet. Characters that are neither in the normal base-64 alphabet nor the alternative alphabet are discarded prior to the padding check. A TypeError is raised if s is incorrectly padded. Optional altchars must be a string of at least length 2 (additional characters are ignored) which specifies the alternative alphabet used instead of the + and / characters. The default is None, for which the standard Base64 alphabet is used. generate URL or filesystem safe Base64 strings. Optional altchars must be a string of at least length 2 (additional characters are ignored) which specifies an alternative alphabet for the + and / characters. The modern interface, which was introduced in Python 2.4, provides: base64.b64encode(s) The legacy interface provides for encoding and decoding to and from file-like objects as well as strings, but only using the Base64 standard alphabet. The modern interface supports encoding and decoding string objects using both base-64 alphabets defined in RFC 3548 (normal, and URL- and filesystem-safe). There are two interfaces provided by this module. The encoding algorithm is not the same as the uuencode program. This standard defines the Base16, Base32, and Base64 algorithms for encoding and decoding arbitrary binary strings into text strings that can be safely sent by email, used as parts of URLs, or included as part of an HTTP POST request. This module provides data encoding and decoding as specified in RFC 3548.
Base64 - RFC 3548: Base16, Base32, Base64 Data Encodings
0 kommentar(er)
