Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fastcore 1.1 breaking changes

See original GitHub issue

🐛 Bug

Describe the bug Fastcore 1.1 contains a breaking change described here:

Remove Path.{read,write} (use Path.{read_text,write_text} instead) and change Path.{load,save} to functions load_pickle and save_pickle (#121)

We need to update our calls to Path.read to fix this issue.

Issue Analytics

State:
Created 3 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

2reactions

FraPochetticommented, Oct 9, 2020

Sure man! Will do that tomorrow 😉. I will also check icedata.

I’m guessing that read_text returns a string just like read does right?

Yes.

1reaction

FraPochetticommented, Oct 9, 2020

Yes please

Top Results From Across the Web

fastcore/CHANGELOG.md at master - Release notes - GitHub

1.1.0. Breaking Changes. Remove Path.{read,write} (use Path.{read_text,write_text} instead) and change Path.{load,save} to functions load_pickle and ...

With colab, fastai path doesn't work at chapter 9 - Part 1 (2020)

There was a breaking change, you can see in the fastcore changelog: ... ([#125](https://github.com/fastai/fastcore/issues/125)) ## 1.1.1 ...

fastai Changelog - pyup.io

Update fastcore minimum version ... There is one breaking change in this version of fastai, which is that custom metadata is now ......

fastcore 1.4.5 - PyPI

To install fastcore run: conda install fastcore (if you use Anaconda, ... the problem that normally in Python tab-completion and docs break when...

fast.ai (@fastdotai) / Twitter

Release v1.5.27 · fastai/fastcore ... Breaking Changes - `_quarto.yml` no longer replaced with automatically generated ... Release v2.1.1 · fastai/nbdev.