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

add istext -> istextmime #183

Merged
merged 1 commit into from
Apr 14, 2016
Merged

add istext -> istextmime #183

merged 1 commit into from
Apr 14, 2016

Conversation

stevengj
Copy link
Member

Compatibility for JuliaLang/julia#15708

@stevengj
Copy link
Member Author

stevengj commented Apr 14, 2016

I originally had if VERSION < v"0.5.0-dev+10878", which the version.sh script tells me is the correct version for the merge commit JuliaLang/julia@839f8c9 for JuliaLang/julia#15708, but the nightly build on Travis and AppVeyor still gave me a failure, claiming I was exporting istextmime when it was already defined by Base. So, I just switched it to if !isdefined(Base, :istextmime)

@stevengj stevengj merged commit e71e7f2 into master Apr 14, 2016
@stevengj stevengj deleted the textmime branch April 14, 2016 21:13
@tkelman
Copy link
Contributor

tkelman commented Apr 14, 2016

10000 sounds way too high, should be more like 3-4000. Something went wrong there.

@martinholters
Copy link
Member

I get 0.5.0-dev+3460 for that commit which sounds reasonable. But the !defined check works too, obviously.

@tkelman
Copy link
Contributor

tkelman commented Apr 15, 2016

@vtjnash mentioned somewhere having experienced "resistance" to basing things on isdefined instead of version numbers. How long ago was this and in what context, if you can remember? I think feature-checks are generally preferable to using version numbers.

@stevengj
Copy link
Member Author

I think the advantage of version checks is that it is obvious when they can be removed. e.g. if I see a VERSION < v"0.2-xxx" in my code, but I require Julia 0.4, then I can obviously remove the check. If I have isdefined(Base, :frob), figuring out whether it is safe to remove may involve digging through the Julia logs.

@stevengj
Copy link
Member Author

I just tried on another computer, and I get 0.5.0-dev+10878 from the Compat.jl version.sh script.

@stevengj
Copy link
Member Author

Oh, I see the problem. I need to do git pull --tags. I hate git sometimes...why doesn't it pull all the tags on the current branch by default?

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.

3 participants