[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:48:06 CET 2014
- Previous message: [Python-Dev] The desired behaviour for resolve() when the path doesn't exist
- Next message: [Python-Dev] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 07 Jan 2014 22:45:54 +0200 Serhiy Storchaka <storchaka at gmail.com> wrote:
07.01.14 22:28, Antoine Pitrou написав(ла): >> 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.
--canonicalize is not strict. --canonicalize-existing is most strict and --canonicalize-missing is least strict. When you have a function which have non-strict behavior (--canonicalize), you can implement a wrapper with strict behavior (--canonicalize-existing), but not vice verse.
Yes, I meant --canonicalize 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] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]