From 643934b950fb97793cec95703310d749c3aea9c7 Mon Sep 17 00:00:00 2001 From: Zenohm Date: Sat, 14 May 2016 18:37:44 -0400 Subject: [PATCH] Explained limitations, offered alternative Added a section at the bottom explaining what a developer should do if they need access to information that the Wolfram Alpha API provides but that isn't built into the interface. Because of the way this update handles the API's replies the information is easy to access using builtin data types. --- README.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.rst b/README.rst index 464b8e6..babdfbc 100644 --- a/README.rst +++ b/README.rst @@ -49,4 +49,6 @@ You may also query for simply the pods which have 'Result' titles or are marked print(res.results[0]) +The interface as it is now does not have code built for accessing every piece of information that the Wolfram Alpha API could return. As such, every class has a copy of the original structure that it is supposed to parse. This copy is placed in a variable called node for every class but the Result class, whose variable is named tree. If there is information from the Wolfram Alpha API that you need for your program that this interface does not provide an exact function for then you can still gain access to that information through the previously mentioned variables; you'll just have to handle the API directly until the functionality you seek is built. + For more information, read the source.