Should I Use \"coding\" or \"encoding\" for Python Source Code Encoding Declaration?

Strict Adherence to Python Source Code Encoding Declaration

Question:

In the discussion regarding Python source code encoding declaration, as outlined in PEP 263, confusion arises from the use of the term "encoding" versus "coding". While the traditional form of declaration is:

#!/usr/bin/python
# -*- coding: <encoding name> -*-

Some developers have adopted a modified version:

#!/usr/bin/python
# -*- encoding: <encoding name> -*-

Answer:

According to the Python documentation, an encoding declaration is recognized if it matches the following regular expression:

coding[=:]\s*([-\w.]+),

This means that the "coding" part (with no prefix) is the recommended form, ensuring full compatibility with the Python specification.

Notably, the specific encoding declaration that you choose will depend on the editing software you use. Some editors, such as GNU Emacs, recognize the "coding" form by default, while others, such as Vim, require a prefix like "-*-".

Therefore, while you may use "encoding" in the first or second line of your Python file, it is advisable to adhere to the recommended "coding" declaration to maintain universal compatibility with both Python and your preferred editing software.

The above is the detailed content of Should I Use \"coding\" or \"encoding\" for Python Source Code Encoding Declaration?. For more information, please follow other related articles on the PHP Chinese website!