Add, Remove, and query Relations

Add emailVerified to protected_attributes

Without this change, you will not be able to save users with getting an error code":105,"error":"the emailVerified key is a reserved word.

Update datatypes to check for circular pointer references. Change circul...

Update datatypes to check for circular pointer references. Change circular pointer references so that they return a string instead of pointer object for the secondary reference

Relational queries weren't possible because as_pointer was False from the Queryset, fixed and added test for relational query. Updated PyPI version.

Python3 support

Add master key header only if no user session is specified

Installation instructions

Added ParseBatcher class to execute batch create, update or delete operations with a single API call, including test cases and documentation. Also added ability to log in a user using Facebook or Twitter authorization.

Push and Installation Query seems to be working now. Removing from the list of "PLANNED" items.

breaking down of Push send into two distinct methods, Push.alert (for json data) and Push.message (for text). Uses 'where' as an optional variable to make specific queries, and pass any other optional parameters through **kw)

Thanks for the work. I will break down the "send text" and "send json" into two distinct methods (Push.message and Push.alert?)

Found out that User.signup was not actually returning a valid User instance (missing username). Fixed and improved test to catch the problem.

Added new push optional parameters and the possibility to send a json payload instead of a simple string message

Finally getting rid of all the senseless code on __init__, and creating the code (for exceptions) and connection (for access keys management and the ParseBase class) modules.

getting _editable_attrs to return a dict. That will make things easier to get only 'public' attributes from objects'

Adding authentication methods, and figured out that Parse does return sessionToken info if requests are made with master key set, so I'm adding a new way to setup the connection. Before any interaction with Parse, simply call ParseBase.register(app_id, rest_key, **optional_keys) and it will save them. So the library now becomes usable for applications both with or without the master key.