Batuhan Taskaya <isidenti...@gmail.com> added the comment:
> That's exactly the implementation in the patch now submitted against this > issue. But that's the patch for CPython, the motive of the proposal here is > to establish a standard API call for *Python*, which different implementation > can implement how they like/can/need. I don't feel great about it, but if you are final motive is to address this issue for other implementations (like pycopy?), I still think that Python-ideas is the best place to discuss it rather than the bugtracker of CPython. > We should address them, one by one. I am not sure about that, IIRC @pablogsal and I talked these about a year ago and decided that there won't be any clear benefit (since nobody come with a need to it) and there will the downside of sometimes limiting ourselves for being backward-compatible for an API that ~almost no one will use. > That's how I usually do, but I posted too much there recently. I wanted to > submit a patch right away, but noticed that standard commit message format is > "bpo-XXXXX: ...", so I created a ticket here to reference in the commit. What people does in this cases is, they push to their branches with a random commit message (Implement blabla) and then share the link to the branch on their post in the Python-ideas. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42729> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
