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
In the README, it it stated that Python 3.7 or greater is required. However, when installing in a conda environment with Python 3.8, I get a conflict, telling me that smcpp=1.15.3 -> python[version='>=3.7,<3.8.0a0']
is required. Hence, I suggest to adapt the README to state that exactly Python 3.7 is required.
NB: With previous releases of smc++, the required Python version seems to be even more complicated:
... after which I gave up. I don't understand the issue here, as the specified python version (3.5) seems to me to fit the requirements listed in these conflict messages. I tried to install these older versions as a workaround to the GLIBC issue that I am having with Ubuntu 18.04, but did not get these versions to work, either.
The text was updated successfully, but these errors were encountered:
SMC++ runs fine with any version of Python >= 3.7. But some of the packages we depend on do not yet provide builds for Python 3.8 (e.g. pysam-developers/pysam#749). In the past, the same was true for other packages and earlier versions of Python as well.
In the README, it it stated that Python 3.7 or greater is required. However, when installing in a conda environment with Python 3.8, I get a conflict, telling me that
smcpp=1.15.3 -> python[version='>=3.7,<3.8.0a0']
is required. Hence, I suggest to adapt the README to state that exactly Python 3.7 is required.
NB: With previous releases of smc++, the required Python version seems to be even more complicated:
... after which I gave up. I don't understand the issue here, as the specified python version (3.5) seems to me to fit the requirements listed in these conflict messages. I tried to install these older versions as a workaround to the GLIBC issue that I am having with Ubuntu 18.04, but did not get these versions to work, either.
The text was updated successfully, but these errors were encountered: