In general I would think packages should be using `import` or `using` rather 
than `require`. That would fix your problem, I think.

--Tim

On Friday, November 07, 2014 09:32:33 AM [email protected] wrote:
> Ah yes, sorry but I am the same person who posted this issue ^ ^b
> 
> So far I have a dirty solution: add below code at the beginning of require
> function in load.jl and re-compile it:
> 
>     if ismatch(r"^\w+$",name) && isdefined(parse(name))
>         return nothing
>     end
> 
> Everything seems goes fine now... Hope it won't have any serious
> side-effect...
> I think as a Julia user, it is more valuable to make package-loading faster
> than make it always updated. The package loading time is a bottle-neck of
> improving user-experience right now. I quite support the precompile
> function.
> 
> On Friday, November 7, 2014 5:34:27 PM UTC+1, Ivar Nesje wrote:
> > https://github.com/lgautier/Rif.jl/issues/40 Seems relevant.
> > 
> > kl. 16:54:10 UTC+1 fredag 7. november 2014 skrev [email protected]
> > 
> > følgende:
> >> Actually it is not what I want, but require function is used in the code
> >> of other packages. I noted this problem when I failed to load Rif package
> >> after I precompiled Gadfly package. The Rif package can not be loaded
> >> since
> >> it "requires" DataFrames package, which is alreally precompiled along
> >> with
> >> Gadfly package. So, if require function just do nothing about any
> >> precompiled package, everything will be fine.
> >> 
> >> On Friday, November 7, 2014 4:33:22 PM UTC+1, Tim Holy wrote:
> >>> Out of curiosity, why do you want to do this? Once you've got the module
> >>> available, I would think you'd just refer to it by module name?
> >>> 
> >>> --Tim
> >>> 
> >>> On Friday, November 07, 2014 06:25:55 AM [email protected] wrote:
> >>> > Can you require a pre-compiled package in your Julia? If yes, could
> >>> 
> >>> you
> >>> 
> >>> > please tell me your version? Thanks!
> >>> > 
> >>> > On Friday, November 7, 2014 3:10:15 PM UTC+1, [email protected]
> >>> 
> >>> wrote:
> >>> > > After I precompiled a package in userimg.jl, require("Package_name")
> >>> 
> >>> is
> >>> 
> >>> > > always blocked without any response. But "using" and "import" the
> >>> 
> >>> package
> >>> 
> >>> > > works fine. That's weired.
> >>> > > 
> >>> > > If I interrupt require-ing package by Ctrl-C, the breaking point
> >>> 
> >>> always
> >>> 
> >>> > > be:
> >>> > > 
> >>> > > julia> require("DataFrames")
> >>> > > ^CERROR: interrupt
> >>> > > 
> >>> > >  in wait at ./task.jl:277
> >>> > >  in wait at ./task.jl:194
> >>> > >  in wait_full at ./multi.jl:602
> >>> > >  in wait_ref at ./multi.jl:755
> >>> > >  in wait_ref_3B_7574 at
> >>> > > 
> >>> > > /home/MyDir/programs/julia/usr/bin/../lib/julia/sys.so
> >>> > > 
> >>> > >  in call_on_owner at ./multi.jl:749
> >>> > >  in wait at ./multi.jl:756
> >>> > >  in _require at ./loading.jl:62
> >>> > >  in require at ./loading.jl:52
> >>> > >  in require_3B_7273 at
> >>> > > 
> >>> > > /home/MyDir/programs/julia/usr/bin/../lib/julia/sys.so
> >>> > > 
> >>> > > FYI:
> >>> > > julia> versioninfo()
> >>> > > Julia Version 0.4.0-dev+728
> >>> > > Commit f7172d3* (2014-09-22 12:08 UTC)
> >>> > > 
> >>> > > Platform Info:
> >>> > >   System: Linux (x86_64-redhat-linux)
> >>> > >   CPU: Intel(R) Xeon(R) CPU E7- 4830  @ 2.13GHz
> >>> > >   WORD_SIZE: 64
> >>> > >   BLAS: libopenblas (USE64BITINT NO_AFFINITY NEHALEM)
> >>> > >   LAPACK: libopenblas
> >>> > >   LIBM: libopenlibm
> >>> > >   LLVM: libLLVM-3.3

Reply via email to