Nick Papior added the comment:
Ok, I can accept a no-fix ;)
I'll close this.
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Nick Papior added the comment:
Thanks for the discussion.
--
___
Python tracker
<https://bugs.python.org/issue45889>
___
___
Python-bugs-list mailing list
Unsub
Nick Papior added the comment:
It basically checks that some part of the path is the same as some part of a
reference path, they need not have the same complete parent which is why the
resolve command would negate this comparison always.
--
As for your last example, that will be quite
Nick Papior added the comment:
> Because of this I don't agree with your idea that anything that can match a
> path is a sub-path.
Why not? If a match is True, it means that what is matched must be some kind of
valid path matching a glob specification. Whether it is a regular expr
Nick Papior added the comment:
Ok, I see this a feature. :)
As for why it is desirable.
A part of a path is still a path, and matching for something must mean that you
are matching a partial path.
Even if you use '*.py' as the pattern this would still make sense as a path:
path = pl.Path
New submission from Nick Papior :
The documentation of Path.match only says it will match a pattern.
But quite often this pattern may be desirable to have as a Path as well.
import pathlib as pl
path = pl.Path("foo/bar")
print(path.match("bar"))
print(path.match(pl.Pa
Nick Papior added the comment:
FYI:
The problem arises since Intel adds a library path to:
../clck/2019.2.1/lib/intel64/
which has libutil.so!
This means that the Intel compiler *may* not find OpenPTY since that may
optionally be placed in libutil.so...
Simply removing the path from
New submission from Nick Papior :
When trying to compile Python without OpenPTY and without stropts.h the
compilation fails at Modules/posixmodule.c.
Apparently there is a failed logic in the def's.
It goes something like this:
#ifdef HAVE_OPENPTY
...
#elif defined(HAVE__GETPTY)
...
#else
Nick Papior added the comment:
Sorry I haven't responded previously.
Thanks a lot for helping me. I hadn't realized the `register` function.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Nick Papior:
Using argparse does not retain the Namespace variable across sub-parsers.
This prohibits customization of Actions due to "upper" level arguments not
being stored in the namespace passed to the sub-parsers.
Hence, one may not create different sub-par
10 matches
Mail list logo
