Expose DirEntry constructor

[moloney]

BPO	27796

^{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-08-18.19:38:12.339>
labels = ['type-feature']
title = 'Expose DirEntry constructor'
updated_at = <Date 2016-08-18.19:38:12.339>
user = 'https://bugs.python.org/moloney'

bugs.python.org fields:

activity = <Date 2016-08-18.19:38:12.339>
actor = 'moloney'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2016-08-18.19:38:12.339>
creator = 'moloney'
dependencies = []
files = []
hgrepos = []
issue_num = 27796
keywords = []
message_count = 1.0
messages = ['273063']
nosy_count = 1.0
nosy_names = ['moloney']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27796'
versions = ['Python 3.6']

[moloney]

As per a discussion on python-ideas [1], the consensus is that we should allow users to create a DirEntry object themselves. This would just take a path and call stat on it and cache the result of that stat call.

Nick Coghlan mentioned possibly allowing a pre-existing stat result to optionally be passed into the constructor [2].

[1] https://mail.python.org/pipermail/python-ideas/2016-August/041716.html
[2] https://mail.python.org/pipermail/python-ideas/2016-August/041713.html