On Mon, Jul 19, 2010 at 1:10 AM, Daniel Herde <email address hidden> wrote:
> Hehe, glad you liked it.
>
> I'd go for importing scipy in the beginning. Problem is: This submodule
> doesn't automatically get imported when you import scipy. Therefore, I
> mentioned it separately.
>
> Otherwise, we could also go for an introductory story somewhere:
>
> In the beginning, there was the command line.
> And He typed "python", and there was python.
> There was still nothing, but from there,
> you could work a whole lot better.
>
> Cheers, Daniel.
>
>
> Frank Male wrote:
> > Review: Approve woot
> > Nice!
> > Should we assume that everyone does import scipy at the beginning, or
> import the individual modules we'll be using at each section?
>
> --
> https://code.launchpad.net/~dmh/scipyforscientists/rev0/+merge/30211<https://code.launchpad.net/%7Edmh/scipyforscientists/rev0/+merge/30211>
> You are reviewing the proposed merge of lp:~dmh/scipyforscientists/rev0
> into lp:scipyforscientists.
>
chapter opening quotes, oh my.
On Mon, Jul 19, 2010 at 1:10 AM, Daniel Herde <email address hidden> wrote:
> Hehe, glad you liked it. /code.launchpad .net/~dmh/ scipyforscienti sts/rev0/ +merge/ 30211<https:/ /code.launchpad .net/%7Edmh/ scipyforscienti sts/rev0/ +merge/ 30211>
>
> I'd go for importing scipy in the beginning. Problem is: This submodule
> doesn't automatically get imported when you import scipy. Therefore, I
> mentioned it separately.
>
> Otherwise, we could also go for an introductory story somewhere:
>
> In the beginning, there was the command line.
> And He typed "python", and there was python.
> There was still nothing, but from there,
> you could work a whole lot better.
>
> Cheers, Daniel.
>
>
> Frank Male wrote:
> > Review: Approve woot
> > Nice!
> > Should we assume that everyone does import scipy at the beginning, or
> import the individual modules we'll be using at each section?
>
> --
> https:/
> You are reviewing the proposed merge of lp:~dmh/scipyforscientists/rev0
> into lp:scipyforscientists.
>