python / python/cpython

pdb on setuptools "ValueError: underlying buffer has been detached"

Open
#80,260 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stdlib
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 36079
Nosy @gerritholl

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 2019-02-22.14:42:18.620>
labels = []
title = 'pdb on setuptools "ValueError: underlying buffer has been detached"'
updated_at = <Date 2019-02-22.14:42:18.620>
user = 'https://github.com/gerritholl'

bugs.python.org fields:

activity = <Date 2019-02-22.14:42:18.620>
actor = 'Gerrit.Holl'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-02-22.14:42:18.620>
creator = 'Gerrit.Holl'
dependencies = []
files = []
hgrepos = []
issue_num = 36079
keywords = []
message_count = 1.0
messages = ['336316']
nosy_count = 1.0
nosy_names = ['Gerrit.Holl']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue36079'
versions = ['Python 3.6']

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.

Research direction

Start with the linked BPO issue 36079 and reproduce the reported failure while using pdb on setuptools. No source file or test is identified in the issue, so locate the failing setuptools and debugger path before deciding where a regression test belongs. Done means the detached-buffer error is reproducible, explained, and covered by a passing test.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.