On Wed, Jan 8, 2014 at 4:45 AM, Serhiy Storchaka <storch...@gmail.com> wrote: > --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. >
Sorry, only now that I have time to look into this. So what we are going to do before implementing the behaviour for resolve(strict=False) is to change the behaviour of resolve(strict=True) from --canonicalize-existing to --canonicalize? Is there any time left because we are in RC1 already? Should we postpone it to 3.5? But then, we'll have backward compatibility problem. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
