News for hackers. Stuff that matters.
Re:Pandas 3.0 by jtrueb on Wednesday January 28, 2026 @08:33AM (#46795161)
That timestamp resolution discrepancy is going to cause so many problems
Re:Pandas 3.0 by EForEndeavour on Wednesday January 28, 2026 @10:24AM (#46796542)
Do you mean the new default datetime resolution of microseconds instead of the previous nanosecond resolution? Obviously this will require adjustments to any code that requires ns resolution, but I'd bet that's a tiny minority of all pandas code ever written. Do you have a particular use case in mind for the problems this will cause?
Re:Pandas 3.0 by jtrueb on Wednesday January 28, 2026 @01:40PM (#46799732)
I would describe it as the huge majority, reflecting on my pandas use over the years. Pretty much all of the data worth exploring in pandas over excel, some data gui, or polars involves timestamps.
Re:Pandas 3.0 by ciupicri on Wednesday January 28, 2026 @02:14PM (#46800168)
Yeah, but is nanosecond-level resolution necessary? In many scenarios, a resolution of one second is adequate.
Re:Pandas 3.0 by jtrueb on Wednesday January 28, 2026 @03:13PM (#46800899)
I don't need nanosecond accuracy. I just know there are a lot of scripts expecting it.