-
Notifications
You must be signed in to change notification settings - Fork 46
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
Updated for 1.0 #54
Updated for 1.0 #54
Conversation
Any change for merging this and tagging a new release soon? It would be great to get |
It'd be great for me to have this work by the end of the week; otherwise, I'll be using 0.7 in my course this semester :-} |
Thank you for submitting. Will you please enable tests on julia 0.7 and 1.0? To do this we need to change these lines to also include Once we see that this fix changes tests we will be good to merge. |
It seems it's the test infrastructure itself that fails, as it uses |
That is, rather than |
The following should work:
|
@mlhetland yes, that's what some other packages seem to use. |
Maybe something @sglyon wants to address? (Or should I change it? Not sure where the Travis infrastructure is, ATM, but I’m sure it’s possible to find it :-)) |
I think we should make that change -- it is what I would do myself so if you are willing to do it on this branch that'd be great! |
Didn't notice that it was all just further down in the Travis-file xD Fixed. |
Hm. I thought I tested it with 1.0, but it seems maybe I only tested with 0.7 for deprecation warnings. Still importing |
Well, one problem is that we'll need |
Codecs has been tagged, but not merged JuliaLang/METADATA.jl#16489 . |
Oh, OK. |
Anyway: I've tested with Julia 0.6, 0.7 and 1.0, and the tests run fine locally for me. But then, of course, I use |
So I guess as soon as we get the right version of |
Sounds great, thank you for all the work here. Please notify us on this thread when I should review and prepare to merge |
What is the status of this PR please? We need a 1.0 compatible version of YAML for BioJulia packages ASAP, but don't want to tread on toes of people already working on PRs :) |
Codecs.jl v0.5.0 has been release which works for julia v0.7 / v1.0, if this PR uses that version it should pass? |
The holdup has been that Codecs 0.5 hasn't been merged into METADATA. If you can specify specific tags or branches in your requirements, you could always just use this PR and 0.5 of Codecs directly. I could add a tag, if that's useful (i.e., rather than checking out the branch). But using As soon as Codecs 0.5 is in METADATA, the checks here should pass, I guess, yes. |
Ok great, thank you for the update |
I’m on my phone right now, so it’s a bit awkward to check, but I believe |
@mlhetland Codec 0.5 is indeed available now. If you have access to the travis you re-run the CI checks. |
Hm. If I do have access, I at least can’t figure out how. (Wouldn’t I need write access to this repo? Am I missing something?) |
Just thought I'd push a change to trigger a new check – so I added a |
Being too clever here, I guess – breaking stuff. (Tricky when I can't test the CI stuff locally…) The deprecation warning for |
See e.g Weave for travis config that works with project.toml https://github.com/mpastell/Weave.jl/blob/master/.travis.yml |
Ah – yeah, I looked at Weave (since I assumed you were up to date, given the discussion earlier :-). I just didn't want to hack around too much, and wasn't sure which parts worked with Julia 0.6 (given that some parts of it don't). If you have a suggested edit for the YAML Travis file, I'd be happy to implement it :-) |
I'm having a look at it now. |
All done, and ready to merge! (cc @sglyon) |
Now that |
Merged thank you! |
Thanks for merging @sglyon |
Now getting a release would be great, so this becomes available without using |
I’m coming to this only now of course and I don’t know how the versioning has been done previously.
I tried to release a v0.2.2 in line with your Project.toml, but attobot yelled at me - the metadata url is still set to the old repo, so I’ve submitted a PR to fix that and then v0.2.2 can get released without a hitch.
Best,
Ben.
… On 16 Aug 2018, at 13:03, Magnus Lie Hetland ***@***.***> wrote:
Now getting a release would be great, so this becomes available without using YAML#master… :-> (BTW, my Project.toml already says version = 0.2.2.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADPejZgACaOVT1N-gVZS2NFPY9NLARqtks5uRV-lgaJpZM4V1T9H>.
|
Actually the version number is going to be v0.3.0, since julia 0.5 support is dropped, and previous v0.2.x versions supported julia 0.5, METADATA CI is making me increment the minor version number (as it should to be fair!). |
Ah, sure. You should edit |
* Updated for 1.0 * Add tests for 0.7 and 1.0 * Add Pkg imports in 0.7+ * Remove start, next from 1.0 * Add Project.toml * Use Pkg.add in .travis.yml * Temporarily remove Project.toml * Reintroduce Project.toml
Updated to use new iteration protocol, if available. Importing
done
creates problems otherwise.