[julia-users] Re: invalid redefinition of constant MyType

You can put them in a module, and re-import it when you've changed the module file. :) http://docs.julialang.org/en/latest/manual/faq/#how-can-i-modify-the-declaration-of-a-type-immutable-in-my-session // Tomas On Thursday, May 8, 2014 8:34:23 AM UTC+2, K leo wrote: > > I defined a composite ty

Re: [julia-users] array with different column types

I myself have been hitting my head against the wall that is meta-programming in Julia. I think I can answer your first question at least. Q1: This is because the line poly = emptyPoly doesn't create a new copy of a ploygon but a reference to the empty one so that both poly and emptyPoly refer

Re: [julia-users] Pasting an expression inside a macro

The examples should definitely work, so please open an issue on github. Either the parsing or the example should be updated, but I don't know what. There is an issue to include the examples in the testing suite, but it seems like nobody has picke

Re: [julia-users] Julia: First Month

Am I right in thinking that the issues you have with function call overloading are equivalent to those involved with multiple inheritance? In the sense that overloading function application effectively makes an array (for example) a member of both AbstractArray and Callable, which will create ambig

Re: [julia-users] Importing Datetime data with microsecond fidelity

Hey Andre, Unfortunately there's nothing currently that would make this very easy. I'm actually in the middle of a big rewrite of the Datetime.jl package that will, among other things, include the possibility of handling something like this, but it's at least a few weeks away of anything practical

Re: [julia-users] Re: Simulating fixed-size arrays

Thanks, that's great! Maybe this should make it to upstream julia. Fixed-size arrays are essential to get good performance, and compact memory usage. -- Carlos On Wed, May 7, 2014 at 5:46 PM, Tobias Knopp wrote: > see https://github.com/JuliaLang/julia/

Re: [julia-users] How can a remote proc self-discover DArray localparts?

It can't. All part references are in the DArray object, `dz` in your example above. On Thu, May 8, 2014 at 1:07 AM, Rick Graham wrote: > How can a remote proc discover, on its own, that it is "hosting" a portion > of a DArray? > > Here a DArray is distributed across two workers, but the workers

Re: [julia-users] Julia: First Month

On Thursday, May 8, 2014 8:47:53 AM UTC+2, Stefan Karpinski wrote: > [...] And obviously in Matlab they're the same syntax, but since neither > functions nor arrays can be used in a higher order fashion, that hardly > matters. > I don't have Matlab at hand, but IIRC this produces the expected o

Re: [julia-users] Re: Simulating fixed-size arrays

Definately fixed-size arrays should be in base. The question is a little how this interacts with NTuple, which (if I understand this correctly) also be at some point "tight" fixed-size vectors. Am Donnerstag, 8. Mai 2014 11:03:08 UTC+2 schrieb Carlos Becker: > > Thanks, that's great! > > Maybe

Re: [julia-users] Importing Datetime data with microsecond fidelity

Jacob, Thanks for the update. I was really impressed with your previous Datetime.jl implementation. So I am thrilled to hear you are working on an update. Your response mentions the "possibility". Does this mean it might not include this functionality? Truncating might work. We could divide t

Re: [julia-users] ANN: JuMP 0.5 released with support for nonlinear programming

This is indeed really cool, and seems just the kind of thing that could be a compelling reason for a lot of people to use julia. -viral On Saturday, May 3, 2014 1:37:34 AM UTC+5:30, Stefan Karpinski wrote: > > Very impressive work – the automatic differentiation is particularly cool. > > > On Fr

[julia-users] Re: Static build

It is certainly high on the priority list, but won't be in 0.3. We are just about wrapping up the 0.3 release process. That said, 0.3 includes a lot of foundational work for compiling julia code into binaries, and the complete feature is not too far away. -viral On Thursday, May 8, 2014 12:16:

Re: [julia-users] Re: Simulating fixed-size arrays

Small fixed size arrays would certainly be great to have in Base. With the recent work on SIMD, certain operations could really end up with huge performance gains. -viral On Thursday, May 8, 2014 3:17:55 PM UTC+5:30, Tobias Knopp wrote: > > Definately fixed-size arrays should be in base. The qu

[julia-users] require("file.py")

Hello all, I have a basic .juliarc.jl script that adds various utility functions to LOAD_PATH - as described in previous posts: addpath and search path

[julia-users] Re: Function roots() in package Polynomial

Because I was a (tiny) bit unsatisfied with the Polynomial package, I wrote my own polynomial functions, like - polyval() to be applied to vectors as well as polynomial types - roots() that uses the Matlab order in constructing the companion matrix and finding all roots - horner() tha

Re: [julia-users] Re: Function roots() in package Polynomial

I'd suggest fit(Polynomial, data) instead of polyfit(data). The generic fit function is defined in StatsBase. 2014-05-08 14:23 GMT+02:00 Hans W Borchers : > Because I was a (tiny) bit unsatisfied with the Polynomial package, > I wrote my own polynomial functions, like > > - polyval() to be app

Re: [julia-users] Re: Function roots() in package Polynomial

Actually, I called it pfit(); is that name also given? I don't understand your signature because a polynomial will not be provided, only data and a degree. How can I see a list of function names in Julia, JuliaBase, ... and packages on the METADATa list. [As long as I really don't understand the

Re: [julia-users] ANN: JuMP 0.5 released with support for nonlinear programming

This is really great, guys. I was impressed by JuMP the first time I used it, and I'm certain I will be again next time I have reason to use it. On Thu, May 8, 2014 at 3:41 AM, Viral Shah wrote: > This is indeed really cool, and seems just the kind of thing that could be > a compelling reason

Re: [julia-users] Re: Function roots() in package Polynomial

Sorry for being too brief. My notation was not clear. The first argument should be a type and not an instance. This is becoming the standard way of fitting models deriving from StatsBase and Distributions. Hence, provided that your polynomial type is parametrised by its degree, the definition could

Re: [julia-users] Re: macro for generating functions with optional arguments

I'm not sure I understand. Except for one particular situation (tuple arguments), declaring the type of inputs has no impact on performance. The JIT will compile a separate version of the function for each different set of input types. See the "performance tips" section of the manual. --Tim On

Re: [julia-users] Re: Static build

See https://groups.google.com/d/msg/julia-dev/qdnggTuIp9s/BoQSNGNXxV0J On Thursday, May 08, 2014 03:48:58 AM Viral Shah wrote: > It is certainly high on the priority list, but won't be in 0.3. We are just > about wrapping up the 0.3 release process. That said, 0.3 includes a lot of > foundational

Re: [julia-users] array with different column types

Replace your macro with a function and delete the uses of eval. You code will be faster, and easier to understand. Most of the difficulty people seem to have with macros comes from thinking they are a type of function call -- the @ character is supposed to remind you that this is not true. On Thur

Re: [julia-users] Re: macro for generating functions with optional arguments

That makes sense. The other (primary) reason I want this is still valid: assisting multiple dispatch (and clarity for other developers) by having the correct types on optional arguments. Since there are no objects for encapsulation of related behaviors, the only good way to explore an API (othe

[julia-users] Re: require("file.py")

Arh my bad. Looks like I just needed to set my PYTHONPATH. Oliver Den torsdag den 8. maj 2014 14.06.49 UTC+2 skrev Oliver Lylloff: > > Hello all, > > I have a basic .juliarc.jl script that adds various utility functions to > LOAD_PATH - as described in previous posts: > addpath

[julia-users] [newb] array aliasing

Is the following well-defined in julia? julia> x = [1:10] 10-element Array{Int64,1}: 1 2 3 4 5 6 7 8 9 10 julia> x[1:9] = x[2:10] 9-element Array{Int64,1}: 2 3 4 5 6 7 8 9 10 In general, are all such aliased assignments well-defined (all, as in for arbitrary

Re: [julia-users] Re: macro for generating functions with optional arguments

I agree that declaring types is an effective way of increasing clarity. (Fundamentally I suspect that suggests inadequacies in our documentation.) Aside from the more "valid" use in controlling which version of a function will run on which types of data. However, you don't have to leave off typ

Re: [julia-users] array with different column types

Thank you Johan and Jameson. Johan, I don't know how to make a loop on the fields with a function. For example this doesn't work: function removeLine(poly::Poly, index::Int) for op = (:a, :b, :x1, :y1, :x2, :y2, :typ) splice!(poly.$op, index) end end How to do, please ? L

Re: [julia-users] Re: macro for generating functions with optional arguments

That doesn't seem to work with composite types and Nothing. Using a day-old nightly build: julia> type MyType; end julia> example(x::Int, mt::MyType=nothing) = println("in example") example (generic function with 2 methods) julia> example(1) ERROR: no method example(Int64, Nothing) in example

Re: [julia-users] Shared read-only memory?

Given that there's a lot in your head about your application that I don't know, perhaps I should stop guessing about what you're trying to do and just make sure the principles are clear: 1. The more data you have to serialize and send to other processes, the slower it will be. The key thing abo

[julia-users] delete some entries of a n*1 array

Hello, Assume I want to delete the first and the third entries of this array: julia> x = [3,5,9,7] 4-element Array{Int64,1}: 3 5 9 7 How to do ? Using !splice I can only delete one entry or a range.

[julia-users] Pre-compiling packages in Userimg.jl

I've understood that it's possible to pre-compile stuff into something called userimg.jl, but I'm struggling to find information on *how* to do this. Primarily, I'd like to compile a few packages I find myself including very often (and never changing), such as Gadfly and DataFrames. I suppose i

[julia-users] Re: delete some entries of a n*1 array

deleteat!(x,(1,3)) But am I missing something or are splice! and deleteat! a little redundant? Am Donnerstag, 8. Mai 2014 16:49:58 UTC+2 schrieb Stéphane Laurent: > > Hello, > > Assume I want to delete the first and the third entries of this array: > > > julia> x = [3,5,9,7] > > 4-element Array{

[julia-users] Re: macro for generating functions with optional arguments

On Friday, February 21, 2014 9:36:07 PM UTC+1, Joosep Pata wrote: > #2) def. value in expression, does not work > ex = :(x=1) > q = quote > function f2($ex) > x > end > end > println("does not work") > macroexpand(q)|>println > eval(q) > f2()|>println > ~

[julia-users] Re: delete some entries of a n*1 array

julia> deleteat!(x, 1) ErrorException("deleteat! not defined") Le jeudi 8 mai 2014 17:00:01 UTC+2, Tobias Knopp a écrit : > > deleteat!(x,(1,3)) > > But am I missing something or are splice! and deleteat! a little redundant? > > Am Donnerstag, 8. Mai 2014 16:49:58 UTC+2 schrieb Stéphane Laure

[julia-users] Re: delete some entries of a n*1 array

Ah sorry I am on Julia 0.3 prerelease Am Donnerstag, 8. Mai 2014 17:07:10 UTC+2 schrieb Stéphane Laurent: > > julia> deleteat!(x, 1) > > ErrorException("deleteat! not defined") > > > > Le jeudi 8 mai 2014 17:00:01 UTC+2, Tobias Knopp a écrit : >> >> deleteat!(x,(1,3)) >> >> But am I missing someth

Re: [julia-users] array with different column types

You can still use meta-programming to generate the code function removeLine(poly, index) for op = (:a, :b, :x1, :y1, :x2, :y2, :typ) @eval splice!($poly.$op, $index) end end On Thursday, May 8, 2014 5:40:35 PM UTC+3, Stéphane Laurent wrote: > > Thank you Johan and Jameson. > > Joh

Re: [julia-users] array with different column types

No that generates an error: ErrorException("error compiling removeLine: syntax: prefix \$ in non-quoted expression") Le jeudi 8 mai 2014 17:09:24 UTC+2, Johan Sigfrids a écrit : > > You can still use meta-programming to generate the code > > function removeLine(poly, index) > for op = (:a,

[julia-users] duplicated inline plots in IJulia

Hi, Is anyone else seeing duplicated output from PyPlot in conjunction with IJulia in inline mode recently? This does not appear with Gadfly, nor with pyplot in IPython. Cheers, Joosep

Re: [julia-users] array with different column types

I have also tried with eval(quote ... end) but unsuccessfully.

Re: [julia-users] array with different column types

Works for me both with @eval and eval(quote ... end). Maybe you are using a different version of Julia. I'm on the latest Windows nightly. On Thursday, May 8, 2014 6:18:27 PM UTC+3, Stéphane Laurent wrote: > > No that generates an error: > > ErrorException("error compiling removeLine: syntax: pr

[julia-users] macro for generating functions with optional arguments

In your example, nothing is of type Nothing, which is not a MyType, so the assignment fails. Tim, for kw arguments, is it true that new functions are specialized for each type? I'm thought that it wouldn't, which would cause the variable to be an actual Union type if declared as such, and therefo

Re: [julia-users] array with different column types

If I'm using your code verbatim I get julia> removeLine(poly,1) ErrorException("type Poly has no field op") julia> versioninfo() julia> Julia Version 0.2.0 julia> Commit 05c6461 (2013-11-16 23:44 UTC) Platform Info: System: Windows (x86_64-w64-mingw32) WORD_SIZE: 64 BLAS: li

Re: [julia-users] delete some entries of a n*1 array

deleteat! discards elements and returns the modified array. It also accepts disjoint locations or ranges (I think), in sorted order. On the other hand, splice! accepts a single location or range, copies and returns the removed elements, and optionally allows them to be replaced in the original arr

[julia-users] Re: macro for generating functions with optional arguments

Thanks to all for the responses! Pierre, you have made me positively giddy. Your response was enough to make Julia's metaprogramming finally "click" for me, and now I realize how incredibly powerful it is. I was able to make something even better than I'd hoped for. Once I realized how easily y

[julia-users] Re: Pre-compiling packages in Userimg.jl

It's currently undocumented, and perhaps rightfully so. Not all packages support pre-compilation, and it can cause a few other problems, too (I think https://github.com/JuliaLang/julia/issues/6657 is related to having a userimg.jl file). Also note that each time you update your packages, you'

[julia-users] Re: macro for generating functions with optional arguments

I could see the potential for others to want to use this, so I made a gist for it: https://gist.github.com/sunetos/0714ae73647160d76aae As an aside, I'm really not sure why I didn't understand macros better until Pierre's comment; I had read the metaprogramming docs

Re: [julia-users] array with different column types

Apparently its something that's been fixed or changed after 0.2. It works fine on 0.3. On Thursday, May 8, 2014 7:03:03 PM UTC+3, Stéphane Laurent wrote: > > If I'm using your code verbatim I get > > julia> removeLine(poly,1) > > ErrorException("type Poly has no field op") > > > > julia> versioni

Re: [julia-users] Re: macro for generating functions with optional arguments

Long ago I began a project to add exercises (with answers) to the documentation. We needed better web infrastructure (and more/better problems) to make that practical, so that was abandoned. But for metaprogramming I can imagine that a few exercises might help it click. --Tim On Thursday, May

Re: [julia-users] Re: macro for generating functions with optional arguments

It's only been recently that macros really clicked for me, too. I think it might help to stress that macros aren't all that special. They are essentially functions that take expressions as arguments, and return an expression. What is special is how they're invoked and how the returned expres

Re: [julia-users] Re: macro for generating functions with optional arguments

I wholeheartedly agree that the documentation for macros would benefit from the use of explicit returns to make the analogy to functions more clear. I think the other main source of confusion with macros is that they're "one-time only" functions that execute exactly once when the compiler first

Re: [julia-users] Re: macro for generating functions with optional arguments

Tim: I like that idea. I also think Julia is getting pretty close to the point where one of those "watch me build a in julia in 10 minutes" videos on would be popular on HN; those can be really informative for learning effective workflows in a new environment. The release of v0.3 might be a go

Re: [julia-users] Re: macro for generating functions with optional arguments

Matt, John: Making the return explicit is a great idea, and maybe also clarify the input to a macro is also an instance of Expr. It's inferable from the docs, but if you just jump the "macro" section of the page, it's not obvious. Clearly stating that a macro is a function mapping an Expr to an

[julia-users] Re: macro for generating functions with optional arguments

On Thursday, May 8, 2014 6:47:03 PM UTC+2, Adam Smith wrote: > Thanks to all for the responses! Pierre, you have made me positively > giddy. Your response was enough to make Julia's metaprogramming finally > "click" for me, and now I realize how incredibly powerful it is. I was able > to make s

[julia-users] Re: exit codes from a processchain?

I think I see how. processchain.processes[2].exitcode is the exitcode for the seconds process in the pipeline. On Wednesday, May 7, 2014 12:58:06 PM UTC-7, ken...@sdsc.edu wrote: > > > I am doing a readsfrom(`firstprocess` |> `secondprocess`). How do I > extract the exit codes for each process

Re: [julia-users] Re: Function roots() in package Polynomial

Thanks; I really appreciate all your efforts. But no, as far as I understand, the Poly type in Polynomial is not parametrized by a degree. I think there was a discussion lately, "How can Julia recognise the degree of a polynomial", that might be relevant. You see, I am a hard-core numerical ana

Re: [julia-users] array with different column types

Sorry, actually it works. Maybe there was a problem previously because of JuliaStudio. Sometimes when I copy-paste some code in the JuliaStudio console it is not executed. Thanks for your help.

Re: [julia-users] array with different column types

A = :fieldname X.(A) == getfield(X, A) On Thursday, May 8, 2014, Johan Sigfrids wrote: > Apparently its something that's been fixed or changed after 0.2. It works > fine on 0.3. > > On Thursday, May 8, 2014 7:03:03 PM UTC+3, Stéphane Laurent wrote: >> >> If I'm using your code verbatim I get >

Re: [julia-users] array with different column types

Cool, thank you Jameson. So what is the best choice between these two possibilities : function removeLine(poly::Poly, index::Int) for op = (:a, :b, :x1, :y1, :x2, :y2, :typ) @eval splice!($poly.$op, $index) end end function removeLine2(poly::Poly, index::Int) for op = (

[julia-users] Re: Pre-compiling packages in Userimg.jl

I believe you are referring to this thread https://groups.google.com/forum/#!msg/julia-dev/qdnggTuIp9s/R2eCdspk-ukJ I think that the framework is there to have packages that can be precomplied into .so so that we don't have to wait 5 to 6 seconds each time we need to load a package into the ju

Re: [julia-users] Natural language processing in Julia

Hi all, I am interested in writing Natural Language Processing (NLP) tools in Julia. My name is Sorami, I am a data scientist at BrainPad Inc. in Tokyo, Japan. I used to be a graduate student doing NLP. I am much interested in Julia, and I see its great potential as a powerful NLP / Text Mini

Re: [julia-users] array with different column types

Actually I'm rather using the followig function allowing to remove several lines. function removeLines(poly::Poly, indices::BitArray{1}) for op = (:a, :b, :x1, :y1, :x2, :y2, :typ) @eval $poly.$op = ($poly.$op)[!$indices] end end function removeLines2(poly::Poly, indices::B

Re: [julia-users] array with different column types

The version without @eval is better. You shouldn't use @eval if you don't have to; it should be faster without it. -- Leah On Thu, May 8, 2014 at 2:42 PM, 'Stéphane Laurent' via julia-users < julia-users@googlegroups.com> wrote: > Actually I'm rather using the followig function allowing to remo

Re: [julia-users] Re: Optimal pmap usage

It indee broke stuff, but out of all my C calling, I've found the one that has the leak. The calls look like this: 1. Create a multidimensional array to store some doubles 2. Create a comprehension that has all the parameters to be executed in parallel 3. Recuperate them back through linear inde

Re: [julia-users] How can a remote proc self-discover DArray localparts?

Ah, okay. That reminds me, my neighbor keeps telling me about a family living in my coat closet, but when I look on my own I can never find them. 8-) On Thursday, May 8, 2014 5:18:38 AM UTC-4, Amit Murthy wrote: > > It can't. All part references are in the DArray object, `dz` in your > example

[julia-users] difference between inside and outside constructors

Would anyone explain the differences between the following two ways of defining a composite type? = type AA aa bb function AA() aa=1 bb=2 new(aa,bb) end end type BB aa bb end function BB() aa=1 bb=2 return BB(aa,bb) end

[julia-users] Re: require("file.py")

require("file.py") will try to load file.py as a Julia file, which is not what you want. You don't add files to paths, you add directories. For example, this will add a directory "/foo/bar" to the Python search path: unshift!(PyVector(pyimport("sys")["path"]), "/foo/bar") search path.

Re: [julia-users] Re: Static build

Thanks for the heads up and the link. I've tried to follow jeff's steps but got stuck fairly quickly - on the userimg.jl sysimg.jl files. What are the files he is refering to? Are they suupose to be part of julia source? kuba

Re: [julia-users] difference between inside and outside constructors

The main thing is that an inner constructor replaces the default constructor. AA(1,2) # this will work. BB(1,2) # this will throw an error You should also be able to see this in the output for "methods(AA)" and "methods(BB)". -- Leah On Thu, May 8, 2014 at 5:51 PM, cnbiz850 wrote: > Would

[julia-users] Re: Memory Bounded Algorithm for GLM

Did the requested functionality (Memory Bounded Algorithm for GLM, based on AS 274) ever get implemented? Or was the follow up discussion about QR factorization and committing code to "test/perf" about some other functionality? On Friday, July 12, 2013 10:45:14 AM UTC-7, Douglas Bates wrote: >

[julia-users] Re: duplicated inline plots in IJulia

Sure am. Started after a fresh git pull this morning. Haven't had a chance to look into it. Nat On Thursday, May 8, 2014 11:29:08 AM UTC-4, Joosep Pata wrote: > > Hi, > > Is anyone else seeing duplicated output from PyPlot in conjunction with > IJulia in inline mode recently? > > This does no

[julia-users] Re: Memory Bounded Algorithm for GLM

QR should be more stable numerically than Cholesky on the normal equations. You don't even have to keep Q around since it will typically be large and dense (the "Q-less" QR). I presume SuiteSparseQR could be useful here?! On Friday, July 12, 2013 10:45:14 AM UTC-7, Douglas Bates wrote: > > The g

[julia-users] Jacobi polynomials and Gauss-Jacobi quadrature related functions

Package Jacobi https://github.com/pjabardo/Jacobi.jl I have just written a package that implements Jacobi polynomials and related functions (derivatives of Jacobi polynomials and its zeros). This package also implements Gauss-Jacobi quadrature rules, computing nodes and weights for cases inclu

[julia-users] Least squares curve fitting package

Package CurveFit https://github.com/pjabardo/CurveFit.jl This package implements a few least squares fitting functions for some common cases (for me at least) . The only "different" aspect of this package is the nonlinear least squares fitting function. For now, I have only implemented the `fi

Re: [julia-users] Re: Static build

Put userimg.jl in base, and then build julia with make. --Tim On Thursday, May 08, 2014 03:57:45 PM Kuba Roth wrote: > Thanks for the heads up and the link. I've tried to follow jeff's steps but > got stuck fairly quickly - on the userimg.jl sysimg.jl files. What are the > files he is refering to

Re: [julia-users] Re: ANN: Coverage.jl - Code coverage tracking w/ coveralls.io

I've now "fixed" this by truncating the range of characters to ASCII - ugly, but it works. On Wednesday, May 7, 2014 2:16:06 PM UTC-4, Elliot Saba wrote: > > This looks like it might be a Requests.jl issue. Is there an easy way to > get the data that the Requests module is choking on? > -E > >

Re: [julia-users] Re: Memory Bounded Algorithm for GLM

Premature optimization, while being the root of all evil, is also a lot of fun! -viral On 12-Jul-2013 11:15 pm, "Douglas Bates" wrote: > The good news is that I did switch to the Cholesky decomposition for > solving the weighted least squares problem at each iteration of the IRLS > algorithm and

[julia-users] Re: [ANN] Orchestra: Heterogeneous Ensemble Learning Package

Glad to see you guys like it. :) You're right, at the moment you can't get predicted probabilities. It's something I'll be working on in the near future once I get a couple of other features out of the way (need feature selection + some variant of split-combine-apply transformer). In terms of

Re: [julia-users] [newb] array aliasing

Yes, it is well-defined. The right-hand side is returned, which might cause some confusion here. On Thu, May 8, 2014 at 10:10 AM, Neal Becker wrote: > Is the following well-defined in julia? > > julia> x = [1:10] > 10-element Array{Int64,1}: > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 >

Re: [julia-users] Re: Function roots() in package Polynomial

As the author of Polynomial.jl, I'll say that being "a bit unsatisfied" is a good reason to make pull requests for any and all improvements :) While loladiro is now the official maintainer of Polynomials.jl (since he volunteered to do the badly-needed work to switch the coefficient order), if I ha

[julia-users] Re: require("file.py")

Thanks Steven, That's a neat trick - I'll keep that in mind. However, this would require me to load PyCall in .juliarc.jl, which I in general do not want to do. Adding "mypath" to PYTHONPATH by ENV["PYTHONPATH"] = join([ENV["PYTHONPATH"],mypath]) in .juliarc.jl makes @pyimport look in "mypath

Re: [julia-users] Re: Function roots() in package Polynomial

Thanks a lot. Just a few minutes ago I saw here on the list an announcement of the "Least-squares curve fitting package" with poly_fit, among others. I think this is good enough for me at the moment. I will come back to your suggestion concerning polynomials when I have a better command of the typ