pg8000 VS polars

As others have said you can use a custom compiled version of the lib, lambda layer or use lambda images, however, if you're not committed to psycogp2 I've found pg8000 a much easier library to work with in Lambda. You can just install it as any other library without any problems.

When people say "pure X", to me, it normally means they didn't involve an FFI or external compiler. This is an often beneficial thing since it simplifies your build process.

For example, here [0] is a "pure Python postgres driver" and the implication is that it doesn't use libpg.

Or see also this discussion [1].

[0] https://github.com/tlocke/pg8000

[1] https://www.reddit.com/r/learnpython/comments/nktut1/eli5_th...

I agree that information shouldn't be duplicated, but in one of my projects I've taken the opposite approach and made the FAQ the only place that certain information is presented. It's for the library https://github.com/tlocke/pg8000 and I've called them 'Examples' rather than a FAQ, but each time I get a question that isn't covered by the examples I add in a new example. I'd be interested to hear what people think of this approach.

This is because 0.1 is in actuality the floating point value value 0.1000000000000000055511151231257827021181583404541015625, and thus 1 divided by it is ever so slightly smaller than 10. Nevertheless, fpround(1 / fpround(1 / 10)) = 10 exactly.

I found out about this recently because in Polars I defined a // b for floats to be (a / b).floor(), which does return 10 for this computation. Since Python's correctly-rounded division is rather expensive, I chose to stick to this (more context: https://github.com/pola-rs/polars/issues/14596#issuecomment-...).

https://github.com/pola-rs/polars/releases/tag/py-0.19.0

That turned out to be related to pola-rs/polars#11912, and this linked comment provided a deceptively simple solution - use PARSE_DECLTYPES when creating the connection: