Re: [Python-Dev] Type hints -- a mediocre programmer's reaction
voice-from-audience burn the witch.. /voice-from-audience More seriously.. +1 to Harry voice. Adding type hints to function code is so ugly that that i'm breaking silence and i'm expressing it here before you, so: It's ugly Perhaps this question was asked a million times, but why not docstrings, which seems to be more elegant and natural place for that? I will not use it. Damn, if i had reputation this could be a threat. ;) On Mon, Apr 20, 2015 at 8:43 PM Barry Warsaw ba...@python.org wrote: On Apr 20, 2015, at 07:30 PM, Harry Percival wrote: tldr; type hints in python source are scary. Would reserving them for stub files be better? I think so. I think PEP 8 should require stub files for stdlib modules and strongly encourage them for 3rd party code. Cheers, -Barry ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/tymoteusz.jankowski%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] My thinking about the development process
I did a pull-request with current progress: https://github.com/python/psf-salt/pull/25 Any feedback is appreciated. Btw: Donald is very patient and helpful. :) On Thu Jan 08 2015 at 8:00:59 AM Nick Coghlan ncogh...@gmail.com wrote: On 6 December 2014 at 06:04, Brett Cannon bcan...@gmail.com wrote: # Next steps I'm thinking first draft PEPs by February 1 to know who's all-in (8 weeks away), all details worked out in final PEPs and whatever is required to prove to me it will work by the PyCon language summit (4 months away). I make a decision by May 1, and then implementation aims to be done by the time 3.5.0 is cut so we can switch over shortly thereafter (9 months away). Sound like a reasonable timeline? I've now updated PEP 474 to cover my current proposal for the support repositories, as well as some of the preparatory work that is already being undertaken: https://www.python.org/dev/peps/pep-0474/ By the end of the month, I'll also aim to have an updated version of PEP 462 published that considers how the forge.python.org service could potentially be extended to handle CPython itself, rather than attempting to build those flows directly into the existing Roundup and Rietveld based approach. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ tymoteusz.jankowski%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
