Serhiy Storchaka
|
4fc7942118
|
Issue #28847: A deprecation warning is now emitted if the index file is missed
and recreated in the 'r' and 'w' modes (will be an error in future Python
releases).
|
2016-12-07 11:11:12 +02:00 |
Serhiy Storchaka
|
520348e5c0
|
Issue #28847: dbm.dumb now supports reading read-only files and no longer
writes the index file when it is not changed.
|
2016-12-07 11:00:06 +02:00 |
Serhiy Storchaka
|
028ace1ccb
|
Issue #28847: dbm.dumb now supports reading read-only files and no longer
writes the index file when it is not changed.
|
2016-12-07 10:56:39 +02:00 |
Serhiy Storchaka
|
0122ae9ac8
|
Issue #21708: Deprecated dbm.dumb behavior that differs from common dbm
behavior: creating a database in 'r' and 'w' modes and modifying a database
in 'r' mode.
|
2016-07-06 12:21:58 +03:00 |
Serhiy Storchaka
|
2116b12da5
|
Issue #23865: close() methods in multiple modules now are idempotent and more
robust at shutdown. If needs to release multiple resources, they are released
even if errors are occured.
|
2015-04-10 13:29:28 +03:00 |
Serhiy Storchaka
|
7e7a3dba5f
|
Issue #23865: close() methods in multiple modules now are idempotent and more
robust at shutdown. If needs to release multiple resources, they are released
even if errors are occured.
|
2015-04-10 13:24:41 +03:00 |
Serhiy Storchaka
|
23edd49e5b
|
Issue #22885: Fixed arbitrary code execution vulnerability in the dbm.dumb
module. Original patch by Claudiu Popa.
|
2015-02-16 00:32:41 +02:00 |
Serhiy Storchaka
|
74eb8b2d1a
|
Issue #22885: Fixed arbitrary code execution vulnerability in the dbm.dumb
module. Original patch by Claudiu Popa.
|
2015-02-16 00:30:43 +02:00 |
Serhiy Storchaka
|
e5243cc713
|
Issue #21729: Used the "with" statement in the dbm.dumb module to ensure
files closing. Patch by Claudiu Popa.
|
2014-06-25 20:37:30 +03:00 |
Serhiy Storchaka
|
65c623de74
|
Issue #21729: Used the "with" statement in the dbm.dumb module to ensure
files closing. Patch by Claudiu Popa.
|
2014-06-25 20:35:31 +03:00 |
Serhiy Storchaka
|
b398d33c65
|
Issue #18039: dbm.dump.open() now always creates a new database when the
flag has the value 'n'. Patch by Claudiu Popa.
|
2014-06-10 21:16:00 +03:00 |
Serhiy Storchaka
|
12c575f2f6
|
Restore performance of some dumb database methods (regression introduced by #19385).
|
2014-05-28 18:49:52 +03:00 |
Benjamin Peterson
|
e3083d3ad5
|
make operations on closed dumb databases raise a consistent exception (closes #19385)
Patch by Claudiu Popa.
|
2014-04-26 16:56:52 -04:00 |
Nick Coghlan
|
c610aba1ed
|
Close #19282: Native context management in dbm
|
2013-11-17 15:59:51 +10:00 |
Andrew Svetlov
|
f7a17b48d7
|
Replace IOError with OSError (#16715)
|
2012-12-25 16:47:37 +02:00 |
Andrew Svetlov
|
ad28c7f9da
|
Issue #16706: get rid of os.error
|
2012-12-18 22:02:39 +02:00 |
Georg Brandl
|
d9e833c70a
|
#6045: provide at least get() and setdefault() for all dbm modules.
|
2010-12-04 09:14:36 +00:00 |
Brett Cannon
|
2b5d6ebfe5
|
dbm.dumb was opening files without specifying the encoding. Caused problem on
at least OS X where the default is macroman.
Closes issue #4382.
|
2008-11-24 21:09:58 +00:00 |
Brett Cannon
|
58425d3103
|
Make dbm.dumb encode strings as UTF-8. Also fix it so it accepts bytes and
strings.
Closes issue #3799.
|
2008-11-21 00:17:53 +00:00 |
Georg Brandl
|
0a7ac7d70d
|
Create the dbm package from PEP 3108. #2881.
|
2008-05-26 10:29:35 +00:00 |