On Fri, Mar 23, 2018 at 1:47 PM, Jason Maldonis > > I can find the time I'll write the PEP (although I'd rather just > contribute to it). Figuring out what to include and how to change the > methods' APIs seems like one of the easier PEPs to write in terms of > required knowledge (I don't know much about python's C code), so hopefully > I would have a chance at doing an adequate job. If you think not, please > tell me and I won't bother :) >
Most of PEP writing (at least for a PEP like this) is capturing the debate and conclusions and capturing and moderating the discussion to some extent -- technical knowledge is the least of it. I expect you'll get plenty of help on the technical issues if there are any (I'm say if, 'cause at this point it doesn't look like anyone is proposing any *new* functionality, it's really just moving and renaming things. I suggest by starting with the a PEP outpine from a previous PEP, getting it into a a gitHub repo (it can start in your own account somewhere, then go through this thread to start sorting out the issues. I say gitHub repo 'cause then it's easy to publish and collect comments and improvements in a central place - CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
