Yury Selivanov added the comment: > Yury, I'm more than happy to help! I've spent a decent amount of time > learning about code objects, byte code, etc. and I'd love to put that > knowledge to use. Let me know the best way to find these issues on the > tracker or otherwise.
Certainly! There seem to be a lot of issues with inspect.findsource and inspect.getsource functions. Quick search results: #28121 and #26890 (and I know there are few more open issues). For PEP 525 we need to add two new functions to the inspect module (I overlooked them and didn't add them to 3.6): inspect.getasyncgeneratorstate and inspect.getasyncgeneratorlocals (mirroring inspect.getgeneratorstate and inspect.getgeneratorlocals). There are some issues that nobody even replied to, like #26577. For those the protocol is usually to reproduce the problem first, and then make a patch/tests. You can use advanced search on this tracker to find issues like that one. If you are into async world, you can work on adding contextlib.asyncontextmanager decorator. Although this one should first be discussed on the python-ideas mailing list. Also, if you are into C programming, Victor Stinner, INADA Naoki and I are trying to optimize Python ceval loop from time to time (you knowledge of dis/opcodes can be helpful), so you can look for those kind of open issues too. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29354> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
