> See the Stackoverflow post I linked to at the start of my post. > > > https://stackoverflow.com/questions/56966429/getting-pairs-of-one-item-and-the-rest-over-a-python-list
I’m confused— that seems to be a SO post related to another ongoing thread… <https://stackoverflow.com/questions/56966429/getting-pairs-of-one-item-and-the-rest-over-a-python-list> > I don't know if a gigabyte of data in a list is Big Data or not, We’ll, Wes McKinney of Pandas fame once defined “medium data” as too big for memory, but not too big for a typical workstation hard disk (when we still used hard disks). So no, 1GB is not big data. But not sure what call “big enough to stress typical workstation memory”. But anyway: If you really have that much data, you probably want numpy arrays or something (even array.arrays are far more memory efficient for.basic data types) But sure, if we can eliminate inefficiencies in Python standard data types, then why not? I’ve lost track of the exact use case here, but maybe the proposal a while back for sequence views would help? We often end up making a full copy of a slice simple to iterate over it, or … if there was sway to work with a subset of a sequence without making an actual copy, that could help a lot in these cases. -CHB -- Christopher Barker, PhD (Chris) Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/BHUBKEBL4ZY7UGGKFYFZFJKDZOR2A37Z/ Code of Conduct: http://python.org/psf/codeofconduct/
