Add sys flag to always show full paths in stack traces (instead of relative paths)

Open
#79,776 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

No files, tests, or entry points are named. Start by locating Python's stack-trace path formatting and existing sys flags, then determine where a flag for always showing full paths would belong; done means the flag changes stack-trace paths consistently and has coverage for both relative and full-path output.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-feature
BPO 35595
Nosy @stevendaprano, @tirkarthi

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 2018-12-27.15:50:03.992>
labels = ['type-feature', '3.8']
title = 'Add sys flag to always show full paths in stack traces (instead of relative paths)'
updated_at = <Date 2018-12-28.12:05:04.061>
user = 'https://bugs.python.org/ScottArciszewski'

bugs.python.org fields:

activity = <Date 2018-12-28.12:05:04.061>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2018-12-27.15:50:03.992>
creator = 'Scott Arciszewski'
dependencies = []
files = []
hgrepos = []
issue_num = 35595
keywords = []
message_count = 2.0
messages = ['332593', '332622']
nosy_count = 3.0
nosy_names = ['steven.daprano', 'xtreak', 'Scott Arciszewski']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue35595'
versions = ['Python 3.8']

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.