git(hub) best practices

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

git(hub) best practices

Tiago Antao
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
[hidden email]
http://mail.scipy.org/mailman/listinfo/ipython-dev
Reply | Threaded
Open this post in threaded view
|

Re: git(hub) best practices

Jason Moore
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 <[hidden email]> 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
[hidden email]
http://mail.scipy.org/mailman/listinfo/ipython-dev


_______________________________________________
IPython-dev mailing list
[hidden email]
http://mail.scipy.org/mailman/listinfo/ipython-dev
Reply | Threaded
Open this post in threaded view
|

Re: git(hub) best practices

Chris Friedline
I have a template that I use that might help you.  Check out:
https://github.com/cfriedline/ipynb_template

Chris

--
Christopher J. Friedline, Ph.D.
NSF Postdoctoral Research Fellow
Virginia Commonwealth University
Richmond, VA 23284
http://chris.friedline.net


Jason Moore wrote:

> One possibility is to not save the output of cells. I think there is an
> option for that.
>
>
> Jason
> moorepants.info <http://moorepants.info>
> +01 530-601-9791
>
>
> On Fri, Feb 28, 2014 at 7:23 AM, Tiago Antao <[hidden email]
> <mailto:[hidden email]>> 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
>     [hidden email] <mailto:[hidden email]>
>     http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
> _______________________________________________
> IPython-dev mailing list
> [hidden email]
> http://mail.scipy.org/mailman/listinfo/ipython-dev

_______________________________________________
IPython-dev mailing list
[hidden email]
http://mail.scipy.org/mailman/listinfo/ipython-dev

signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: git(hub) best practices

Phil Austin
This post has NOT been accepted by the mailing list yet.
> I have a template that I use that might help you.  Check out:
> https://github.com/cfriedline/ipynb_template

Very useful, thanks.   To those who want to have this filter run on ipynb files
in any repository, just copy .gitattributes to ~/.gitattributes and add the lines

[core]
     attributesfile= ~/.gitattributes

to our ~/.gitconfig

Reply | Threaded
Open this post in threaded view
|

Re: git(hub) best practices

Tiago Antao
In reply to this post by Chris Friedline
Hi,

[Apologies for the late answer]

On Fri, 28 Feb 2014 11:10:02 -0500
Chris Friedline <[hidden email]> wrote:

> I have a template that I use that might help you.  Check out:
> https://github.com/cfriedline/ipynb_template


This works very well, thank you.

It cannot be used for nbviewer, but it is quite easy to do a script to
copy things elsewhere and execute ipython notebook in batch (ipython -c
"%run notebook.ipynb") to render the notebooks for nbviewer.

Regards,
Tiago
_______________________________________________
IPython-dev mailing list
[hidden email]
http://mail.scipy.org/mailman/listinfo/ipython-dev