Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign up

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

pandas-dev / pandas Public

Notifications You must be signed in to change notification settings
Fork 18.4k
Star 45.2k

Code
Issues 3.6k
Pull requests 81
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

CI: ensure proper coverage of different pyarrow versions#30039

Merged

jreback merged 5 commits intopandas-dev:masterpandas-dev/pandas:masterfrom

jorisvandenbossche:ci-pyarrowjorisvandenbossche/pandas:ci-pyarrowCopy head branch name to clipboard

Dec 4, 2019

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Dec 4, 2019

test pyarrow=0.12 as minimum supported version
jorisvandenbossche
committed
uncomment in travis 3.6 cov build
jorisvandenbossche
committed
move minimum supported version to other build
jorisvandenbossche
committed
use conda-forge and pyarrow>=0.15 in azure-37 build
jorisvandenbossche
committed
skip failing parquet test
jorisvandenbossche
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.