paultiq

I took a look at this, but went down a different path of loading duckdb_wasm instead of building duckdb. Proof of concept here: https://github.com/iqmo-org/jupylite_duckdb/blob/main/notebooks/example.ipynb I'm still trying to figure out...

Still reproduces on `│ 0.8.2-dev3092 │ 1f17e1cec6 │`

> Isn't duckdb's duckdb_plus60 the correct answer according to the linked blog post? I interpret as the opposite: that the correct timezone aware offset is the one given by the...

The first example (UTC-05:00) isn't reproducing, since it's a fixed offset w/ no daylight savings component. The behavior I'm expecting is given by your second and third examples: - `print(pandas.Timestamp("2018-02-14...

> Pandas may do something different here, but what adding 60 days across a DST boundary should return is a matter for theologians really. > > > > I'd also...

> No, we use ICU internally (which doesn't have these problems). We only use `pytz` when producing `pandas` output because that its what `pandas` requires. Yup, that's what I was...

> Yes that does what @paultiq is expecting: ... Yes, thanks... that's the part I was hung up on. That this version is `(24*60 - 1)` hours, but the Pandas...

I still have the same issue too in v1.1.3 (extension version f743d4b)... has anyone seen a change in behavior here? The short version is: - AWS_PROFILE set, referencing a profile...

> @paultiq I have the same issue. Just verified with Duckdb 1.1.3 and it still fails. I have not seen any improvement. This extension does not support web identity as...

> Updating here too, we have found that using the `amazon/aws-lambda-python:3.12` image only works for 24 hours. Looks like the AWS session expires and duckdb doesn't pick up the new...