Python set encoding utf8

How to Enable UTF-8 in Python ?

In this post , we will see — How to Enable UTF-8 in Python.

• In Python 3 UTF-8 is the default source encoding
• When the encoding is not correctly set-up , it is commonly seen to throw an «»UnicodeDecodeError: ‘ascii’ codec can’t encode» error
• Python string function uses the default character encoding .
  • Check sys.stdout.encoding value — sometimes it is set to «None».
  • The encoding default can be located in — /etc/default/locale
  • The default is defined by the variables LANG, LC_ALL, LC_CTYPE
  • Check the values set against these variables.
    • For example — If the default is UTF-8 , these would be LANG=»UTF-8″ , LC_ALL=»UTF-8″ , LC_CTYPE=»UTF-8″

     $ export PYTHONIOENCODING=utf8 

    • Set the environment variables in /etc/default/locale . This way the system`s default locale encoding is set to the UTF-8 format.

     LANG="UTF-8" or "en\_US.UTF-8" LC\_ALL="UTF-8" or "en\_US.UTF-8" LC\_CTYPE="UTF-8" or "en\_US.UTF-8" 

     Or use command line export LC\_ALL="UTF-8" export LC\_ALL="UTF-8" export LC\_CTYPE="UTF-8" 

     a = b = str1.encode('utf-8') print (a.encode('utf-8')) print (b) 

     a = b = str1.encode('utf-8', 'ignore').decode('utf-8') print (b) 

     \# encoding=utf8 from \_\_future\_\_ import unicode\_literals import sys reload(sys) sys.setdefaultencoding('utf8') 

     import os import locale os.environ\["PYTHONIOENCODING"\] = "utf-8" thisLocale=locale.setlocale(category=locale.LC\_ALL, locale="en\_GB.UTF-8") 

    • When you use IDLE (Python 2) and the file contains non-ASCII characters , then it will prompt you to add an encoding declaration, using the Emacs -*- style. This basically tells the text editor what codec to use.

     #!/usr/bin/env python # -\*- coding: utf-8 -\*- 

     #!/usr/bin/env python # coding: utf8 

    • If you encode with ascii an decide to throw out the unicode characters ,use the below option . In this example , unicode characters will be dropped from varB.

     varb = str1.encode('ascii', 'ignore').decode('ascii') print (varB) 

    Additional points :

    • UTF-8 properties —
      • Can handle any Unicode code point.
      • A string of ASCII text is also valid UTF-8 text.
      • UTF-8 is a byte oriented encoding. The encoding specifies that each character is represented by a specific sequence of one or more bytes. This avoids the byte-ordering issues that can occur with integer and word oriented encodings, like UTF-16 and UTF-32, where the sequence of bytes varies depending on the hardware on which the string was encoded.

      Other Interesting Reads —

      How to log an error in Python ?

      How to Code Custom Exception Handling in Python ?

      How to Handle Errors and Exceptions in Python ?

      How to Handle Bad or Corrupt records in Apache Spark ?

       Does Python use UTF 8, How do I encode utf8 in Python, How do I change encoding in Python, What is Character Set in Python, decode utf-8 python, convert string to unicode python 3, python utf-8 to ascii, python utf-8 header, python unicode to utf8, python encoding types, python unicode() function, python print utf-8, decode utf-8 python, convert string to unicode python 3, python utf-8 to ascii, python utf-8 header, python unicode to utf8, python encoding types, python unicode() function, python print utf-8, decode utf-8 python, python utf-8 header, convert string to unicode python, # -\*- coding: utf-8 -\*-, python utf-8 to ascii, python unicode() function, python unicode to utf8, python print utf-8,Does Python use UTF 8?,How do I encode utf8 in Python?,How do you encode a character in python?, How do I get Unicode in Python?, decode utf-8 python, python utf-8 header, convert string to unicode python, # -\*- coding: utf-8 -\*-, python utf-8 to ascii, python unicode() function, python unicode to utf8, python print utf-8, utf-8 in python, how to decode utf-8 in python, how to use utf-8 in python, how to convert string to utf-8 in python, how to encode a string to utf-8 in python, how to decode utf-8 in python 3,how to convert ascii to utf-8 in python, how to convert a file to utf-8 in python, how to convert iso-8859-1 to utf-8 in python, how to convert ansi to utf-8 in python, utf-8 python ,utf-8 encoding ,utf-8 characters ,utf-8 meaning ,utf-8 vs utf-16 ,utf-8 decoder ,utf-8 vs ascii ,utf-8 converter ,utf-8 character set ,utf-8 table, decode utf-8 python ,encoding utf-8 python ,python utf-8 header ,convert string to unicode python 3 ,python string to unicode ,python unicode to utf8 ,python encoding types ,python print utf-8, set utf 8 python, set default encoding utf-8 python 

      Источник

      PEP 263 – Defining Python Source Code Encodings

      This PEP proposes to introduce a syntax to declare the encoding of a Python source file. The encoding information is then used by the Python parser to interpret the file using the given encoding. Most notably this enhances the interpretation of Unicode literals in the source code and makes it possible to write Unicode literals using e.g. UTF-8 directly in an Unicode aware editor.

      Problem

      In Python 2.1, Unicode literals can only be written using the Latin-1 based encoding “unicode-escape”. This makes the programming environment rather unfriendly to Python users who live and work in non-Latin-1 locales such as many of the Asian countries. Programmers can write their 8-bit strings using the favorite encoding, but are bound to the “unicode-escape” encoding for Unicode literals.

      Proposed Solution

      I propose to make the Python source code encoding both visible and changeable on a per-source file basis by using a special comment at the top of the file to declare the encoding.

      To make Python aware of this encoding declaration a number of concept changes are necessary with respect to the handling of Python source code data.

      Defining the Encoding

      Python will default to ASCII as standard encoding if no other encoding hints are given.

      To define a source code encoding, a magic comment must be placed into the source files either as first or second line in the file, such as:

      or (using formats recognized by popular editors):

      #!/usr/bin/python # vim: set fileencoding= : 

      More precisely, the first or second line must match the following regular expression:

      The first group of this expression is then interpreted as encoding name. If the encoding is unknown to Python, an error is raised during compilation. There must not be any Python statement on the line that contains the encoding declaration. If the first line matches the second line is ignored.

      To aid with platforms such as Windows, which add Unicode BOM marks to the beginning of Unicode files, the UTF-8 signature \xef\xbb\xbf will be interpreted as ‘utf-8’ encoding as well (even if no magic encoding comment is given).

      If a source file uses both the UTF-8 BOM mark signature and a magic encoding comment, the only allowed encoding for the comment is ‘utf-8’. Any other encoding will cause an error.

      Examples

      These are some examples to clarify the different styles for defining the source code encoding at the top of a Python source file:

      With interpreter binary and using Emacs style file encoding comment:

      #!/usr/bin/python # -*- coding: latin-1 -*- import os, sys . #!/usr/bin/python # -*- coding: iso-8859-15 -*- import os, sys . #!/usr/bin/python # -*- coding: ascii -*- import os, sys . 

      # This Python file uses the following encoding: utf-8 import os, sys . 

      #!/usr/local/bin/python # coding: latin-1 import os, sys . 

      #!/usr/local/bin/python import os, sys . 

      #!/usr/local/bin/python # latin-1 import os, sys . 

      #!/usr/local/bin/python # # -*- coding: latin-1 -*- import os, sys . 

      #!/usr/local/bin/python # -*- coding: utf-42 -*- import os, sys . 

      Concepts

      The PEP is based on the following concepts which would have to be implemented to enable usage of such a magic comment:

      1. The complete Python source file should use a single encoding. Embedding of differently encoded data is not allowed and will result in a decoding error during compilation of the Python source code. Any encoding which allows processing the first two lines in the way indicated above is allowed as source code encoding, this includes ASCII compatible encodings as well as certain multi-byte encodings such as Shift_JIS. It does not include encodings which use two or more bytes for all characters like e.g. UTF-16. The reason for this is to keep the encoding detection algorithm in the tokenizer simple.
      2. Handling of escape sequences should continue to work as it does now, but with all possible source code encodings, that is standard string literals (both 8-bit and Unicode) are subject to escape sequence expansion while raw string literals only expand a very small subset of escape sequences.
      3. Python’s tokenizer/compiler combo will need to be updated to work as follows:
         1. read the file
         2. decode it into Unicode assuming a fixed per-file encoding
         3. convert it into a UTF-8 byte string
         4. tokenize the UTF-8 content
         5. compile it, creating Unicode objects from the given Unicode data and creating string objects from the Unicode literal data by first reencoding the UTF-8 data into 8-bit string data using the given file encoding

         Note that Python identifiers are restricted to the ASCII subset of the encoding, and thus need no further conversion after step 4.

         Implementation

         For backwards-compatibility with existing code which currently uses non-ASCII in string literals without declaring an encoding, the implementation will be introduced in two phases:

         1. Allow non-ASCII in string literals and comments, by internally treating a missing encoding declaration as a declaration of “iso-8859-1”. This will cause arbitrary byte strings to correctly round-trip between step 2 and step 5 of the processing, and provide compatibility with Python 2.2 for Unicode literals that contain non-ASCII bytes. A warning will be issued if non-ASCII bytes are found in the input, once per improperly encoded input file.
         2. Remove the warning, and change the default encoding to “ascii”.

         The builtin compile() API will be enhanced to accept Unicode as input. 8-bit string input is subject to the standard procedure for encoding detection as described above.

         If a Unicode string with a coding declaration is passed to compile() , a SyntaxError will be raised.

         SUZUKI Hisao is working on a patch; see [2] for details. A patch implementing only phase 1 is available at [1].

         Phases

         Implementation of steps 1 and 2 above were completed in 2.3, except for changing the default encoding to “ascii”.

         The default encoding was set to “ascii” in version 2.5.

         Scope

         This PEP intends to provide an upgrade path from the current (more-or-less) undefined source code encoding situation to a more robust and portable definition.

         References

         History

         • 1.10 and above: see CVS history
         • 1.8: Added ‘.’ to the coding RE.
         • 1.7: Added warnings to phase 1 implementation. Replaced the Latin-1 default encoding with the interpreter’s default encoding. Added tweaks to compile() .
         • 1.4 — 1.6: Minor tweaks
         • 1.3: Worked in comments by Martin v. Loewis: UTF-8 BOM mark detection, Emacs style magic comment, two phase approach to the implementation

         Copyright

         This document has been placed in the public domain.

         Источник

         Читайте также:  Как ограничить input html