namlook

By design, all Documents accessed via db (`db.Document.find()`) are already instanciated. So you don't need to call @classmethod. Your User class would look like : ``` python class User(Document): __collection__...

Well, in this case: ``` python class User(Document): __collection__ = 'users' structure = { 'id': int, 'screen_name': unicode, 'token': unicode, 'secret': unicode, } use_dot_notation = True def create_or_update_by_id(self, id, screen_name,...

Yes, I know this is weird and completely un-Pythonic but this design inherits from a (very old) historical design. I tried to refactorise but the bad was already done (ie...

Hi, I miss real falling test case in order to fix the problem. Can you provide one ?

Nop, this issue is still in 0.8.3. If you really need it, this is the patch to add to your model: ``` python from mongokit import Document as MongoDocument class...

Indeed, this would be nice feature. Feel free to make a pull request. And please, don't forget to add tests and update the doc :)

Hi, do you have any test cases so I can reproduce the issue ?

Hi, I'm glad you ask. The last two years, I was into the creation of a startup (http://www.elkorado.com).The project was built on top of MongoKit. This year, a big client...

I added @eneepo and @gulbinas as collaborators for this repository. You're in charge now guys, you can start branches and merge pull requests. Tell me if you have any troubles...

I reopen this issue as it seems the project needs more maintainers... (I also added a note at the beginning of the README.)