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
I have just tried installing fretbursts with the recommended "conda install -c conda-forge fretbursts" line and received an error message about a conflict due to my version of python (3.9). On the documentation it says python 3.6+ is needed; but is there a limit to the version of python supported ? Is there a workaround otherwise ?
Many thanks,
Christophe
The text was updated successfully, but these errors were encountered:
Compatibility issues with 3.6/3.7+ is a known problem. From what I remember there was some issues with unit testing that prevented the package from being updated to support newer python versions. I have wanted to get round to fixing this for a while but haven't found the time.
My suggestion would be to use a dedicated conda environment for your FRETBursts installation which uses an older version of python, in general, this is good practice anyway (see: [https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html])
So, to create an environment and install FRETBursts you'd want to do something along the lines of:
Sorry if I'm chiming in much later. I'm taking over the maintenance of FRETbursts.
What I can tell you is this: the latest github version of FRETBursts is fully compatible with python 3.9, unfortunately I haven't been able to get it up onto conda-forge, the update process is broken somehow.
So if you install with pip instead
Hello,
I have just tried installing fretbursts with the recommended "conda install -c conda-forge fretbursts" line and received an error message about a conflict due to my version of python (3.9). On the documentation it says python 3.6+ is needed; but is there a limit to the version of python supported ? Is there a workaround otherwise ?
Many thanks,
Christophe
The text was updated successfully, but these errors were encountered: