Having to declare database path as static global is harmful
Docs:
- http://peewee.readthedocs.org/en/latest/peewee/cookbook.html#deferring-initialization
- http://peewee.readthedocs.org/en/latest/peewee/cookbook.html#dynamically-defining-a-database

>  If the only way to use it is with globals, I don't think I can use peewee at all and I'll have to try something else.

To be honest, I don't want users with an attitude like yours.

It's a real problem for me that I have to hardcode the path to the database as a global. This basically makes it impossible to use peewee in a library where I expect to have the database path passed to me.

I can work around hardcoding the value by gymnastics stuffing a value into a global location before I import peewee, but it's still global so it's impossible to create two separate database instances using peewee (e.g. in a library or a blueprint).

I expected it to be possible to use peewee based on the database instance, e.g. something like:

``` python
class Page(Model):
    title = CharField()
    content = TextField()

def get_db(path):
    db = SqliteDatabase(path)
    db.create_table(Page)
    return db

def add_page(db, title, content):
    p = db.create(Page, title=title, content=content)
    p.save()
```

Is it possible I missed a way to use peewee similar to this? If the only way to use it is with globals, I don't think I can use peewee at all and I'll have to try something else.

Thanks.
