removing undesired prints

[scarrazza]

Closes #386. I don't think there is some simple way to catch prints from pytest but let me know.

[bpcarlos]

Fixed the undesired prints

[codecov]

Codecov Report

Merging #387 (acb855c) into master (db9b794) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #387   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           77        77           
  Lines        12454     12450    -4     
=========================================
- Hits         12454     12450    -4     

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/qibo/core/gates.py	100.00% <ø> (ø)
...qibo/tests_new/test_tensorflow_custom_operators.py	100.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update db9b794...acb855c. Read the comment docs.

[stavros11]

I had a quick look too and did not find any other prints.

Closes #386. I don't think there is some simple way to catch prints from pytest but let me know.

I am also not aware of any method to do this directly with pytest. A naive solution would be to write a test that loads each .py file from the project as string and checks if it contains the word print, excluding the cases where print appears in docstrings. If you agree I can try to implement this test in a different PR.

[scarrazza]

@stavros11 ok, let's do that.