Dev

[OEG-Clark]

Added functionalities of data flow and code_tokens

[dgarijo]

@OEG-Clark, thanks for your contribution. There are few things that are missing here:

• There is no documentation explaining what the dataflow is, what it means or how to interpret it. Without it, it's difficult to use. Please add something in the readme.
• There are no tests for the dataflow. How do we know the dataflow is correct? I would like a test extracted from the Google paper as an explicit test, that we can run testing the program

Once that's done, I think we can merge the PR.

[dgarijo]

Also please move the my-languages.so file in a new folder called resources

[dgarijo]

Thanks. All the paths will now break in Unix. We need to make the paths system independent. I will have a look when I get the time

[OEG-Clark]

This is working in my system, so windows should be good, and for the testing part, we may need to state to change the path in test_inspect4py.py.

[dgarijo]

Thanks. I just need some comments on the dataflow. How is it supposed to be used? Can we use the figure from the Google paper you used as reference?

[OEG-Clark]

Will Add tomorrow, however, the test is just the same example

[dgarijo]

Right, but we need it for reference and to explain how things work

[dgarijo]

whatt?? Why was there an inspect4py2?