As per versae#65, current behaviour when auth fails is that a 401 StatusException is raised, and caught by this try/except block and a misleading NotFoundError is raised in its place - lets just let the StatusException through. Unsure about what other Exceptions may be raised but cannot reproduce.
…in a transactions
Previous code would simply report "Invalid data sent" if Neo4j returned a non-200 error status -- since this encapsulates server errors (500s) as well as data formatting errors (400s), the 'message' field in the response JSON can be very useful.
…s (not yet implemented).