You can actually start running it immediately for any package that does
claim to be 0.2 compatible. If they are not compatible, they should not use
any functionality that is deprecated in 0.3.
The best option will probably be to run PkgEvaluator with deprecations
removed (a few weeks before the deprecations is actually removed), so that
it opens issues for packages that will cause trouble.
Ivar
kl. 00:32:25 UTC+2 torsdag 17. juli 2014 skrev Tony Fong følgende:
>
> It's a little late now, but I have updated Lint.jl to warn on extending a
> deprecated function. It parses the deprecated.jl and keeps a list. If a new
> function definition "matches" the signature of a deprecated function, it'd
> give a lint error. The definition of a "match" is more relaxed than the
> typical invariant style w.r.t. ADT such as Array{ Real, 1} so it should
> catch reasonably specialized forms of a function.
>
> Hopefully it'd be more useful the next time we have API migration.
>
> On Thursday, July 17, 2014 2:12:04 AM UTC+7, Iain Dunning wrote:
>>
>> Hi all,
>>
>> If you updated to Julia 0.3-RC1 in the past couple of days, you may have
>> noticed issues with many packages. This was due to deprecated functions
>> that were deprecated in the previous release cycle being finally removed.
>> Most packages affected by this have fixed these minor issues so if you run
>> Pkg.update() you should be OK. Please do give 0.3-RC1 a good try so as many
>> bugs are flushed out before 0.3 is released as possible.
>>
>> Cheers,
>> Iain
>>
>
