[Sikuli-driver] [Bug 1210474] Re: [1.0] Problems importing xml.dom.minidom in script running mode
** Changed in: sikuli Status: In Progress = Won't Fix ** Changed in: sikuli Importance: Medium = Undecided ** Changed in: sikuli Assignee: RaiMan (raimund-hocke) = (unassigned) ** Changed in: sikuli Milestone: 1.1.0 = None ** Description changed: --- problem a Sikuli script xml.sikuli found on sys.path hides the Python module + + users should obey the rule: + A Sikuli script, that can be found on sys.path at runtime, should not be named like a Python module, that is to be imported in the same script run. --- with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. ** Summary changed: - [1.0] Problems importing xml.dom.minidom in script running mode + [1.0] some_name.sikuli hides a Python module some_name at import and gives weird errors -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210474 Title: [1.0] some_name.sikuli hides a Python module some_name at import and gives weird errors Status in Sikuli: Won't Fix Bug description: --- problem a Sikuli script xml.sikuli found on sys.path hides the Python module users should obey the rule: A Sikuli script, that can be found on sys.path at runtime, should not be named like a Python module, that is to be imported in the same script run. --- with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210474/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1210474] Re: [1.0] Problems importing xml.dom.minidom in script running mode
Seems to be Jython problem, because it happens also, when using plain Jython to run a script containing this line. ** Changed in: sikuli Status: New = In Progress ** Changed in: sikuli Importance: Undecided = Medium ** Changed in: sikuli Assignee: (unassigned) = RaiMan (raimund-hocke) ** Changed in: sikuli Milestone: None = 1.1.0 -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210474 Title: [1.0] Problems importing xml.dom.minidom in script running mode Status in Sikuli: In Progress Bug description: with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210474/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1210474] Re: [1.0] Problems importing xml.dom.minidom in script running mode
I again checked the problem with any combination of Sikuli and Jython 2.5.3 and 2.5.4: I do not get the error anymore. The only situation: if a xml.sikuli can be found in sys.path (might be in the same directory or even the current script), the import fails. Sikuli's import support prioritizes .sikuli scripts when searching along the sys.path, so a Sikuli script should not be named as a Python module, when this Python module should be imported. Nevertheless I leave this a s bug, to check wether this can be avoided somehow. ** Description changed: + --- problem + a Sikuli script xml.sikuli found on sys.path hides the Python module + --- + with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module - from xml.dom import minidom + from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210474 Title: [1.0] Problems importing xml.dom.minidom in script running mode Status in Sikuli: In Progress Bug description: --- problem a Sikuli script xml.sikuli found on sys.path hides the Python module --- with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210474/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
