[TIMOB-11907] Studio: MobileWeb module Packaging Failed in Windows 8
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2012-12-03T14:49:57.000+0000 |
Affected Version/s | Release 3.0.0 |
Fix Version/s | n/a |
Components | Android, Tooling |
Labels | qe-mw100112 |
Reporter | Pragya Rastogi |
Assignee | Chris Barber |
Created | 2012-11-30T08:54:51.000+0000 |
Updated | 2014-07-17T09:47:36.000+0000 |
Description
Steps To Reproduce:
1. Complete Install Studio 3.0
2. Create Mobile Module.
3. Try packaging Mob Module using directory or SDK or project
Actual: Observe error in Console.
[Traceback (most recent call last):
File "C:\PragyaWrkspace\MobModule\build.py", line 18, in <module>
import markdown
File "C:\Users\Pragya.Rastogi\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20121128151109\common\markdown\__init__.py", line 173, in <module>
etree = etree_loader.importETree()
File "C:\Users\Pragya.Rastogi\AppData\Roaming\Titanium\mobilesdk\win32\3.0.0.v20121128151109\common\markdown\etree_loader.py", line 10, in importETree
import xml.etree.cElementTree as etree_in_c
File "C:\Program Files (x86)\Python-2.6.8\Lib\xml\etree\cElementTree.py", line 3, in <module>
from _elementtree import *
File "<string>", line 129, in <module>
AttributeError: 'module' object has no attribute 'fromstringlist']
Expected: Packaging must be successful.
@Pragya: What kind of module is it (android, ios, mobileweb?), and what happens when you update python to 2.7, the min supported version for the sdk?
Hi dustin, Its a mobile web module which i tried to package in a default project with all Android and MobileWeb deployment targets as enabled. Able to reproduce with new build : Titanium SDK:3.0.0.v20121130200208 Titanium Studio, build: 3.0.0.201211301903
@Pragya. What is the stack trace you get the second time?
Chris, assigning to you for feedback, though I can't reproduce it. Windows 8, Titanium Studio, build: 3.0.0.201211291910
Hey Pragya, please: -uninstall python -restart your machine -try to reproduce the bug -if you can reproduce, please include the stack trace. thanks!
Hi Thomas, After following above steps, the issue appear to be fixed on my machine. Thanks -Pragya
Marking as Cannot Reproduce since it's fixed on Pragya's machine.