Multi-layered symlinks to python cause runtime error. sys.path is malformed.

Open
#57,393 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start by reading the historical symlink_path_fix.patch and reproduce the multi-layered symlink launch case described in the issue. Trace Python startup path handling and verify that sys.path is correctly formed; done means the runtime error is resolved without malformed entries.

Written by the indexing model from the issue text.

Description

interpreter-core type-bug
BPO 13184
Nosy @terryjreedy, @ncoghlan
Files
  • symlink_path_fix.patch
    		•

    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 2011-10-15.05:14:40.251>
labels = ['interpreter-core', 'type-bug']
title = 'Multi-layered symlinks to python cause runtime error.  sys.path is malformed.'
updated_at = <Date 2013-02-01.21:54:27.632>
user = 'https://bugs.python.org/JasonHowlett'

    bugs.python.org fields:

    activity = <Date 2013-02-01.21:54:27.632>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-10-15.05:14:40.251>
creator = 'Jason.Howlett'
dependencies = []
files = ['23415']
hgrepos = []
issue_num = 13184
keywords = ['patch']
message_count = 4.0
messages = ['145582', '145608', '146139', '146158']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'ncoghlan', 'Jason.Howlett']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue13184'
versions = ['Python 2.7']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.