bpo-34526：[doc] Add description and examples of multiple arguments for Path.relative_to

[lvluling]

the docs for Path.relative_to is a bit confusing why other is a star-args, especially as no example actually passes more than one argument to relative_to

https://bugs.python.org/issue34526

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@lvluling

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

[CharlieZhao95]

Thanks. You missed the definition of class PurePath in the context, it could be changed from :class:PurePath to the class PurePath.

[JelleZijlstra]

@barneygale would you be able to review this PR?

[barneygale]

I've left a comment on the #78707. I don't think relative_to() and is_relative_to() should accept multiple arguments - I'd rather we restricted this to methods that explicitly deal with path construction - PurePath() and PurePath.joinpath().

[barneygale]

In #94469 we deprecated passing multiple positional arguments to relative_to(), so I think this patch is no longer valid. Thank you for working on it all the same!