Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

d3.js in IPython 2.0.ipynb

JeffBezanson

(quail-define-package
 "symbol-input" "unicode" "unicode-sym" t
 "Easier input for unicode technical symbols"
 nil t nil nil nil nil nil nil nil nil t)

(quail-define-rules
    ("\\alpha"   ?α)
    ("\\beta"    ?β)
    ("\\gamma"   ?γ)
    ("\\delta"   ?δ)

MikeInnes

# Repeat an operation n times, e.g.
# @dotimes 100 println("hi")

macro dotimes(n, body)
  quote
    for i = 1:$(esc(n))
      $(esc(body))
    end
  end
end

alsam

# Fortran-like array with arbitrary starting indices
#
# usage:
#
# julia> include("FArray.jl")
# size (generic function with 51 methods)
# 
# julia> y = FArray(Float64, -1:1, -7:7, -128:512, -5:5, -1:1, -3:3, -2:2, -1:1);
# 
# julia> y[-1,-7,-128,-5,-1,-3,-2,-1] = 14

svaksha

Julia Debugging Procedures

So you managed to break Julia. Congratulations! Collected here are some general procedures you can undergo for common symptoms encountered when something goes awry. Including the information from these debugging steps can greatly help the maintainers when tracking down a segfault or trying to figure out why your script is running slower than expected.

If you've been directed to this page, find the symptom that best matches what you're experiencing and follow the instructions to generate the debugging information requested. Table of symptoms:

• Segfaults during bootstrap (sysimg.jl)

• Segfaults when running a script

jiahao

/* Experimental typographically tinkered IJulia stylesheet
 * Copyright © 2013 Jiahao Chen <jiahao@mit.edu>
 * MIT License
 *
 * To use, place in ~/.ipython/profile_julia/static/custom/custom.css
 * and refresh IJulia
 * 
 * Based on suggestions from practicaltypography.com
 */

welch

It is a rite of passage to post one's successful build instructions for OpenCV on a Mac
after you've tried all the other conflicting instructions out there and still failed. 
brew failed for me (was this because I could never get a happy brew doctor situation? 
I'll never know). macports? nope. build-from-source recipes? I didn't find one that 
worked for me.

Here's what did work to build OpenCV 2.4.5 from the distribution tarball using cmake,
on Mac OSX 10.8.4, linked to an anaconda installation rather than the system python. 
It is a mashup of various bits of advice out there. If you're already comfortable with 
build/install from source, all you need to read is the cmake invocation in step 3 and 

randyzwitch

#Python/pypy
import math
def smallestdivisall(n):
    for i in xrange(1, math.factorial(n)+1):
        for j in xrange(1, n+1):
            if i % j != 0:
                break
            elif j == n:
                return i
                

staticfloat

Julia Debugging Procedures

So you managed to break Julia. Congratulations! Collected here are some general procedures you can undergo for common symptoms encountered when something goes awry. Including the information from these debugging steps can greatly help the maintainers when tracking down a segfault or trying to figure out why your script is running slower than expected.

If you've been directed to this page, find the symptom that best matches what you're experiencing and follow the instructions to generate the debugging information requested. Table of symptoms:

• Segfaults during bootstrap (sysimg.jl)

• Segfaults when running a script