[Python-Dev] GSOC
i want to contribute in mailman which is a sub-org under python software in GSOC there's 2 templates to submit i want to know which template is the correct one, the one in mailman's site or the one in python's site ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/CBVDOE7L2FBDSWB2IPZ3776TZ6Y2WGNL/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Accepting PEP 670 – Convert macros to functions in the Python C API
PEP 670 – Convert macros to functions in the Python C API: https://peps.python.org/pep-0670/ That's great! Thanks to everyone who was involved in PEP 670: the feedback helped Erlend and me to write a better PEP. It was a long journey, Erlend started the first discussion about macros in March 2021! https://discuss.python.org/t/what-to-do-with-unsafe-macros/7771 Victor On Tue, Apr 12, 2022 at 11:22 AM Petr Viktorin wrote: > > Hello, > The Steering Council is **Accepting** the latest iteration of PEP 670: > Convert macros to functions in the Python C API. Congratulations! > > > - Petr, on behalf of the Steering Council -- Night gathers, and now my watch begins. It shall not end until my death. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/YK2MOWYS3IOL3BQ3DBG7G7YF3MH7BBQM/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Do you ever use ceval.c's LLTRACE feature?
Hi, In 2017, I proposed to document the feature, but nobody was volunteer to write the doc (issue still open): https://bugs.python.org/issue25571 I added a bare minimum mention of this feature in the "Python Debug Build" documentation: https://docs.python.org/dev/using/configure.html#python-debug-build A bug was fixed in 2018, so it has at least one user :-) https://bugs.python.org/issue34113 In 2017, adding an API to trace instructions with sys.settrace() was discussed, but the idea got rejected: * https://bugs.python.org/issue29400 * https://mail.python.org/pipermail/python-dev/2017-September/149632.html IMO it would be more flexible than the current "lltrace" implementation which hardcode writing bytecode into C stdout stream which is not convenient and cannot be easily redirected. I have no idea if it would be possible to provide an *efficient* implementation of such hook in ceval.c, even if it's only implemented in debug build. Victor ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/M6R6EWL2FS5SZC4A3ZDIPZH2LI6G4TFO/ Code of Conduct: http://python.org/psf/codeofconduct/
