"ImportError: dynamic module does not define init function" when deleting and recreating .so files from different machines over NFS
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start by reviewing dynload_report_dlerror.patch and the Python 3.5 interpreter-core import and dynamic-loader code. Reproduce the reported deletion and recreation of .so files across NFS, then determine whether the attached patch accurately reports the loader failure and verify the resulting behavior with the relevant interpreter tests.
Written by the indexing model from the issue text.
Description
| BPO | 19615 |
|---|---|
| Files |
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 2013-11-15.17:53:53.657>
labels = ['interpreter-core', 'type-bug']
title = '"ImportError: dynamic module does not define init function" when deleting and recreating .so files from different machines over NFS'
updated_at = <Date 2013-11-15.18:15:18.444>
user = 'https://bugs.python.org/ecatmur'
bugs.python.org fields:
activity = <Date 2013-11-15.18:15:18.444>
actor = 'ecatmur'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2013-11-15.17:53:53.657>
creator = 'ecatmur'
dependencies = []
files = ['32643']
hgrepos = []
issue_num = 19615
keywords = ['patch']
message_count = 2.0
messages = ['202963', '202967']
nosy_count = 1.0
nosy_names = ['ecatmur']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue19615'
versions = ['Python 3.5']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100