Skip to content
This repository has been archived by the owner on May 4, 2021. It is now read-only.

Pin pandas version and consider dropping Python 3.5 support #70

Closed
prashantmital opened this issue Mar 6, 2020 · 4 comments
Closed
Labels
tracked-in-jira Ticket filed in Mongo's Jira system

Comments

@prashantmital
Copy link
Contributor

We should pin pandas in our Travis builds to >=1.0.0, <2.
Note that this would require dropping Python 3.5 support. It appears pandas now only support 3.6.1+, 3.7+ and 3.8+: https://pandas.pydata.org/pandas-docs/stable/getting_started/install.html#python-version-support

@ShaneHarvey
Copy link
Member

I think it’s a good idea to leave it unpinned, that way we notice breaking changes in new releases when they happen.

@prashantmital
Copy link
Contributor Author

Sure. What do you think about dropping Python 3.5? Tight integration with Pandas/Numpy is the main usecase for bson-numpy so it seems reasonable to me to unsupport runtimes that are no longer supported by those libraries.

@agolin95
Copy link

agolin95 commented Dec 4, 2020

@agolin95 agolin95 added the tracked-in-jira Ticket filed in Mongo's Jira system label Dec 4, 2020
@prashantmital
Copy link
Contributor Author

Closing this as we have discontinued development of BSON-NumPy. PyMongoArrow is now the recommended way to materialize MongoDB query results as NumPy ndarrays as well as tabular formats like Pandas' DataFrames and PyArrow Tables.

PyMongoArrow supports CPython 3.6+ only.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tracked-in-jira Ticket filed in Mongo's Jira system
Projects
None yet
Development

No branches or pull requests

3 participants