Thomas Kluyver

I spotted this blog post about the challenges of trying to fit unicode characters to a monospace grid: http://denisbider.blogspot.co.uk/2015/09/when-monospace-fonts-arent-unicode.html

Ha! I'm flattered that you're using it :-)

I have been experimenting with caching on the [cache-experimentation branch](https://github.com/takluyver/entrypoints/tree/cache-experimentation). I tested one implementation with a cache file stored in each `sys.path` directory (`make_cache.py` and `read_cache.py`) and one with a...

### Single vs in-directory Keeping a cache file in each `sys.path` directory is easier to work with conceptually - if the directory has different paths because it's accessed over NFS...

To test performance on a Linux system, clone this repository and check out the `cache-experimentation` branch. Then: ```shell # Make the caches python3 make_single_cache.py sudo python3 make_cache.py # Needs to...

I've just realised that a considerable portion of the ~0.4 seconds running the cache examples is due to imports, rather than actually loading the entry points. In my tests, doing...

I guess it depends what model of cache you're thinking about. The single file cache is easy for the application to build without requiring different tools to co-ordinate. But cache...

I'll try to think about hybrid approaches that could bridge the gap and allow applications to use caching while package managers get on board.

For reference, I just checked the performance of fetching the mtimes of all entry points files. Best of 3 tries: - Cold start: 4.5 seconds (about the same as reading...

Yeah, in the context of deployment tools that build an environment as a ~immutable thing, and any changes in dependencies mean building a new env, creating a single-file cache definitely...