`pythonic-start-process` crashes when starting in a directory that shadows a stdlib module name

[glyph]

If I have a package with a src/foo/bar/site.py, and I use pythonic-start-process to start my interpreter while editing that file, it crashes because it shadows the built-in site module, even if there is properly a __init__.py file in that folder marking it as a package. There should be some heuristics to select an appropriate cwd, or at least an easy option to do so.

(This is derived from the behavior of the 'isortify' package, but perhaps they're using it improperly?)