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 your feature request related to a problem? Please describe.
The pipeline uses python 3.6 and the shuffled analysis uses 3.8, so the data frame outputs of these two are not compatible, because pyhton 3.6 cannot open 3.8 pickles. This problem can be managed by having multiple virtual environments on Eleanor.
Describe the solution you'd like
Update the pipeline to use 3.8
Describe alternatives you've considered
Keep using the workaround. I think this will cause a lot of issues for less experienced users.
The text was updated successfully, but these errors were encountered:
klaragerlei
changed the title
Different part of this repo need different versions of python
Different parts of this repo need different versions of python
Sep 20, 2021
Could this be solved by specifying the max pickler-protocol in the shuffled-analysis code, so that it saves dataframes that are backwards compatible with the 3.6 pipeline?
Protocol version 4 was added in Python 3.4. It adds support for very large objects, pickling more kinds of objects, and some data format optimizations. It is the default protocol starting with Python 3.8. Refer to PEP 3154 for information about improvements brought by protocol 4.
Protocol version 5 was added in Python 3.8. It adds support for out-of-band data and speedup for in-band data. Refer to PEP 574 for information about improvements brought by protocol 5.
Is your feature request related to a problem? Please describe.
The pipeline uses python 3.6 and the shuffled analysis uses 3.8, so the data frame outputs of these two are not compatible, because pyhton 3.6 cannot open 3.8 pickles. This problem can be managed by having multiple virtual environments on Eleanor.
Describe the solution you'd like
Update the pipeline to use 3.8
Describe alternatives you've considered
Keep using the workaround. I think this will cause a lot of issues for less experienced users.
The text was updated successfully, but these errors were encountered: