[IPython-dev] git(hub) best practices

Jason Moore moorepants@gmail....
Fri Feb 28 09:42:43 CST 2014


One possibility is to not save the output of cells. I think there is an
option for that.


Jason
moorepants.info
+01 530-601-9791


On Fri, Feb 28, 2014 at 7:23 AM, Tiago Antao <tra@popgen.net> wrote:

> Dear all,
>
> First just a strong word of appreciation for all the work on ipython
> notebook. It is the best thing since sliced bread, and I am one of
> those people that spends most of his day working inside ipython
> notebook and that normally griefs for any period spent outside it. You
> did an amazing job!
>
> I am writing to inquire if there are any github best practices,
> especially with regards to notebook size.
>
> The issue is that in the typical work/commit/work/commit loop,
> notebook diffs tend to be quite large if one is using charts
> (matplotlib ones in my case). The Base64 encoding is quite big (as it
> would be expected of course).
>
> In the interests of reducing the load on github I oftentimes wonder if
> there is a more efficient way to maintain a tight work/commit cycle
> while not imposing so much disk usage on the host?
>
> Any ideas would be most welcome...
>
> Best,
> Tiago
> PS - Again, my sincere thanks for this wonderful tool...
> _______________________________________________
> IPython-dev mailing list
> IPython-dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/ipython-dev/attachments/20140228/8c1c64d5/attachment.html 


More information about the IPython-dev mailing list