Hi Rebecca,
Am Sat, Feb 03, 2024 at 12:32:07PM + schrieb Rebecca N. Palmer:
> My fixes are pushed to Salsa, but they're in a fork because this isn't a
> debian-science package:
> https://salsa.debian.org/rnpalmer-guest/influxdb-python
Argh, I missed that link inside the bug report and
My fixes are pushed to Salsa, but they're in a fork because this isn't a
debian-science package:
https://salsa.debian.org/rnpalmer-guest/influxdb-python
Note that this uncertainty is only around whether this is a complete fix
- even in the case where it's not, it *wouldn't* be actively worse than
doing nothing, though it would be hiding the problem.
Some looking through the code suggests that the precision is user-set
and hence constant within a single query, and hence that this fix is OK,
but I'm not entirely certain of that.
There are ways to make pandas 2.x accept mixed time format, but I think
they're 2.x _only_ and/or slow.
That's not the only problem: some of the tests mix timestamps in
slightly different formats (with and without fractional seconds), which
is no longer allowed by default:
https://pandas.pydata.org/pandas-docs/version/2.1.4/whatsnew/v2.0.0.html#datetimes-are-now-parsed-with-a-consistent-format
Control: severity -1 important
(We would like to transition to pandas 2.1 fairly soon.)
This bug can probably be fixed by replacing all 3 instances of
pandas.util.testing with pandas.testing.
There are also some (unrelated) Python 3.12 issues:
self.assertRaisesRegexp ->
6 matches
Mail list logo
