You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it correct that the current (unstable) branch is not compatible with python2-based TRIQS installations and that the tag py2_compat should be used in that case? Is it possible to mention this in the installation documentation?
The text was updated successfully, but these errors were encountered:
Thank you for pointing this out!
I have created a Python2 compatible 0.9.x release branch and set this as the default branch.
This should avoid any confusion.
We will tag a Python3 compatible release once the TRIQS 3.0 release is tagged.
Is it correct that the current (unstable) branch is not compatible with python2-based TRIQS installations and that the tag py2_compat should be used in that case? Is it possible to mention this in the installation documentation?
The text was updated successfully, but these errors were encountered: