-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[release-0.4, RFC] backports for 0.4.1 #13834
Conversation
When working with Sublime as my default editor on OS X I had set my editor to: EDITOR=/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl Since the `ispath` function did not recognize this as a path (because contained a backslash) this resulted in my editor not being recognized as "subl" and line number support being unavailable. The section of `edit` that deals with determining the user's editor has been abstracted into a new function `editor`. Test cases have been added for `editor` along with some basic tests for `shell_split`. Note that `startswith` is used to identify alternative editor names: - Sublime Text can refer to "subl" or "sublime". - Emacs can refer to "emacs" or "emacsclient". (cherry picked from commit 53fcec2) ref #13032
(cherry picked from commit d5edd11)
(cherry picked from commit 09c9a19)
Docs attached to numbers weren't being found. Finding docs for specific methods using the syntax help?> f(::Int) wasn't being recognised due to changes in how `gen_call_with_extracted_types` generated an error when it failed. (Previously the error was thrown by the function, but is now returned as an `:(error("..."))` expression.) (cherry picked from commit 446ddaa) ref #13535
Removed test for a non-working example and added clearer doctest example instead. (cherry picked from commit 0e498d3)
(cherry picked from commit d06e348)
Docstrings defined before `==` is available for `Symbol` comparisons causes a build error. Fix by comparing with `===`. Ref: #13534 (comment) (cherry picked from commit d8b6a24) ref #13602
The Images failure looks due to a specific instance of random numbers. I'll have to investigate and likely change that test, but for your purposes you can ignore that particular error. |
For your benefit, justifications for #13803 include: it's necessary for jump-dev/JuMP.jl#604 and would allow operations like using SIUnits.ShortUnits
A = [1m 2m; -1m 5m]
v = [3m,-1m]
A*v to become type-stable (currently it returns a non-leaftype as a mechanism to circumvent what would otherwise be an error). That said, I also recognize the risk. As I stated elsewhere, since I'm obviously biased I would prefer to defer to others in making the decision about whether to include it. The patch list looks delicious, very much looking forward to 0.4.1 even if nothing else gets added. |
fix #13810 fix #13806 fix JuliaParallel/DistributedArrays.jl#6 (cherry picked from commit 843ab66)
Now that OpenBLAS v0.2.15 has been merged to the master branch (#13808), I vote for including it in the backports for 0.4.1. I am assuming that the OpenBLAS API stayed the same. Many bugs and performance issues have been fixed in the 7 months since the last OpenBLAS release, and they include showstoppers for me in using Julia. |
Scroll up, it's already here a3f7c1f Though when I ran the microbenchmarks it did look like randmatstat got about 15% slower, which might be attributable to the new version of openblas? |
I was wrong to blame openblas, it was actually 1fc2d8e that was responsible for the 15% slowdown in rand_mat_stat. DataArrays has still not been tagged to work with #13803. I could be convinced to maybe pull #13491 and #13553 in here if perf and PackageEvaluator look okay on them, but unless someone argues for them I'm inclined to leave them until the next point release. |
@tkelman - thanks for the clarification. |
Is there a rough ETA on the next tagged bugfix? Some students are asking about it in @alanedelman's class. |
This weekend probably. Asked for input and opinions above and have yet to get any other than from Tim. On Wed, Nov 4, 2015 at 11:14 AM -0800, "Jake Bolewski" notifications@github.com wrote: Reply to this email directly or view it on GitHub: |
https://gist.github.com/c4ae8dfc79bdc2111f7e Most of the failures are either intermittent things I've seen before, or odd issues that only happened on the 0.4.0 baseline run where some unrelated package gives something like Will merge and tag shortly unless anyone wants to advocate that anything remaining on the checklist in the first comment is must-do-now. |
[release-0.4, RFC] backports for 0.4.1
🚂