[LNT] Python 3 support: use int() instead of long()

[thopre]

Summary

Use int() rather than long() to interpret a string as a long integer
since Python 3's integer are long by default. This was produced by
running futurize's stage2 lib2to3.fixes.fix_long.

[hubert.reinterpretcast]

lnt/tests/compile.py

532 ↗

(On Diff #220974)

Is this okay for 32-bit Python 2?

[thopre]

lnt/tests/compile.py

532 ↗

(On Diff #220974)

According to the Conservative Python 3 Porting Guide [1]:

In Python 2, calling int on a number that doesn’t fit in the machine int range would automatically create a long with the appropriate value.

[1] https://portingguide.readthedocs.io/en/latest/numbers.html

So yes this should be safe.

[hubert.reinterpretcast]

lnt/tests/compile.py

532 ↗

(On Diff #220974)

Thanks for checking. LGTM.

lnt/trunk/lnt/tests/compile.py

if binary_path is not None and codesize_util is not None:
             format_args = {"build_config": build_config}
             cmd = codesize_util + [os.path.join(build_base,
                                                 binary_path % format_args)]
             if opts.verbose:
                 g_log.info('running: %s' %
                            " ".join("'%s'" % arg for arg in cmd))
             result = subprocess.check_output(cmd).strip()
             if result != "fail":
-                bytes = long(result)
+                bytes = int(result)
                 success = True
 
                 # For now, the way the software is set up things are going to
                 # get confused if we don't report the same number of samples
                 # as reported for other variables. So we just report the size
                 # N times.
                 #
                 # FIXME: We should resolve this, eventually.