-
Notifications
You must be signed in to change notification settings - Fork 55
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
Upgrade to Julia 1.0 #104
Upgrade to Julia 1.0 #104
Conversation
This is WIP. Depends on fixing |
Now it is good for a review. I have it working under 1.0 with all core functionality. I did not do support (and they are commented out in tests) for two things:
Therefore, I would drop those two things (the second is more problematic as it is breaking in functionality - but maybe there is a simple and safe fix for this?). @nalimilan Any opinions about the best approach? I would want to tag a release of |
CC @tshort (as this is a major discussion point what I propose) |
I'm good with dropping those two items. Thanks for all the work here! |
Thank you for a prompt response. After thinking about it I have made two additional commits that clean up everything of The rationale is that If this proposal would be acceptable I would recommend merging the PR and tagging a release. |
I'm good with deleting all the CI tests on nightly, including Travis. |
I would leave them for now if you are OK with this as I expect that soon some minor bug release of Julia 1.0 might come out. |
That's fine. |
If this update is going to have breaking changes in it, should we consider #100. Since semantic versioning is so strict now its worth going over proposed breaking changes. |
I'm good with #100 and a semantic version bump. |
Cool! also keep in mind that #101 is essentially a bug-fix (fixing some edge cases that throw errors with @transdorm), so it can be added in at any time. |
Sorry, I'm a bit lost in the #101 thread :). |
Yup it got lost in the weeds a bit. A rebase might be in order for it since I think its trying to do too much. |
@pdeffebach I agree that it would be good to have #100 (I left a small comment there) and #101 in the release. I would propose the following process:
|
@@ -1,9 +1,10 @@ | |||
language: julia | |||
julia: | |||
- 0.6 | |||
- 0.7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also add 1.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added
README.md
Outdated
@@ -5,7 +5,7 @@ | |||
[![Travis](https://travis-ci.org/JuliaStats/DataFramesMeta.jl.svg?branch=master)](https://travis-ci.org/JuliaStats/DataFramesMeta.jl) | |||
[![AppVeyor](https://ci.appveyor.com/api/projects/status/github/juliastats/dataframesmeta.jl?branch=master&svg=true)](https://ci.appveyor.com/project/tshort/dataframesmeta-jl/branch/master) | |||
|
|||
Metaprogramming tools for DataFrames and Associative objects. | |||
Metaprogramming tools for DataFrames and AbstractDict objects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could add backticks while you're at it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
README.md
Outdated
the original `df` is not affected. Here is an example where two new columns are | ||
added: | ||
|
||
```julia | ||
df = DataFrame(A = 1:3, B = [2, 1, 2]) | ||
df2 = @byrow! df begin | ||
@newcol colX::Array{Float64} | ||
@newcol colY::DataArray{Int} | ||
@newcol colY::Array{Int} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe use Union{Int,Missing}
to illustrate that missing values are supported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed and added a case with missing
to show that it actually works.
@@ -155,28 +149,10 @@ functions. | |||
@select select Select | |||
|
|||
|
|||
Chaining operations is a useful way to manipulate data. There are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this no longer supported? I haven't followed the updates on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not work on Julia 1.0 due to Lazy.jl issues. The relevant test are also commented out. When it starts working again it should be reinserted after tests are uncommented (I have added a note there).
REQUIRE
Outdated
Compat 0.57.0 | ||
julia 0.7 | ||
DataFrames 0.13 | ||
Compat 1.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we get rid of the dependency on Compat?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
appveyor.yml
Outdated
- JULIA_URL: "https://julialangnightlies-s3.julialang.org/bin/winnt/x86/julia-latest-win32.exe" | ||
- JULIA_URL: "https://julialangnightlies-s3.julialang.org/bin/winnt/x64/julia-latest-win64.exe" | ||
- julia_version: 0.7 | ||
- julia_version: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd say better test 1.0, since we already have nightly to test recent versions. That way we ensure we still really support 1.0 (I know there's a debate going on about that).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
@@ -50,21 +50,6 @@ DMA = DataFrame( | |||
v3 = Array{Union{Float64, Missing}}(rand(N)) # numeric e.g. 23.5749 | |||
); | |||
|
|||
# DataArray version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better keep this to benchmark Array{Union{T, Missing}}
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a benchmark for Union{T, Missing}
in DataFrame
named DMA
.
@nalimilan if you approve this PR can you merge it so that #100 can be rebased? After #100 is merged I think we should tag a release. Thanks! |
Sure! |
Thanks! 😄 |
@@ -1,3 +1,2 @@ | |||
julia 0.6 | |||
DataFrames 0.11 | |||
Compat 0.57.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR takes out Compat, but src/DataFramesMeta.jl still imports it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#107 fixes this
Prepare a for a new release of DataFramesMeta.jl working on Julia 1.0.