> On Nov 28, 2017, at 15:59, Paul Moore <[email protected]> wrote: > > On 28 November 2017 at 20:38, Barry Warsaw <[email protected]> wrote:
>> I had occasional to speak with someone very involved in Rust development. >> They have a process roughly similar to our PEPs. One of the things he told >> me, which I found very interesting and have been mulling over for PEPs is, >> they require a section in their specification discussion how any new feature >> will be taught, both to new Rust programmers and experienced ones. I love >> the emphasis on teachability. Sometimes I really miss that when considering >> some of the PEPs and the features they introduce (look how hard it is to >> teach asynchronous programming). > > That's a really nice idea. I'd like to see Python adopt something > similar (even just as a guideline on how to write a PEP). https://github.com/python/peps/issues/485 -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
