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
Thanks to the maintainers for starting this project -- it's hard to overstate the impact that cloudpickle has had in filling in the gaps of Python's built-in pickling capabilities, and one only needs to look at the pypistats for cloudpickle to see how important it has become in industry and other open source projects.
I was wondering if there are any plans for another release at some point -- I can see that there have been quite a lot of important developments since the last one, such as improved compatibility with Python 3.10. I don't mean to be pushy; as a maintainer of a few (far less impactful) open source projects myself, I know it's a thankless job. :) Just curious if there is a timeline in effect; no worries if not.
The text was updated successfully, but these errors were encountered:
Hi @smacke. We plan to release cloudpickle within the next couple of weeks - before releasing, we typically check through tailored CI workflows that the newcloudpickle remains backwards-compatible with some widely used downstream libraries relying on cloudpickle, such as ray, dask and joblib. However, some of these workflows are broken, and need fixes (see #432 ). Once they are fixed, we can run the downstream tests, and once they pass, we will release cloudpickle 2.0.0.
Hi,
Thanks to the maintainers for starting this project -- it's hard to overstate the impact that cloudpickle has had in filling in the gaps of Python's built-in pickling capabilities, and one only needs to look at the pypistats for cloudpickle to see how important it has become in industry and other open source projects.
I was wondering if there are any plans for another release at some point -- I can see that there have been quite a lot of important developments since the last one, such as improved compatibility with Python 3.10. I don't mean to be pushy; as a maintainer of a few (far less impactful) open source projects myself, I know it's a thankless job. :) Just curious if there is a timeline in effect; no worries if not.
The text was updated successfully, but these errors were encountered: