Add LegacyStrings for julia 0.5 compatability

[davidanthoff]

This should make things run on current julia 0.5 builds.

[coveralls]

Coverage decreased (-58.3%) to 0.0% when pulling 7c23be6 on davidanthoff:legacystrings into 494f831 on stevengj:master.

[davidanthoff]

I just realized that the travis config still relies on the staticfloat PPA, which is not maintained and won't give us a recent julia 0.5 build. I think that explains the CI errors. I'll try to figure out what to do about the travis stuff.

[stevengj]

This should not be needed with PyCall master, thanks to cd80a6e

[stevengj]

See also #295

[davidanthoff]

Ah, I had tried master but hadn't run Pkg.build.

[davidanthoff]

@stevengj Could you tag a new version? Would be really helpful to have a tagged version that runs on 0.5 RC0 so that downstream packages can more easily be brought in shape for 0.5. If that version still has deprecation warnings, no problem, but having something that doesn't error out would be great.

[stevengj]

Yeah, I'm planning on tagging new versions of a bunch of my packages in the next couple of days.

[davidanthoff]

Cool. I think PyCall especially would help. The downstream packages really need a tagged version that works on travis and appveyor to get their julia 0.5 porting working. I actually don't need a version that doesn't throw deprecation warnings, from my point of view just a tag on the current master would already help a great deal. The deprecation warnings could be fixed later, they don't really stop downstream packages from getting their stuff in order.

[stevengj]

JuliaLang/METADATA.jl#5793