适用于Appengine数据存储区的Google Contact的Python模型

Question

I would like to save contacts on AppEngine datastore from the Google API v3 . I want to know what is the best way to store these data and especially if there is already a model!

Looking at the sources of gdata , I found a very interesting beginning. But this is the modeling of the data only in python and not for the datastore.

Question : Is this model already exists in python?

If not:

Question : What is the best way to start from scratch?

Beginning example of a contact in Python :

class Contact(db.Model):
    """
    https://developers.google.com/gdata/docs/2.0/elements?hl=fr#gdContactKind
    https://developers.google.com/appengine/docs/python/datastore/datamodeling
    """

    content = db.Text()
    """atom:content Notes about the contact."""

    link = db.ListProperty(Link,indexed=False,default=[])
    """atom:link*   Links to related information. Specifically, atom:link[@rel='alternate'] links to an HTML page describing the contact."""

    title = db.StringProperty()
    """atom:title   Contact's name. This field is read only. To modify the contact's name, see gd:name."""

    email = db.ListProperty(Email,indexed=False,default=[])
    """gd:email*    Email addresses."""

    """etc..."""

class Link(db.Model):
    """
    Link
    """
    link = db.LinkProperty()

class Email(db.Model):
    """
    Email
    """
    email_address = db.EmailProperty()


class EmailImParent(db.Model):
  address = db.StringProperty()
  label = db.StringProperty()
  rel = db.StringProperty()
  primary = db.StringProperty()


class Email(db.Model,EmailImParent):
  """
  The gd:email element.
  """
  email =  db.EmailProperty()
  display_name = db.StringProperty()

Answer 1

I think everyone is rolling their own. It is easy enough to do, you can take a look at AE-BaseApp/Python and check out the code from the Github link. I have some new code that will be updated in the near future that contains some improvements to the contact model. (the updated code is currently broken due to hacking to get logins working on both http and https here )