> I agree with Nick, this is indeed big, but not impossible. If you are not sure yet whether you will work on implementation, you can focus on polishing the PEP text, and then if it is accepted and you will decide to give implementation to someone else, we will find a volunteer.
Unless I'm misunderstanding something, it seems that the OP is under the impression that because they authored the PEP, they're obligated and responsible for the entire implementation. Instead, we should be able to relatively easily split up the implementation into multiple self-contained PRs. The OP can still work on some of them if they want to and are able to, but other contributors can work on other parts of it. The easiest way of doing this would likely be separating each self-contained PR into a bullet point in a bpo issue with a brief description (similar to the layout posted above), and then the OP can work through them as they have time to do so. Any other contributor can simply pick up where the OP left off, or on other parts of it while the OP is working on something else. This would of course be after/if the PEP is accepted. On Mon, Nov 4, 2019 at 7:33 AM Ivan Levkivskyi <levkivs...@gmail.com> wrote: > On Thu, 31 Oct 2019 at 23:20, Nick Coghlan <ncogh...@gmail.com> wrote: > >> [...snip...] >> >>> >>> It's not enough to move the typing classes, I must move >>> functools.lru_cache() and dependencies, collections.abs.Mapping and >>> dependencies, and track the frame level. >>> >>> *It's too big for me.* >>> >>> >> It's certainly not an easy project to tackle. >> >> For some of the specific points you raise though, you wouldn't translate >> the existing Python code directly to C. >> > > I agree with Nick, this is indeed big, but not impossible. If you are not > sure yet whether you will work on implementation, you can focus on > polishing the PEP text, and then if it is accepted and you will decide to > give implementation to someone else, we will find a volunteer. > > -- > Ivan > > > _______________________________________________ > 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/AKXBKSBYESEJVKAAPCXHG4Z5EWOS54MM/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ 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/YYAKCVANFGRJAVGML4WJ225M5ANYZFDD/ Code of Conduct: http://python.org/psf/codeofconduct/
