I just read a huge thread about this exact issue from January (https://forum.freecodecamp.org/t/sea-level-predictor-errors/437517 )where a member of the freeCodeCamp staff said they adjusted the test code to resolve the issue but I am still having this issue.
I’m not sure how to fix this.
Your code so far
https://repl.it/@PaigeCrossley/boilerplate-sea-level-predictor#sea_level_predictor.py
Your browser information: Google Chrome
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36.
Challenge: Sea Level Predictor
Link to the challenge:
Jagaya
February 17, 2021, 8:38pm
#2
Well it’s a common error and there are a couple topics already adressing it, including one from just a couple hours ago
Expected results in tests were written some time ago, at that time pandas were using as default different (less precise) representation of float numbers when read with read_csv method. pandas 1.2.0 changed that default, but float_precision='legacy' optional argument allows to use the same precision as in older versions.
Thank you! No idea how I missed that one.
system
August 19, 2021, 9:10am
#4
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
