[Python-Dev] The desired behaviour for resolve() when the path doesn't exist (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue Jan 7 21:28:41 CET 2014
- Previous message: [Python-Dev] The desired behaviour for resolve() when the path doesn't exist
- Next message: [Python-Dev] The desired behaviour for resolve() when the path doesn't exist
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 07 Jan 2014 17:26:20 +0200 Serhiy Storchaka <storchaka at gmail.com> wrote:
Behavior of --canonicalize-existing can be derived from --canonicalize, just check that resulting patch exists. But other modes can't be derived from --canonicalize-existing. def resolveexisting(path): path = path.resolve() if not path.exists(): raise FileNotFoundError(errno.ENOENT, 'No such file or directory: %r' % str(path)) return path So perhaps two main modes should be --canonicalize (default) and --canonicalize-missing (with missing=True)?
That sounds reasonable. And I think strict should be the default.
Regards
Antoine.
- Previous message: [Python-Dev] The desired behaviour for resolve() when the path doesn't exist
- Next message: [Python-Dev] The desired behaviour for resolve() when the path doesn't exist
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]