Thanks @fijal and team for all the effort! This is awesome.
The last update on the Pypy+Pandas wiki[0] is from this August, and it mentions that there are still 15 outstanding failing tests. Does this release mean that 5.9 is now at 100% parity? What does the same metric look like for Pypy+Numpy, and where can that one be tracked if not 100% yet?
I am looking forward to migrating some pipelines over to 5.9 soon.
As you point out there are still a few failing tests. The
The number of failing tests on both is very low but not zero.
The PyPy team has had good collaboration with Pandas and NumPy, but there are some deeper issues with these packages depending on refcount semantics in some edge cases, IMO rarely seen in real world scenarios. For numpy this means using an out keyword argument can be tricky, and for Pandas it means some galse positives in determining when a dataframe is being held by another reference, making it read-only
Of course if your workflow depends on those features, they are critical. We are working on full compatibility and also on increasing speed.
Comments
Thanks @fijal and team for all the effort! This is awesome.
The last update on the Pypy+Pandas wiki[0] is from this August, and it mentions that there are still 15 outstanding failing tests. Does this release mean that 5.9 is now at 100% parity? What does the same metric look like for Pypy+Numpy, and where can that one be tracked if not 100% yet?
I am looking forward to migrating some pipelines over to 5.9 soon.
[0] https://bitbucket.org/pypy/pypy/wiki/cpyext_2_-_cython_and_p...
As you point out there are still a few failing tests. The The number of failing tests on both is very low but not zero. The PyPy team has had good collaboration with Pandas and NumPy, but there are some deeper issues with these packages depending on refcount semantics in some edge cases, IMO rarely seen in real world scenarios. For numpy this means using an out keyword argument can be tricky, and for Pandas it means some galse positives in determining when a dataframe is being held by another reference, making it read-only
Of course if your workflow depends on those features, they are critical. We are working on full compatibility and also on increasing speed.