allowing tensorflow version flexibility when installing from source

[scarrazza]

Following the discussion this morning, here we:

• unlock tf versions when installing from source
• set the latest tensorflow version for the pip package
• include a check for the tf version, storing the compiled version during installation.

[codecov]

Codecov Report

Merging #7 (f81f045) into tf250 (2e5e6ac) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             tf250        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         3    -1     
  Lines          373       371    -2     
=========================================
- Hits           373       371    -2     

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

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

Impacted Files	Coverage Δ
...m_operators/python/ops/qibo_tf_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 2e5e6ac...f81f045. Read the comment docs.

[stavros11]

Thanks for implementing this. I was a bit confused about the use of the __init__.py.in file at first but after building the custom operators I now understand the use. Works well for me.

[stavros11]

Aren't these checks equivalent to a single if tf.__version__ != __target_tf_version__ check?

Also regarding the error message, I think there is also the option to just rebuild the custom operators without upgrading/downgrading any of the libraries. However this may be confusing for the average user so it is okay to leave it as it is.

[scarrazza]

Yes, indeed, should be equivalent. The if/else is here just to explain to the average user how to solve the incompatibility.
But, I agree that a simple != should make it, e.g. we could say qibotf and tensorflow do not match, please recompile qibotf or check the documentation. What do you think?

[stavros11]

But, I agree that a simple != should make it, e.g. we could say qibotf and tensorflow do not match, please recompile qibotf or check the documentation. What do you think?

This sounds good and is a bit more general than the current. I would just add "qibotf and tensorflow versions do not match". I am fine with either message, but perhaps referring to the docs is the best idea.