Add failing tests for the cause of issue #119

It seems that sys.exit(newint) (and other longs) always returns 1!

Author: edschofield

tests/test_future/test_futurize.py

@@ -17,6 +17,18 @@
 
 
 class TestLibFuturize(unittest.TestCase):
+    def test_correct_exit_status(self):
+        """
+        Issue #119: futurize and pasteurize were not exiting with the correct
+        status code. This is because the status code returned from
+        libfuturize.main.main() etc. was a ``newint``, which sys.exit() always
+        translates into 1!
+        """
+        from libfuturize.main import main
+        # Try futurizing this test script:
+        retcode = main([__file__])
+        self.assertTrue(isinstance(retcode, int))   # i.e. Py2 builtin int
+
     def test_is_shebang_comment(self):
         """
         Tests whether the fixer_util.is_encoding_comment() function is working.

tests/test_future/test_pasteurize.py

@@ -129,6 +129,18 @@ def test_urllib_refactor2(self):
         filename = urllib_parse.urlparse(url)[2].split('/')[-1]
         """
 
+    def test_correct_exit_status(self):
+        """
+        Issue #119: futurize and pasteurize were not exiting with the correct
+        status code. This is because the status code returned from
+        libfuturize.main.main() etc. was a ``newint``, which sys.exit() always
+        translates into 1!
+        """
+        from libpasteurize.main import main
+        # Try pasteurizing this test script:
+        retcode = main([__file__])
+        self.assertTrue(isinstance(retcode, int))   # i.e. Py2 builtin int
+
 
 class TestFuturizeAnnotations(CodeHandler):
     @unittest.expectedFailure