Merge lp://staging/~dmh/scipyforscientists/rev0 into lp://staging/scipyforscientists

Nice!
Should we assume that everyone does import scipy at the beginning, or import the individual modules we'll be using at each section?

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?

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.
>
> 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.
>

It's not an opening quote if you mix up three or more pop-culture
references ;)

Hope you had a good trip back to the US - have a good time until grad
school (aka as close to real work as it gets) starts.

Frank Male wrote:
> 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.
>>
>> 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.
>>
>

btw: could you change the ownership of the branch such that I can commit
directly?

It would save the merge request etc hassle.

Best wishes, Daniel.

Frank Male wrote:
> 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.
>>
>> 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.
>>
>

Ah, got it sorted out - it's possible to

     bzr push lp:~scipyforscientists/scipyforscientists/common

for every member of scipyforscientists. Can you just make this trunk?

Bazaar and Launchpad rock :D

Frank Male wrote:
> 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.
>>
>> 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.
>>
>

lp:scipyforscientists

is now owned by scipyforscientists.

Enjoy!

On Tue, Jul 20, 2010 at 2:49 AM, Daniel Herde <email address hidden> wrote:

> Ah, got it sorted out - it's possible to
>
> bzr push lp:~scipyforscientists/scipyforscientists/common
>
> for every member of scipyforscientists. Can you just make this trunk?
>
> Bazaar and Launchpad rock :D
>
>
> Frank Male wrote:
> > 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.
> >>
> >> 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>
> <https://code.launchpad.net/%7Edmh/scipyforscientists/rev0/+merge/30211>
> >> You are reviewing the proposed merge of lp:~dmh/scipyforscientists/rev0
> >> into lp:scipyforscientists.
> >>
> >
>
> --
> 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.
>