On 2020-03-10 19:21, Stefan Behnel wrote:
Hi Petr!
Petr Viktorin schrieb am 14.01.20 um 14:37:
It also includes a more drastic change: it removes the MRO walker from the
proposal.
Reflecting on the feedback, it became clear to me that a MRO walker, as it
was described, won't give correct result
Hi,
Pathlib's symlink_to() and link_to() methods have different argument
orders, so:
a.symlink_to(b) # Creates a symlink from A to B
a.link_to(b) # Creates a hard link from B to A
I don't think link_to() was intended to be implemented this way, as the
docs say "Create a hard link point
Despite the bug being closed as WONTFIX, at the very least this seems like
a valid docs issue. But (for whatever a non-core-dev opinion is worth),
I'm +1 both on the proposed solution and deprecation.of `link_to()`
Jim
On Wed, Mar 11, 2020 at 10:45 AM Barney Gale wrote:
> Hi,
>
> Pathlib's sym
On Wed, 11 Mar 2020 11:17:22 +
Barney Gale wrote:
> Hi,
>
> Pathlib's symlink_to() and link_to() methods have different argument
> orders, so:
>
> a.symlink_to(b) # Creates a symlink from A to B
> a.link_to(b) # Creates a hard link from B to A
>
> I don't think link_to() was inten
Antoine Pitrou wrote:
> On Wed, 11 Mar 2020 11:17:22 +
> Barney Gale barney.g...@gmail.com wrote:
> > Hi,
> > Pathlib's symlink_to() and link_to() methods have different argument
> > orders, so:
> > a.symlink_to(b) # Creates a symlink from A to B
> > a.link_to(b) # Creates a hard link from B
