Skip to content
Projeler
Gruplar
Parçacıklar
Yardım
Yükleniyor...
Oturum aç / Kaydol
Gezinmeyi değiştir
C
cpython
Proje
Proje
Ayrıntılar
Etkinlik
Cycle Analytics
Depo (repository)
Depo (repository)
Dosyalar
Kayıtlar (commit)
Dallar (branch)
Etiketler
Katkıda bulunanlar
Grafik
Karşılaştır
Grafikler
Konular (issue)
0
Konular (issue)
0
Liste
Pano
Etiketler
Kilometre Taşları
Birleştirme (merge) Talepleri
0
Birleştirme (merge) Talepleri
0
CI / CD
CI / CD
İş akışları (pipeline)
İşler
Zamanlamalar
Grafikler
Paketler
Paketler
Wiki
Wiki
Parçacıklar
Parçacıklar
Üyeler
Üyeler
Collapse sidebar
Close sidebar
Etkinlik
Grafik
Grafikler
Yeni bir konu (issue) oluştur
İşler
Kayıtlar (commit)
Konu (issue) Panoları
Kenar çubuğunu aç
Batuhan Osman TASKAYA
cpython
Commits
5680b95b
Kaydet (Commit)
5680b95b
authored
Şub 16, 1995
tarafından
Guido van Rossum
Dosyalara gözat
Seçenekler
Dosyalara Gözat
İndir
Eposta Yamaları
Sade Fark
added list of restrictions
üst
bcc95825
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
36 additions
and
2 deletions
+36
-2
libshelve.tex
Doc/lib/libshelve.tex
+18
-1
libshelve.tex
Doc/libshelve.tex
+18
-1
No files found.
Doc/lib/libshelve.tex
Dosyayı görüntüle @
5680b95b
...
...
@@ -30,9 +30,26 @@ list = d.keys() # a list of all existing keys (slow!)
d.close() # close it
\end{verbatim}
Restrictions:
\begin{itemize}
\item
The choice of which database package will be used (e.g. dbm or gdbm)
depends on which interface is available. Therefore it isn't safe to
open the database directly using dbm. The database is also
(unfortunately) subject to the limitations of dbm, if it is used ---
this means that (the pickled representation of) the objects stored in
the database should be fairly small, and in rare cases key collisions
may cause the database to refuse updates.
\item
Dependent on the implementation, closing a persistent dictionary may
or may not be necessary to flush changes to disk.
Note:
\code
{
shelve
}
does not support
{
\em
concurrent
}
access to
\item
The
\code
{
shelve
}
module does not support
{
\em
concurrent
}
access to
shelved objects. Two programs should not try to simultaneously access
the same shelf.
\end{itemize}
Doc/libshelve.tex
Dosyayı görüntüle @
5680b95b
...
...
@@ -30,9 +30,26 @@ list = d.keys() # a list of all existing keys (slow!)
d.close() # close it
\end{verbatim}
Restrictions:
\begin{itemize}
\item
The choice of which database package will be used (e.g. dbm or gdbm)
depends on which interface is available. Therefore it isn't safe to
open the database directly using dbm. The database is also
(unfortunately) subject to the limitations of dbm, if it is used ---
this means that (the pickled representation of) the objects stored in
the database should be fairly small, and in rare cases key collisions
may cause the database to refuse updates.
\item
Dependent on the implementation, closing a persistent dictionary may
or may not be necessary to flush changes to disk.
Note:
\code
{
shelve
}
does not support
{
\em
concurrent
}
access to
\item
The
\code
{
shelve
}
module does not support
{
\em
concurrent
}
access to
shelved objects. Two programs should not try to simultaneously access
the same shelf.
\end{itemize}
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