Changes between Initial Version and Version 1 of Ticket #33465
- Timestamp:
- Jan 27, 2022, 11:15:33 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #33465 – Description
initial v1 42 42 }}} 43 43 44 So we're "saving" `104 bytes` per `SafeString` created, by the look of it. I presume it to be some fun implementation detail of something somewhere that it is allegedly accounting for more than ` 56` bytes, which is the `asizeof({})`44 So we're "saving" `104 bytes` per `SafeString` created, by the look of it. I presume it to be some fun implementation detail of something somewhere that it is allegedly accounting for more than `64` bytes, which is the `asizeof({})` 45 45 46 46 A quick and dirty check over the test suite suggests that for me locally, running `14951 tests in 512.912s` accounted for `949.0 MB` of SafeStrings, checked by just incrementing a global integer of bytes (using `SafeString.__new__` and `--parallel=1`) and piping that to `filesizeformat`, so y'know, ''room for error''.