Michael Penkov
Michael Penkov
> The process seems to work but it consumes a lot of memory. Can you run a profiler to see where the memory consumption is?
That's not the kind of profiling that we need here. You're profiling CPU time, we need to profile memory usage. See e.g. https://pypi.org/project/memory-profiler/ in particular the "line-by-line memory usage" section.
I played around with it a bit earlier: https://github.com/RaRe-Technologies/smart_open/pull/545 I'm not sure if it's really worth it for the entire package. Adding it for just the public-facing functions may be...
I'd do it from scratch because that PR did type annotations for everything, even internal stuff, which is overkill. Are you up to it?
Yes, I think this is the cause: ``` #### Remove Assert and Docstring export PYTHONOPTIMIZE=2 ```
@donsokolone Can you think of a way we can avoid the unwanted writes?
I think even simpler `from unittest import mock` is safe. That submodule has been around since Python 3.3. There is no way it won't be available. The existing behavior is...
Thank you @a-detiste !
I think you can just report the issue here
Isn't this a problem with `pickle`, not with `sqlitedict` itself?