Titanium JIRA Archive
Alloy (ALOY)

[ALOY-249] Better error output on python < 2.7

GitHub Issuen/a
TypeBug
PriorityHigh
StatusResolved
ResolutionFixed
Resolution Date2012-09-12T07:27:03.000+0000
Affected Version/sn/a
Fix Version/s2012 Sprint 19, Release 3.0.0
ComponentsTitanium Studio
Labelsn/a
ReporterTony Lukasavage
AssigneeUnknown
Created2012-09-12T05:57:48.000+0000
Updated2018-03-07T22:26:12.000+0000

Description

Right now error output from the Titanium compiler plugin only lists the alloy error output if python 2.7+ is installed. Otherwise it defers to an older method of output that doesn't give all the information. We need someone with python chops to make a fix here so that we can get good error logs regardless of the version of python installed, so long as that version meets the minimum standards for Titanium, which I believe is 2.6+. Changes need to be made here: https://github.com/appcelerator/alloy/blob/master/Alloy/plugin/plugin.py From original ticket: The subprocess.check_output method is currently used by the ti.alloy compiler plugin to execute the appropriate commands and output error information, if necessary. While this works well and gives us good error logs, it only works for python 2.7+, where in its current state, Titanium supports 2.6+. There is a fallback function that is executed in case the developer does not have 2.7+ installed, subprocess.check_call. This method, unfortunately, does not give the full error log subprocess.check_output does. We need to implement a method in the ti.alloy compiler plugin that allows for solid error output on python 2.6+.

Comments

  1. Tony Lukasavage 2012-09-12

    Confirmed that the output is working for both errored and error-free use cases on both python 2.6 and 2.7

JSON Source