-
Notifications
You must be signed in to change notification settings - Fork 9
FemtoCleaner for julia 1 #114
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
base: master
Are you sure you want to change the base?
Conversation
Fix AbstractTrees download command for local run Fix running FemtoCleaner.cleanrepo command Added Julia 6.4 download link Fixed non-working URLs Brought local running in Readme upfront
Update README.md Update .travis.yml Create Project.toml
Remove Base. for Distributed , Add HTTP dependency
Failed Travis |
I abandoned updating this. It is beyond my experience with Julia. Someone should know old syntaxes and then update this. The developers themselves should update this |
So the issue is that the syntax of the repo itself needs to be updated? |
Yes the FemtoCleaner/Deprecations should be written in Julia 1. Also, we need to address changes after Julia 0.6.4 in Deprecations so FemtoCleaner uses them. |
Can FemtoCleaner clean itself?!
Best,
Logan Kilpatrick
… On Sep 12, 2019, at 9:42 PM, Amin Yahyaabadi ***@***.***> wrote:
Yes the FemtoCleaner/Deprecations should be written in Julia 1. Also, we need to address changes after Julia 0.6.4 in Deprecations so FemtoCleaner uses them.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have already done this in this PR. But that is not enough because Deprecations doesn't address the changes after Julia 0.6.4 |
Too bad actual repository owners keep silence on this issue. |
My guess is that it would have been updated, but most repos don’t need this anymore so there’s not enough demand to make it worth it. The maintainers have many other things they need to help with that are likely more important than this repo.
Best,
Logan Kilpatrick
… On Oct 17, 2019, at 12:25 AM, Anton Kochkov ***@***.***> wrote:
Too bad actual repository owners keep silence on this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
If anyone wants to work on this, they responded to my old issue:
Answer:
|
Needs help.