c2c-oerpscenario team mailing list archive

["Vo Minh Thu \(OpenERP\)" <796789@xxxxxxxxxxxxxxxxxx>]

Cristian,

Quoting PEP 0263:
    More precisely, the first or second line must match the regular
    expression "coding[:=]\s*([-\w.]+)". The first group of this
    expression is then interpreted as encoding name.

Just above that paragraph, some examples are given, e.g.:
    #!/usr/bin/python
    # vim: set fileencoding=<encoding name> :

Maybe your comment is a general comment; I fail to see how it relates to
this bug report.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/796789

Title:
  PEP 0263 - coding (instead of encoding)

Status in OpenERP Modules (addons):
  Opinion
Status in OpenERP GTK Client:
  Opinion
Status in OpenERP Web Client:
  Opinion
Status in OpenERP Server:
  Opinion

Bug description:
  IMHO
  http://www.python.org/dev/peps/pep-0263/
  and
  http://www.python.org/dev/peps/pep-3120/

  suggest to use
  #!/usr/bin/python
  # -*- coding: <encoding name> -*-
  instead of 
  # -*- encoding: <encoding name> -*-

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/796789/+subscriptions