Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2001-July/016044.html below:

Defining Python Source Code Encodings

• Previous message: [Python-Dev] PEP: Defining Python Source Code Encodings
• Next message: [Python-Dev] Re: PEP: Defining Python Source Code Encodings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"M.-A. Lemburg" <mal@lemburg.com> writes:

> - which format to use for the magic comment, e.g.
> 
>   * Emacs style:
> 
>       #!/usr/bin/python
>       # -*- encoding = 'utf-8' -*-

Emacs already has a name for this; you'd write that

# -*- coding: utf-8; -*-

Seems reasonable to me.

Cheers,
M.

-- 
  We've had a lot of problems going from glibc 2.0 to glibc 2.1.
  People claim binary compatibility.  Except for functions they
  don't like.                       -- Peter Van Eynde, comp.lang.lisp

• Previous message: [Python-Dev] PEP: Defining Python Source Code Encodings
• Next message: [Python-Dev] Re: PEP: Defining Python Source Code Encodings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4