Re: [Python-Dev] 3.4.4rc1, when?

On 10/4/2015 11:44 PM, Larry Hastings wrote: On 10/04/2015 06:26 PM, Terry Reedy wrote: When might 3.5.1 candidate be? No announcements yet! May I assume that you will give at least two weeks notice and that 3.5.1c1 will be at least 3 or 4 weeks off? -- Terry Jan Reedy

[Python-Dev] Not Deprecating Arbitrary Function Annotations

Congratulations on the release of 3.5 and Pep 484. I've used Python professionally for 10 years and I believe type hints will make it easier to work with large codebases evolving over time. My only concern about Pep 484 is the discussion of whether or not to deprecate arbitrary function

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

"They"? On Mon, Oct 5, 2015 at 12:57 PM, Ryan Gonzalez wrote: > There is one reason I would be really freaking mad if they deprecated > other uses of annotations: > > https://pypi.python.org/pypi/plac > > On October 5, 2015 1:55:37 PM CDT, Steve Wedig >

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

Function annotations for uses other than types are not deprecated, just discouraged if they don't have an appropriate decorator: https://docs.python.org/3/library/typing.html#typing.no_type_check . There is even a decorator for decorators since most uses previous to type hints utilized some form

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

PSF. Nothing personal, of course... On October 5, 2015 3:01:11 PM CDT, Guido van Rossum wrote: >"They"? > >On Mon, Oct 5, 2015 at 12:57 PM, Ryan Gonzalez >wrote: > >> There is one reason I would be really freaking mad if they deprecated >> other uses of

Re: [Python-Dev] 3.4.4rc1, when?

On 10/05/2015 11:42 AM, Terry Reedy wrote: On 10/4/2015 11:44 PM, Larry Hastings wrote: On 10/04/2015 06:26 PM, Terry Reedy wrote: When might 3.5.1 candidate be? No announcements yet! May I assume that you will give at least two weeks notice and that 3.5.1c1 will be at least 3 or 4 weeks

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

There is one reason I would be really freaking mad if they deprecated other uses of annotations: https://pypi.python.org/pypi/plac On October 5, 2015 1:55:37 PM CDT, Steve Wedig wrote: >Congratulations on the release of 3.5 and Pep 484. I've used Python >professionally

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

Maybe I should clarify how the process of changing the language works. The PSF doesn't enter into it -- they manage the infrastructure (e.g. mailing lists, Hg repo, tracker, python.org) but they don't have anything to do with deciding how or when the language changes. Language changes are done

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

Brett and Alexander, I am concerned about deprecation of arbitrary function annotations because Pep 484 suggests that two paths are under consideration. Here is the relevant section: " We do hope that type hints will eventually become the sole use for annotations, but this will require

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

On Mon, 5 Oct 2015 at 13:55 Steve Wedig wrote: > Brett and Alexander, > > I am concerned about deprecation of arbitrary function annotations because > Pep 484 suggests that two paths are under consideration. Here is the > relevant section: > > " > We do hope that type hints

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

Not really being affected by the "python annotation movement", I supply some non-constructive comment: I would not prefer any of these outcomes but would always allow all possible meanings that people wish to encode in the annotations. My $0.02 and I am out. On 05.10.2015 22:46, Steve

Re: [Python-Dev] Not Deprecating Arbitrary Function Annotations

Uh, I kind of knew that. Then I rushed the email and my brain momentarily left me. Sorry... On October 5, 2015 3:23:29 PM CDT, Guido van Rossum wrote: >Maybe I should clarify how the process of changing the language works. > >The PSF doesn't enter into it -- they manage the