>'ict in 'ytes

>>107826742
db?

>>107826703
python is not the right language to worry about memory usage

>>107826703
>What’s the proper way to measure your dict in bytes?
write your Python in C using the extension API

like nigga wtf are you doing, you're in a duck typed garbage collected language
>dump straight into a buffer
no, you shouldn't pass arbitrary python objects around like a retard. the standard practice is to serialize them in some way. then you get a string or a buffer of specific length out, but at runtime the size of the object can vary hugely.

File: 1767698396892044.gif (2.54 MB, 252x189)

2.54 MB GIF

>>107826703
>the joke is sex

>>107826703

len(json.dumps(mydict))

File: apu_billiard.jpg (111 KB, 1024x702)

111 KB JPG

>>107827256
>>107826742
oh fuck I fell for it

>>107827267

>>> len(json.dumps(d))
Traceback (most recent call last):
  File "<python-input-5>", line 1, in <module>
    len(json.dumps(d))
        ~~~~~~~~~~^^^
  File "/usr/lib/python3.13/json/__init__.py", line 235, in dumps
    return _default_encoder.encode(obj)
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/lib/python3.13/json/encoder.py", line 202, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.13/json/encoder.py", line 263, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.13/json/encoder.py", line 182, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
                    f'is not JSON serializable')

ok now what?

>>107827256
thought we were having some sort of dict measuring contest here

Nigga stole that joke from 10yo StackOverflow post, btw.

>>107828593
it's new to me

>>107826703
>I turned my dict into a pickle, Guido!
I'M PICKLED DICT!

>>107826703
>MUH DICT