Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove 0.4 deprecations #16605

Merged
merged 6 commits into from
May 29, 2016
Merged

Remove 0.4 deprecations #16605

merged 6 commits into from
May 29, 2016

Conversation

tkelman
Copy link
Contributor

@tkelman tkelman commented May 27, 2016

not including the deprecated syntax in the parser, ref parts of #13054 which could be rebased

tkelman added 5 commits May 26, 2016 18:13
So these will now give MethodError for non boolean input
not including the deprecated syntax in the parser, ref #13054 which could be rebased
remove a blank line at the beginning of a function
after the "0.5 deprecations" comment was added but before the final tag
@tkelman
Copy link
Contributor Author

tkelman commented May 28, 2016

Any objections to doing this now? We haven't quite hit feature freeze but we're getting close. Someone who's written in scheme more recently than 2003 should clean up the parser deprecations that were introduced for 0.4.

@IainNZ
Copy link
Member

IainNZ commented May 28, 2016

Should be fun to watch PkgEval!

@tkelman tkelman merged commit 3ab92ef into master May 29, 2016
@tkelman tkelman deleted the tk/rmdeps branch May 29, 2016 01:37
@tkelman
Copy link
Contributor Author

tkelman commented May 29, 2016

Good thing we have that running on a nightly cron job then 😉

@tkelman
Copy link
Contributor Author

tkelman commented May 29, 2016

Surprising number of packages still using int or Uint - http://pkg.julialang.org/pulse.html (made a bit worse by the coin-or servers being down for maintenance this weekend, so anything depending on Cbc or Ipopt failed)

edit: DataArrays looks like the most common cause, interestingly it is referring to Base.int and extending it with new methods, which wasn't triggering a deprecation warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants