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
However, it looks like this causes some internal problems for pdpy. When I do pdpy.fetch_mps with a date range, before enabling that option, all goes well:
importpdpy# No error, a data frame results.pdpy.fetch_mps(from_date='2000-10-11',to_date='2024-02-19')
However, if I enable copy_on_write, I get an error:
Thanks for this package!
I nearly always use Pandas
copy_on_write
mode - which will be the default and only mode in upcoming Pandas 3.0 : https://pandas.pydata.org/pandas-docs/stable//user_guide/copy_on_write.html.I enable it with:
However, it looks like this causes some internal problems for
pdpy
. When I dopdpy.fetch_mps
with a date range, before enabling that option, all goes well:However, if I enable
copy_on_write
, I get an error:This results in:
Is there something going in internally that does not work with this option?
The text was updated successfully, but these errors were encountered: