On Thu, Jan 21, 2021 at 4:43 PM Barney Gale wrote:
> Hi Brett,
>
> Per your PR review feedback [0] I left a comment on the bug [1] asking
> when the link_to() method should be scheduled for removal. It didn't elicit
> a great deal of feedback, so I'm raising this again here!
>
Per PEP 387 (https
Hi Brett,
Per your PR review feedback [0] I left a comment on the bug [1] asking when
the link_to() method should be scheduled for removal. It didn't elicit a
great deal of feedback, so I'm raising this again here!
The proposed deprecation warning in the docs currently reads:
> This method is de
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
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
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
