What I meant to ask is whether Julia code written with a pycall dependency 
could at some point be compiled and distributed self contained. 

But point taken, thanks.  

On Tuesday, October 28, 2014 8:46:39 PM UTC-4, John Myles White wrote:
>
> I think if you're hoping to read a tutorial, then Julia is not the right 
> language for you until it hits 1.0. At the moment, the one true Julia 
> tutorial is reading the Julia source code.
>
> I wouldn't worry about the concept of an "exe".
>
>  -- John
>
> On Oct 28, 2014, at 5:42 PM, [email protected] <javascript:> wrote:
>
> Thanks very much.
>
> Would it be conceivably possible  at some point  to include python 
> functions called from pycall, in a future julia exe?
>
> I already have a decent grasp of python, but trying to decide if its worth 
> learning the syntax of the entire scipy system if I will be switching to 
> julia later.
>
> The lack   of tutorials for data science in julia is the main factor I'm 
> pondering now. 
>
> On Saturday, October 25, 2014 11:13:43 AM UTC-4, John Myles White wrote:
>>
>> I’m very conservative about recommeinding Julia these days. I’d say that, 
>> as a beginner to programming, you may find Julia to be a difficult ride. I 
>> think you’ll find Julia quite easy to learn after you’ve already mastered 
>> Python. 
>>
>>  — John 
>>
>> On Oct 24, 2014, at 9:41 AM, [email protected] wrote: 
>>
>> > Hi Everyone, 
>> > 
>> > I'v posted the below questions on reddit julia , and wanted to elicit 
>> additional input from the group. I'm trying to figure out which system 
>> (python vs julia) to invest in, Any feedback would be appreciated. 
>> > 
>> > 
>> http://www.reddit.com/r/Julia/comments/2k4dtm/experience_with_pycall_in_action/
>>  
>> - How robust is pycall? Can I rely on it to do database connections and 
>> beautiful soup scraping? 
>> > 
>> > 
>> http://www.reddit.com/r/Julia/comments/2k79mn/is_there_something_about_julia_that_facilitates/
>>  
>> - julia vs python types for simulations. Using julia types in simulations. 
>> > 
>> > Thanks! 
>>
>>
>

Reply via email to