Icevision: Fastcore 1.1 breaking changes

Created on 9 Oct 2020  路  9Comments  路  Source: airctic/icevision

馃悰 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.

bug good first issue hacktoberfest help wanted

Most helpful comment

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.

All 9 comments

Currently a hot-fix was implemented by simplying locking fastcore version to <1.1

As far as I can tell we have only 2 occurrences of pathlib.Path.read() in the codebase: here and here.
Is this correct?

If this is the case I can quickly patch it. It should be a matter of replacing .read() with either .read_text() or .read_bytes(). They both work with json.loads(...)

Is this correct?

I believe you're correct, I did a global search and the other reads that I found seem not to be related with Path

If this is the case I can quickly patch it.

That would be very much appreciated 鉂わ笍, I'm guessing that read_text returns a string just like read does right?

I also opened the reflecting issue on icedata.

It's not necessary to fix the issue there to fix it here, but I just wanted to let you know in case you're interested.

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.

Thanks!!

Should I assign the issue to you? So other people know it's already taken

Yes please

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tugot17 picture tugot17  路  3Comments

lgvaz picture lgvaz  路  5Comments

lgvaz picture lgvaz  路  6Comments

lgvaz picture lgvaz  路  5Comments

lgvaz picture lgvaz  路  5Comments