DOC: Change print statements to print function calls

[alefnula]

Suggestion: Changing print open('bar.csv').read() statements to print(open('bar.csv').read()) in documentation would make the docs more compatible with Python3.X and still keep it compatible with Python2.X.

[alefnula]

I can take this if nobody is working on that already...

[jreback]

go 4 it....

[alefnula]

@jreback Just one thing: I see that you use print (...) in lot of places instead of print(...). Is this just a 2to3 thing or there is a convention to use it with a space between the print and the open bracket? print(...) works with 2.6, 2.7, ... and since it's a function in 3.X I prefer that syntax. But if the convention is to use it with the space between I'll change the docs that way.

[jreback]

I am not sure it matters (prob just a typo if that's the case).....prob print(...)is more correct

[alefnula]

I also changed all the print statements in the code (not just the docs) to print(...). I can also add that to this pull request. Or I should create a new issue?

[jreback]

no code should have print statements, and they would break py3, do you have an example?

[alefnula]

@jreback Not directly in the code but in the comments and docstrings. Also in sphinxexts, scripts, vb_suite...

[jreback]

ahh....sure go ahead with that ....you can put it in another commit with this one.....

just be aware that these are not directly tested so just validate as you go

[jtratner]

@alefnula please put that in a separate issue and @jreback need to have enough time to review that one...somewhat easy to break the code in vbench by accident (since it's not tested directly)