Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
ba03c45f
Commit
ba03c45f
authored
Jul 07, 2003
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
- explain about making Python scripts executable on Unix in more
detail - fix minor markup nit
parent
4cdb61d3
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
2 deletions
+13
-2
Doc/tut/tut.tex
Doc/tut/tut.tex
+13
-2
No files found.
Doc/tut/tut.tex
View file @
ba03c45f
...
...
@@ -299,13 +299,24 @@ executable, like shell scripts, by putting the line
(assuming that the interpreter is on the user's
\envvar
{
PATH
}
) at the
beginning of the script and giving the file an executable mode. The
\samp
{
\#
!
}
must be the first two characters of the file. Note that
\samp
{
\#
!
}
must be the first two characters of the file. On some
platforms, this first line must end with a
\UNIX
-style line ending
(
\character
{
\e
n
}
), not a Mac OS (
\character
{
\e
r
}
) or Windows
(
\character
{
\e
r
\e
n
}
) line ending. Note that
the hash, or pound, character,
\character
{
\#
}
, is used to start a
comment in Python.
The script can be given a executable mode, or permission, using the
\program
{
chmod
}
command:
\begin{verbatim}
$
chmod
+
x myscript.py
\end
{
verbatim
}
% $ <-- bow to font-lock
\subsection
{
Source Code Encoding
}
It is possible to use encodings different than
ASCII
in Python source
It is possible to use encodings different than
\ASCII
{}
in Python source
files. The best way to do it is to put one more special comment line
right after the
\code
{
\#
!
}
line to define the source file encoding:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment