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
bf3a7528
Commit
bf3a7528
authored
May 12, 2003
by
Raymond Hettinger
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix minor typos.
parent
73414a27
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
5 additions
and
5 deletions
+5
-5
Doc/lib/liblocale.tex
Doc/lib/liblocale.tex
+2
-2
Doc/lib/libmimetools.tex
Doc/lib/libmimetools.tex
+1
-1
Doc/lib/libpyexpat.tex
Doc/lib/libpyexpat.tex
+1
-1
Doc/lib/librepr.tex
Doc/lib/librepr.tex
+1
-1
No files found.
Doc/lib/liblocale.tex
View file @
bf3a7528
...
...
@@ -426,8 +426,8 @@ threads that happen to run before the settings have been restored.
If, when coding a module for general use, you need a locale
independent version of an operation that is affected by the locale
(
e.g.
\function
{
string.lower()
}
, or certain formats used with
\function
{
time.strftime()
}
)
)
, you will have to find a way to do it
(
such as
\function
{
string.lower()
}
, or certain formats used with
\function
{
time.strftime()
}
), you will have to find a way to do it
without using the standard library routine. Even better is convincing
yourself that using locale settings is okay. Only as a last resort
should you document that your module is not compatible with
...
...
Doc/lib/libmimetools.tex
View file @
bf3a7528
...
...
@@ -88,7 +88,7 @@ This is a list of strings. For parameters of the form
\begin{methoddesc}
{
getparam
}{
name
}
Return the
\var
{
value
}
of the first parameter (as returned by
\method
{
getplist()
}
of the form
\samp
{
\var
{
name
}
=
\var
{
value
}}
for the
\method
{
getplist()
}
)
of the form
\samp
{
\var
{
name
}
=
\var
{
value
}}
for the
given
\var
{
name
}
. If
\var
{
value
}
is surrounded by quotes of the form
`
\code
{
<
}
...
\code
{
>
}
' or `
\code
{
"
}
...
\code
{
"
}
', these are removed.
\end{methoddesc}
...
...
Doc/lib/libpyexpat.tex
View file @
bf3a7528
...
...
@@ -580,7 +580,7 @@ entity instead of an internal entity.
\begin{datadescni}
{
XML
_
ERROR
_
BAD
_
CHAR
_
REF
}
A character reference referred to a character which is illegal in XML
(for example, character
\code
{
0
}
, or `
\code
{
\&\#
0;
}
'.
(for example, character
\code
{
0
}
, or `
\code
{
\&\#
0;
}
'
)
.
\end{datadescni}
\begin{datadescni}
{
XML
_
ERROR
_
BINARY
_
ENTITY
_
REF
}
...
...
Doc/lib/librepr.tex
View file @
bf3a7528
...
...
@@ -96,7 +96,7 @@ and methods which format specific object types.
Formatting methods for specific types are implemented as methods
with a name based on the type name. In the method name,
\var
{
type
}
is replaced by
\code
{
string.join(string.split(type(
\var
{
obj
}
).
__
name
__
, '
_
')
}
.
\code
{
string.join(string.split(type(
\var
{
obj
}
).
__
name
__
, '
_
')
)
}
.
Dispatch to these methods is handled by
\method
{
repr1()
}
.
Type-specific methods which need to recursively format a value
should call
\samp
{
self.repr1(
\var
{
subobj
}
,
\var
{
level
}
- 1)
}
.
...
...
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