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
9463de20
Commit
9463de20
authored
Apr 11, 1998
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document cPickle and cStringIO.
parent
10032ebb
Changes
6
Hide whitespace changes
Inline
Side-by-side
Showing
6 changed files
with
68 additions
and
22 deletions
+68
-22
Doc/lib/libpickle.tex
Doc/lib/libpickle.tex
+18
-0
Doc/lib/libstrio.tex
Doc/lib/libstrio.tex
+16
-0
Doc/lib/libundoc.tex
Doc/lib/libundoc.tex
+0
-11
Doc/libpickle.tex
Doc/libpickle.tex
+18
-0
Doc/libstrio.tex
Doc/libstrio.tex
+16
-0
Doc/libundoc.tex
Doc/libundoc.tex
+0
-11
No files found.
Doc/lib/libpickle.tex
View file @
9463de20
...
...
@@ -270,3 +270,21 @@ registration}
\seemodule
{
shelve
}{
indexed databases of objects; uses
\module
{
pickle
}}
\end{seealso}
\section
{
Built-in Module
\module
{
cPickle
}}
\bimodindex
{
cPickle
}
\label
{
module-cPickle
}
% This section was written by Fred L. Drake, Jr. <fdrake@acm.org>
The
\module
{
cPickle
}
module provides a similar interface and identical
functionality as the
\module
{
pickle
}
module, but can be up to 1000
times faster since it is implemented in
\C
{}
. The only other
important difference to note is that
\function
{
Pickler()
}
and
\function
{
Unpickler()
}
are functions and not classes, and so cannot be
subclassed. This should not be an issue in most cases.
The format of the pickle data is identical to that produced using the
\module
{
pickle
}
module, so it is possible to use
\module
{
pickle
}
and
\module
{
cPickle
}
interchangably with existing pickles.
Doc/lib/libstrio.tex
View file @
9463de20
...
...
@@ -24,3 +24,19 @@ Retrieve the entire contents of the ``file'' at any time before the
\begin{methoddesc}
{
close
}{}
Free the memory buffer.
\end{methoddesc}
\section
{
Built-in Module
\module
{
cStringIO
}}
\bimodindex
{
cStringIO
}
\label
{
module-cStringIO
}
% This section was written by Fred L. Drake, Jr. <fdrake@acm.org>
The module
\module
{
cStringIO
}
provides an interface similar to that of
the
\module
{
StringIO
}
module. Heavy use of
\class
{
StringIO.StringIO
}
objects can be made more efficient by using the function
\function
{
StringIO()
}
from this module instead.
Since this module provides a factory function which returns objects of
built-in types, there's no way to build your own version using
subclassing. Use the original
\module
{
StringIO
}
module in that case.
Doc/lib/libundoc.tex
View file @
9463de20
...
...
@@ -7,17 +7,6 @@ them! (The idea and most contents for this chapter were taken from a
posting by Fredrik Lundh; I have revised some modules' status.)
\section
{
Fundamental, and pretty straightforward to document
}
\begin{description}
\item
[cPickle.c]
--- mostly the same as pickle but no subclassing
\item
[cStringIO.c]
--- mostly the same as StringIO but no subclassing
\end{description}
\section
{
Frameworks; somewhat harder to document, but well worth the effort
}
\begin{description}
...
...
Doc/libpickle.tex
View file @
9463de20
...
...
@@ -270,3 +270,21 @@ registration}
\seemodule
{
shelve
}{
indexed databases of objects; uses
\module
{
pickle
}}
\end{seealso}
\section
{
Built-in Module
\module
{
cPickle
}}
\bimodindex
{
cPickle
}
\label
{
module-cPickle
}
% This section was written by Fred L. Drake, Jr. <fdrake@acm.org>
The
\module
{
cPickle
}
module provides a similar interface and identical
functionality as the
\module
{
pickle
}
module, but can be up to 1000
times faster since it is implemented in
\C
{}
. The only other
important difference to note is that
\function
{
Pickler()
}
and
\function
{
Unpickler()
}
are functions and not classes, and so cannot be
subclassed. This should not be an issue in most cases.
The format of the pickle data is identical to that produced using the
\module
{
pickle
}
module, so it is possible to use
\module
{
pickle
}
and
\module
{
cPickle
}
interchangably with existing pickles.
Doc/libstrio.tex
View file @
9463de20
...
...
@@ -24,3 +24,19 @@ Retrieve the entire contents of the ``file'' at any time before the
\begin{methoddesc}
{
close
}{}
Free the memory buffer.
\end{methoddesc}
\section
{
Built-in Module
\module
{
cStringIO
}}
\bimodindex
{
cStringIO
}
\label
{
module-cStringIO
}
% This section was written by Fred L. Drake, Jr. <fdrake@acm.org>
The module
\module
{
cStringIO
}
provides an interface similar to that of
the
\module
{
StringIO
}
module. Heavy use of
\class
{
StringIO.StringIO
}
objects can be made more efficient by using the function
\function
{
StringIO()
}
from this module instead.
Since this module provides a factory function which returns objects of
built-in types, there's no way to build your own version using
subclassing. Use the original
\module
{
StringIO
}
module in that case.
Doc/libundoc.tex
View file @
9463de20
...
...
@@ -7,17 +7,6 @@ them! (The idea and most contents for this chapter were taken from a
posting by Fredrik Lundh; I have revised some modules' status.)
\section
{
Fundamental, and pretty straightforward to document
}
\begin{description}
\item
[cPickle.c]
--- mostly the same as pickle but no subclassing
\item
[cStringIO.c]
--- mostly the same as StringIO but no subclassing
\end{description}
\section
{
Frameworks; somewhat harder to document, but well worth the effort
}
\begin{description}
...
...
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