I very much agree, adding deprecation warnings should be treated as a feature change, i.e. those should really go in before a feature freeze (whereas for 0.4 very many went in even after RC1), but at least before the RC sequence starts.
From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of Iain Dunning Sent: Saturday, October 17, 2015 8:50 AM To: julia-users <julia-users@googlegroups.com> Subject: Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated' @Kristoffer, it definitely was a bit short, but not for the reason you'd think. The types were deprecated very early in 0.4 development (mostly), but code to generate warnings wasn't added until quite late. Definitely an oversight, several of us have been fixing them wherever we can. Won't happen again for 0.5. On Saturday, October 17, 2015 at 11:26:39 AM UTC-4, Forrest Curo wrote: Thanks, all! Most of my booboos seem to be due to the fact that julia doesn't like 'foo ()' anymore, she now prefers 'foo()' which I suppose makes the parsing simpler. And I now know where to find that pesky tk button code... On Sat, Oct 17, 2015 at 8:00 AM, Kristoffer Carlsson <kcarl...@gmail.com <javascript:> > wrote: You can start julia with -depwarn=no to turn off deprecation warnings. On a personal note, I think that the time between type deprecation and the release was possibly a bit short. It feels that whatever package I import now I get pages of deprecation warnings. This is particularly inconvenient in IJulia sessions.
