zipfile should call lstat instead of stat if available

Open
#70,457 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating the zipfile implementation that calls stat and inspect how platform support for lstat is handled. Confirm the intended behavior for available and unavailable lstat implementations; the issue is complete when zipfile uses lstat where available without breaking other platforms.

Written by the indexing model from the issue text.

Description

extension-modules stdlib
BPO 26269
Nosy @Yhg1s, @serhiy-storchaka

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 2016-02-02.21:44:58.581>
labels = ['extension-modules', 'library']
title = 'zipfile should call lstat instead of stat if available'
updated_at = <Date 2016-02-27.10:33:42.132>
user = 'https://bugs.python.org/PatrikDufresne'

bugs.python.org fields:

activity = <Date 2016-02-27.10:33:42.132>
actor = 'anish.shah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules', 'Library (Lib)']
creation = <Date 2016-02-02.21:44:58.581>
creator = 'Patrik Dufresne'
dependencies = []
files = []
hgrepos = []
issue_num = 26269
keywords = []
message_count = 1.0
messages = ['259436']
nosy_count = 4.0
nosy_names = ['twouters', 'alanmcintyre', 'serhiy.storchaka', 'Patrik Dufresne']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue26269'
versions = ['Python 3.6']

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.