Skip to content

.mypy_cache folder created next to files not in project #3380

@syagev

Description

@syagev

Issue Type: Bug

When your workspace has mypy linting enabled, open a python file which is not a part of the project (e.g. in a completely different place on the file system or even a network share). VSCode will create a .mypy_cache folder next to the file opened.

This behaviour is almost always undesired - think about opening a random file on a network share that isn't yours. It's ok to create temp directories in the workspace folder, but not ok to do it in random places without asking the user.

Extension version: 2018.10.1
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)
GPU Status 2d_canvas: unavailable_software
checker_imaging: disabled_off
flash_3d: unavailable_software
flash_stage3d: unavailable_software
flash_stage3d_baseline: unavailable_software
gpu_compositing: unavailable_software
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_software
video_decode: unavailable_software
video_encode: unavailable_software
webgl: enabled_readback
webgl2: unavailable_off
Memory (System) 63.81GB (54.09GB free)
Process Argv
Screen Reader no
VM 0%

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions