<commit_before>======
LazyDB
======

LazyDB is a basic wrapper around the Python shelve flatfile dbm
module. LazyDB provides a couchdb/S3 like layer of abstraction around
shelve, allowing convenient access (read and write) to shelve without
sacrificing the convenience of writing pickled python objects to disk.

From the help(shelve) documentation: A "shelf" is a persistent,
dictionary-like object.  The difference with dbm databases is that the
values (not the keys!) in a shelf can be essentially arbitrary Python
objects -- anything that the "pickle" module can handle.  This
includes most class instances, recursive data types, and objects
containing lots of shared sub-objects.  The keys are ordinary strings.

Disclaimer: I wouldn't suggest using this module for production
projects as I predict it having difficulty scaling. LazyDB is ideal
for supporting smaller projects with light data in which the
programmer must move quickly and intends to implement an alternate db
solution sooner rather than later. The intent is to provide a more
elegant interface for utilizing the shelve module, not to create an
efficient replacement.

Typical usage often looks like this::

    #!/usr/bin/env Python
    
    from lazydb.lazydb import Db

    class LazyUser:
    	  def __init__(self, name):
	      self.name = name

    db = Db('mydb', '/home/user/')
    db.put('user', LazyUser('lazybones'))
    u = db.get('user')
    u.name

Contributors
============

Currently, this project is maintained by Mek.
<commit_msg>Updated README.md docs to reflect latest class changes.<commit_after>======
LazyDB
======

LazyDB is a basic wrapper around the Python shelve flatfile dbm
module. LazyDB provides a couchdb/S3 like layer of abstraction around
shelve, allowing convenient access (read and write) to shelve without
sacrificing the convenience of writing pickled python objects to disk.

From the help(shelve) documentation: A "shelf" is a persistent,
dictionary-like object.  The difference with dbm databases is that the
values (not the keys!) in a shelf can be essentially arbitrary Python
objects -- anything that the "pickle" module can handle.  This
includes most class instances, recursive data types, and objects
containing lots of shared sub-objects.  The keys are ordinary strings.

Disclaimer: I wouldn't suggest using this module for production
projects as I predict it having difficulty scaling. LazyDB is ideal
for supporting smaller projects with light data in which the
programmer must move quickly and intends to implement an alternate db
solution sooner rather than later. The intent is to provide a more
elegant interface for utilizing the shelve module, not to create an
efficient replacement.

Typical usage often looks like this::

    #!/usr/bin/env Python
    
    from lazydb.lazydb import Db

    class LazyUser:
    	  def __init__(self, name):
	      self.name = name

    db = Db('/home/user/db')
    db.put('user', LazyUser('lazybones'))
    u = db.get('user')
    u.name

Contributors
============

Currently, this project is maintained by Mek.

{'fraction_non_alphanumeric': 0.06798959011060507, 'fraction_numerical': 0.0006506180871828237, 'mean_word_length': 4.150753768844221, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5229629', 'n_tokens_mistral': 831, 'n_tokens_neox': 785, 'n_words': 412}