title: python handles long ints differently on Windows and Unix
body: <p>The current number of milliseconds since the epoch is <code>1395245378429</code>; on unix (64 bit / Ubuntu / python 2.7), you can do:</p>
  
  <pre><code>&gt;&gt;&gt; t = 1395245378429
  &gt;&gt;&gt; type(t)
  &lt;type 'int'&gt;
  &gt;&gt;&gt; t = 1395245378429L
  &gt;&gt;&gt; type(t)
  &lt;type 'long'&gt;
  &gt;&gt;&gt; int(t)
  1395245378429
  &gt;&gt;&gt; type(int(t)
  &lt;type 'int'&gt;
  </code></pre>
  
  <p>but on Windows (also 64 bit / python 2.7), this happens:</p>
  
  <pre><code>&gt;&gt;&gt; t = 1395245378429
  &gt;&gt;&gt; type(t)
  &lt;type 'long'&gt;
  &gt;&gt;&gt; int(t)
  1395245378429L
  &gt;&gt;&gt; type(int(t))
  &lt;type 'long'&gt;
  </code></pre>
  
  <p>so, the following weird observations:</p>
  
  <ul>
  <li>on Windows, <code>int(&lt;long&gt;)</code> returns a long</li>
  <li>the same number is treated as a long in Windows, but an int on unix</li>
  </ul>
  
  <p>I can't see anything obvious in the documentation to say this is correct behaviour; is there a (correct) way to convert the long to an int (i.e. so it can be used in a method which requires an int argument)</p>