Skip to content

import dill is unresolved in VS 2022 Community #8259

Description

@rkravchuk1

Describe the bug
Simple: doing a 'pip install dill' in Powershell works, and in the command line interpreter of Python, 'import dill' works. However, in the VS IDE, an 'import dill' fails to resolve the package.

Steps to Reproduce
1.'import dill' in VS IDE is unresolved.
2.
3.

Expected behavior
'import dill' should be resolved.

Additional context and screenshots
Running Python 3.13.5 in command-line interpreter and 3.13 in VS IDE.

Sample Code


![Image](https://github.com/user-attachments/assets/fcd646c6-c4d1-42f8-9569-07c4710b6850)

Configuration information (If you are providing a diagnostics file (see below), skip this section)
VS Version: [Can be found under "Help->About Microsoft Visual Studio"]
PTVS version: [Can be found under "Help->About Microsoft Visual Studio->Installed products->Python with Pylance"]
Python version:
Debugger Type (if applicable): [New debugger or legacy debugger?]

Diagnostics file
The diagnostics file contains information such as the Python version, environments, loaded assemblies, configuration options, etc. This file makes it easier for us to reproduce and fix bugs, so we would really appreciate it if you could provide it to us. To locate the logs, you can can follow these steps:

  1. Open the File Explorer on your computer.
  2. In the address bar at the top of the window, type %TEMP% and press Enter.
  3. The %TEMP% folder should open, look for file named PythonToolsDiagnostics_*.log, where * represents a series of numbers.

This file contain the diagnostic information that can help us diagnose and resolve the issue you're experiencing.
Please note that the %TEMP% folder is a hidden system folder, so you may need to enable the display of hidden files and folders in File Explorer to see it. To do this, click on the "View" tab in File Explorer, then check the "Hidden items" box in the "Show/hide" section.
You can attach the file to this issue or email it to us at ptvshelp@microsoft.com. If you email it, please add a link to this issue.

XXX

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions