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

Fix tests and deprecation warnings #14

Merged
merged 1 commit into from
May 17, 2015
Merged

Fix tests and deprecation warnings #14

merged 1 commit into from
May 17, 2015

Conversation

nalimilan
Copy link
Member

Using 'call' as a variable name currently triggers a bug in
Julia 0.4: JuliaLang/julia#11295
Work around it for now by using a different name.

Also get rid of deprecation warnings printed during the tests.

This PR currently breaks compatibility with 0.3. Should I use Compat.jl, or do you prefer creating a new branch for 0.4?

@tshort
Copy link
Contributor

tshort commented May 16, 2015

Thanks for the updates, @nalimilan! As far as compatibility, I prefer the Compat.jl option.

Using 'call' as a variable name currently triggers a bug in
Julia 0.4: JuliaLang/julia#11295
Work around it for now by using a different name.

Also get rid of deprecation warnings printed during the tests,
using Compat.jl where necessary.
@nalimilan
Copy link
Member Author

OK, I've added @compat calls. Tests now pass with both 0.3.8 and 0.4 master.

tshort added a commit that referenced this pull request May 17, 2015
Fix tests and deprecation warnings
@tshort tshort merged commit 383ce25 into JuliaData:master May 17, 2015
@tshort
Copy link
Contributor

tshort commented May 17, 2015

Thanks again, @nalimilan.

@nalimilan nalimilan deleted the deprecations branch May 17, 2015 11:15
@nalimilan
Copy link
Member Author

You're welcome. Should a new release be tagged?

@tshort
Copy link
Contributor

tshort commented May 17, 2015

Yes. Good point.
On May 17, 2015 7:16 AM, "Milan Bouchet-Valat" notifications@github.com
wrote:

You're welcome. Should a new release be tagged?


Reply to this email directly or view it on GitHub
#14 (comment)
.

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