> -3: 2.5 or 2.4 all the same (Except abs/rel imports which still dont > work in 2.5 anyway). > -2: u need my_import (or similar) because __import__( 'vor.model') > will not give u want u want. > -1: u need to give _same_ full absolute paths to __import__ (or > substitute) or else u'll get duplicated modules. OR, do check how the > model.py is imported in the application, and __import__ it the same > way. same to for anything u want to import, _again, _later. > this should bring u to square next. > > 0: i havent asked why the heck u need to __import__ - multiple times - > but this is out of my MYOB.
-3: didn't know that. thanks. -2: yes, I now understand this...thanks again. -1: I think the reason for the original symptoms WAS that model import was relative, as is everything else in TG. 0: actually, I don't really need to be able to import anything multiple times DIRECTLY, but, in many cases, the job that needs to be run later (scheduled) will have model.py statically imported. (via 'import model'). It will need model for its ORM class. But, as we have seen, model will need to be imported relative. 1: At least I'm in a working context...since I will be the user of this jobs module 90% of the time for a while, I'll have a fighting chance of refining it further to handle the other things you allude to. thanks again for your help. sincerely, JJ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
