Tutorials

[Stuart Mumford]

Hi,

The other thing that the astropy repo does to manage the size of the
gh-pages branch is make it an orphan branch on every build, so there is no
history of the built notebooks only the empty ones.

Stuart


On 21 May 2014 10:23, Juan Nunez-Iglesias <jni.soma at gmail.com> wrote:

> Hi Stuart!
>
> This looks like a very good idea on first inspection — iirc git will not
> clone/fork a gh-pages branch by default, so having the run notebooks (with
> a lot of images built-in as Stéfan was concerned about) on that branch
> should not matter?
>
> I'm not sure I have time to get something like this working in time for
> SciPy... Perhaps I can use my own repo for drafting the tutorial, then move
> it into the tutorials repo as time allows?
>
>
> On Wed, May 21, 2014 at 7:06 PM, Stuart Mumford <stuart at mumford.me.uk>wrote:
>
>> Hi,
>>
>> Astropy have a interesting tutorials repo (
>> https://github.com/astropy/astropy-tutorials) we are planning on
>> implementing something similar using that for SunPy. There was some talk of
>> building this on a generic framework based on the Astropy repo, though I
>> don't think this has picked up much momentum.
>>
>> If you are interested in something like this as well then we all could
>> try and work together on a IPython notebook gallery / tutorials framework?
>>
>> Stuart
>>
>>
>> On 21 May 2014 08:14, Stéfan van der Walt <stefan at sun.ac.za> wrote:
>>
>>> Hey Juan
>>>
>>> On Wed, May 21, 2014 at 7:25 AM, Juan Nunez-Iglesias <jni.soma at gmail.com>
>>> wrote:
>>> > I'd like to have a repo for the tutorial Tony and I are doing at
>>> SciPy, and
>>> > all future scikit-image tutorials. I imagine it'll be a mix of
>>> markdown,
>>> > Python, and IPython notebooks. Do you think this is a good idea (say
>>> > github.com/scikit-image/skimage-tutorials), and if so, can you create
>>> it?
>>> > I'd suggest all core members should have write access to it.
>>>
>>> I think it's a great idea!
>>>
>>> https://github.com/scikit-image/skimage-tutorials
>>>
>>> With notebooks, I sometimes worry that the repository grows rapidly if
>>> you don't clear out the images before storing--what do you think is
>>> the best way to handle that?
>>>
>>> I could perhaps add a Travis config that runs all the notebooks (then
>>> one doesn't need to store the images because you are sure they can be
>>> generated). Also, another idea is to deploy to readthedocs upon merge.
>>>
>>> Thanks!
>>> Stéfan
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "scikit-image" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to scikit-image+unsubscribe at googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "scikit-image" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to scikit-image+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "scikit-image" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to scikit-image+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20140521/7b84309c/attachment.html>