Austin Scola added the comment:
Thank you Raymond! I learned a few things by reading the proposed documentation
updates.
--
___
Python tracker
<https://bugs.python.org/issue42
Austin Scola added the comment:
I think that type=pathlib.Path is probably all that I was looking for here. I
was unaware types could be passed easily like that and so updated documentation
would definitely be helpful. The predicates such as existence would just have
been nice-to-haves
Austin Scola added the comment:
Awesome, thank you for the guidance Eric. I'll start a thread on the
python-ideas mailing list, gauge the level of support, and go from there.
--
___
Python tracker
<https://bugs.python.org/issue42
Austin Scola added the comment:
Hey Eric,
Thanks for the response. I'm unfamiliar with the process of adding features to
the language. Would you mind explaining to me what some of the qualifications
are for getting something added to the stdlib? And also what role packages on
PyPI play
New submission from Austin Scola :
One of the types of arguments that I find myself most often passing to
`argparse.ArgumentParser` is paths. I think that I am probably not alone in
frequent usage of paths as arguments. Given this, it would be extremely helpful
to have an `argparse.Action
Austin Scola added the comment:
Okay, thank you for the explanation Eryk. It makes sense to me now why __eq__
doesn't attempt to compare something other than just the parts of the path.
--
stage: -> resolved
status: open -> closed
___
New submission from Austin Scola :
I think it would be more useful for the pathlib.Path.__eq__ method to test the
normalized path (not sure if normalized is the right terminology here).
As a concrete example I think that `PosixPath('/foo')` should equal
`PosixPath('/foo/../foo
