bpo-41287: Handle doc argument of property.__init__ in subclasses

[sizmailov]

Process explicit doc argument of property(...) in the same manner as docstring of getter function in property subclasses.

This eliminates behavior differences between dummy class Property(property): pass and property (see test case for example)

https://bugs.python.org/issue41287

[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).

CLA Missing

Our records indicate the following people have not signed the CLA:

@sizmailov

For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

If you have recently signed the CLA, please wait at least one business day
before our records are updated.

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

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

[github-actions]

This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[sizmailov]

unstale

[github-actions]

This PR is stale because it has been open for 30 days with no activity.

[MaxwellDupre]

Works for me.
./python -m test -v test_pydoc
Ran 74 tests in 32.947s
OK (skipped=3)
test_pydoc passed in 33.1 sec
== Tests result: SUCCESS ==
1 test OK.
Total duration: 33.1 sec
Tests result: SUCCESS
cpython on  fix-issue41287 [$?] via 🐍 v3.11.0a5+ took 33s

[JelleZijlstra]

Thanks, and sorry this took so long! Unfortunately this needs a merge conflict fixed now. It also needs a NEWS entry.

[sizmailov]

Rebased branch on current main, added NEWS entry, addressed review comments.
Hopefully CI would show no errors 🤞

[bedevere-bot]

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

[sizmailov]

I think I found the leak. Can we run CI one more time, please?

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @JelleZijlstra for commit fb8c2d4 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

[sizmailov]

Here are the last two things I want to add to this PR:

1. add a comment about prop_doc and
2. shortened version for the property branch.

I don't want to disrupt the current CI, so I'll push changes once it finishes.

EDIT: I pushed two more commits when CI reached 81 successful, 1 failure (same as in current main), and 1 stuck jobs.

[sizmailov]

@JelleZijlstra Could you please take another look at the PR :) This time everything should be in place.
Many thanks for the prompt CI trigger, it really helped to quickly check for errors, and saved my day!

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @JelleZijlstra for commit 36fc1b0 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

[JelleZijlstra]

I triggered the buildbots to make sure, I'll review the PR again tonight. Thanks for your work!

[JelleZijlstra]

Looks good, just a few typos in the comments

[JelleZijlstra]

Congratulations on your first contribution to Python!

[encukou]

This breaks subclasses that don't have a writable __doc__, see #98963

[gpshead]

Please see #105262 which restores the behavior this broke.