Message87498
With python, the first "import" of a library runs its initialization
code. Subsequent imports only retrieves the module object from the memory.
> for this library, it matter where you import the thing.
More precisely: it matters where you *first* import the thing. the
pyatspi import function probably runs some code that depends on the
running thread.
This is a common issue for event-driven libraries, often resolved by
splitting the initialization into two phases, the "import" phase and an
"init" function that performs thread-sensitive things.
You should forward your problem to the pyatspi team.
Since your first example works correctly, I close this issue as "works
for me". |
|
Date |
User |
Action |
Args |
2009-05-09 14:10:12 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, tyoc |
2009-05-09 14:10:12 | amaury.forgeotdarc | set | messageid: <1241878212.41.0.089163775566.issue5908@psf.upfronthosting.co.za> |
2009-05-09 14:10:11 | amaury.forgeotdarc | link | issue5908 messages |
2009-05-09 14:10:10 | amaury.forgeotdarc | create | |
|