sslivkoff

hi. I just want to remark that pruning these imports would make polars significantly more useful for building cli tools. in the context of cli, startup times + import times...

hmm I'm just using tuna `0.5.11`, nothing special (and I was testing polars `0.14.21`). clicking on entries will zoom in on them btw Ive found it helpful to put: ```bash...

incredible stuff 🍾🍾

It looks an error only happens when using large `int`s. This works without error: ```python numbers = [1, 2] pl.Series(numbers, dtype=pl.Decimal) ```

reran on commit `0xb4fcb1518fdafb0710daff1cb2c0c6116552d39c`. a few remaining discrepancies ``` ┌──────────────────────────────┐ │ Discrepancies in eth_getLogs │ └──────────────────────────────┘ args: address: 0x6b175474e89094c44da98b954eedeac495271d0f start_block: 14000000 end_block: 14000100 different number of results - erigon: 85...

all of these discrepancies have been patched

noticed some regressions ``` ┌──────────────────────────────┐ │ Discrepancies in eth_getLogs │ └──────────────────────────────┘ args: address: 0x6b175474e89094c44da98b954eedeac495271d0f start_block: 14000000 end_block: 14000100 different number of results - erigon: 85 results - reth: 0 results...

also having trouble getting successful responses from trace methods ``` ┌──────────────────────────────┐ │ Discrepancies in trace_block │ └──────────────────────────────┘ args: block_number: 16000000 reth failed ┌─────────────────────────────┐ │ Discrepancies in trace_call │ └─────────────────────────────┘ args:...

once node is sync'd vanilla calls are working with no discrepancies trace calls still not working

need error messages for when valid data is not available