Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 01ab9634601fc1a4f9ac5d72ddc022239d2543fe authored by Miss Islington (bot) on 18 July 2020, 21:39:02 UTC, committed by GitHub on 18 July 2020, 21:39:02 UTC 
bpo-41295: Reimplement the Carlo Verre "hackcheck" (GH-21528)
 

Walk down the MRO backwards to find the type that originally defined the final `tp_setattro`, then make sure we are not jumping over intermediate C-level bases with the Python-level call.

Automerge-Triggered-By: @gvanrossum
(cherry picked from commit c53b310e5926266ce267c44a168165cacd786d6e)

Co-authored-by: scoder <stefan_ml@behnel.de>
1 parent 27b8110
Raw File
Tip revision: 01ab9634601fc1a4f9ac5d72ddc022239d2543fe authored by Miss Islington (bot) on 18 July 2020, 21:39:02 UTC
bpo-41295: Reimplement the Carlo Verre "hackcheck" (GH-21528)
Tip revision: 01ab963
CODE_OF_CONDUCT.md 
# Code of Conduct

Please note that all interactions on
[Python Software Foundation](https://www.python.org/psf-landing/)-supported
infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties)
by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
which includes all the infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).

In general, this means that everyone is expected to be **open**, **considerate**, and
**respectful** of others no matter what their position is within the project.
back to top