Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

Jérémy Bobbio wrote: > > I deliberately used python3 to match the behaviour of what the > > /usr/bin/enjarify script does. > > Guess it's worth adding a comment about it for future readers. :) Excellent point; added in 53c649cef48de11e1584a09795ad890dcdb95eb4. Regards, -- ,''`. :

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

Chris Lamb: > Daniel Shahaf wrote: > > > > +if subprocess.call( > > > +('python3', '-c', 'import enjarify.typeinference'), > > > > Use sys.executable instead of hardcoding 'python3', to handle the case > > that there's more than one python3 binary on the system? > > I deliberately

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

Daniel Shahaf wrote: > > +if subprocess.call( > > +('python3', '-c', 'import enjarify.typeinference'), > > Use sys.executable instead of hardcoding 'python3', to handle the case > that there's more than one python3 binary on the system? I deliberately used python3 to match the

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

Chris Lamb wrote on Sat, Dec 24, 2016 at 18:57:38 +: > @@ -30,6 +31,17 @@ from test_java import javap_version > +def enjarify_version(): > +# Module enjarify.typeinference appeared in enjarify 1.0.3. We use a > call > +# directly to the python3 binary over importing with this module