python cannot import module located on a "VOLUME" directory
Open
Nobody has claimed this yet.
OS-windows
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30865 |
|---|---|
| Nosy | @pfmoore, @tjguk, @bitdancer, @zware, @zooba, @apre |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2017-07-06.09:51:02.021>
labels = ['type-bug', 'library', 'OS-windows']
title = 'python cannot import module located on a "VOLUME" directory'
updated_at = <Date 2017-07-06.14:16:10.709>
user = 'https://github.com/apre'
bugs.python.org fields:
activity = <Date 2017-07-06.14:16:10.709>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2017-07-06.09:51:02.021>
creator = 'apre'
dependencies = []
files = []
hgrepos = []
issue_num = 30865
keywords = []
message_count = 2.0
messages = ['297820', '297831']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'r.david.murray', 'zach.ware', 'steve.dower', 'apre']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue30865'
versions = ['Python 3.6']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the original BPO issue 30865 and reproduce the import failure on Windows using Python 3.6, with the module located on a VOLUME directory. Inspect the Library (Lib) import behavior and define completion as successfully importing that module from the VOLUME directory, with coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100