Skip to content

judy2k/kylie

Repository files navigation

Kylie

https://coveralls.io/repos/judy2k/kylie/badge.svg?branch=master Code Health

Kylie provides mappings between JSON data structures and Python objects. It provides a reasonable amount of power with only a tiny bit of magic, and it has 100% code coverage.

Features

Example

class SpanishInquisitionModel(Model):
    inquisition_id = Attribute('id')
    expected = Attribute(python_type=bool, serialized_type=int)

Then:

>>> surprise = SpanishInquisitionModel(inquisition_id=1234, expected=False)
>>> surprise.inquisition_id
1234
>>> surprise.serialize()
{'id': 1234, expected=0}

Note that the attribute inquisition_id becomes the dict key "id", and expected is mapped to 0 instead of False.

We can now take this dict, dumps it to JSON, and somewhere else call the following on the json_data (which is a dict returned from loads):

>>> my_surprise = SpanishInquisitionModel.deserialize(json_data)
>>> my_surprise.inquisition_id
1234
>>> my_surprise.expected
False

Kylie supports nested models, so you can embed other Model instances inside the data, and Kylie will manage serialization and deserialization of them for you.

Non-Features

So what doesn't Kylie do yet? Well, there are a few things, because it's very new:

  • Doesn't have any mechanism for validation. I plan to add this once I decide the best way to do it. Ideas welcome!
  • No post-deserialize option, unless you do it yourself. This would allow wiring up of objects that are referred to by id and provided elsewhere in the serialized data-structure, for example.

So, still some important things to do, but I think Kylie is already useful.

Why is it called Kylie?

Back in the late 80's (I'm old!) Kylie and Jason were today's Kim and Kanye. This Kylie works well with JSON. Geddit?

http://upload.wikimedia.org/wikipedia/en/1/1a/KylieEspeciallyForYouCover.png

About

Kylie maps between Model objects and JSON data structures.

Resources

License

Stars

Watchers

Forks

Packages