8000 ENH: PyPy3 testing · Issue #37653 · pandas-dev/pandas · GitHub
[go: up one dir, main page]
Skip to content

ENH: PyPy3 testing #37653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jcpunk opened this issue Nov 5, 2020 · 10 comments
Closed

ENH: PyPy3 testing #37653

jcpunk opened this issue Nov 5, 2020 · 10 comments
Assignees
@lithomas1
Labels
CI Continuous Integration Enhancement PyPy
Milestone
1.5

Comments

@jcpunk
Copy link
jcpunk commented Nov 5, 2020 •
edited
Loading

Is your feature request related to a problem?

With the increasing support for PyPy3 in NumPy, it would be helpful if pandas started testing against PyPy3.

Describe the solution you'd like

Please consider adding pypy3 to the .travis.yml (allowed to fail for now).

API breaking implications

No expected API breaks

Describe alternatives you've considered

This is more of a portability concern than anything else.

Additional context

Something like:

  matrix:
   -  python: pypy3
      env:
        - JOB="pypy3" PATTERN="(not slow and not network and not clipboard)"
  allow_failures:
   -  python: pypy3
      env:
        - JOB="pypy3" PATTERN="(not slow and not network and not clipboard)"
@jcpunk jcpunk added Enhancement Needs Triage Issue that has not been reviewed by a pandas team member labels Nov 5, 2020
@jreback
Copy link
Contributor
jreback commented Nov 5, 2020

happy to have a PR to do this

just note that allowed_failures are unfortunately not paid as much attention as one would like

@jcpunk
Copy link
Author
jcpunk commented Nov 6, 2020

I don't really understand conda, but took an initial stab in #37665

@rhshadrach rhshadrach added CI Continuous Integration and removed Needs Triage Issue that has not been reviewed by a pandas team member labels Nov 6, 2020
@rhshadrach rhshadrach added this to the Contributions Welcome milestone Nov 6, 2020
@lithomas1 lithomas1 self-assigned this Jul 2, 2021
@lithomas1
Copy link
Member

@mattip Do you know when PyPy will make a Python 3.8 alpha release? We are dropping Python 3.7 support in 1.4(the next release which should be released in December).

@mattip
Copy link
Contributor
mattip commented Jul 6, 2021

Thanks for the heads up. Hopefully before December. Are you basing your policies on NEP 29?

@lithomas1
Copy link
Member
< 8000 task-lists disabled sortable>

Yes.

@mattip
Copy link
Contributor
mattip commented Jul 6, 2021

cool

@mattip
Copy link
Contributor
mattip commented Oct 31, 2021

PyPy now has a 3.8 release.

You can get it on github actions by specifying pypy-3.8 in the setup-python action.

You can also get it from pypa/manylinux2014:latest (from 5 days ago): pypy3.8 is in /opt/python/pp38-pypy38_pp73.

On azuure pipelines the images may not include pypy3.8 just yet, see actions/runner-images#4347. Many of the changes have been merged, I don't know how that relates to new image deployment.

@lithomas1
Copy link
Member

Thanks @mattip. I'll add the testing in when I have some spare time.

@lithomas1 lithomas1 added PyPy and removed Blocked labels Nov 1, 2021
@stonebig
Copy link
Contributor
stonebig commented Nov 20, 2021 •
edited
Loading

it would be really helpfull, as I encounter a strange problem with Pandas-1.3.x and PyPy on windows, that Pandas-1.2.5 didn't have #44253

@lithomas1 lithomas1 mentioned this issue Dec 8, 2021
Merged
4 tasks
@jreback jreback modified the milestones: Contributions Welcome, 1.4 Dec 14, 2021
@jreback jreback modified the milestones: 1.4, 1.5 Dec 31, 2021
@mroeschke
Copy link
Member

I think #44809 added pypy testing on 3.8 on GHA so closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lithomas1 lithomas1

Labels
CI Continuous Integration Enhancement PyPy
Projects
None yet
Milestone
1.5
Development

No branches or pull requests
7 participants
@mattip @jreback @jcpunk @stonebig @mroeschke @rhshadrach @lithomas1
0