On Jul 23, 10:33 am, svilen <[EMAIL PROTECTED]> wrote:
> > First, I appended the sys.path var like this (relative, was
> > absolute before):
> > sys.path.append( 'vor')
>
> IMO u should not touch sys.path unless u really really have no other
> chance. Although this above is another whole
On Jul 23, 10:33 am, svilen <[EMAIL PROTECTED]> wrote:
> > First, I appended the sys.path var like this (relative, was
> > absolute before):
> > sys.path.append( 'vor')
>
> IMO u should not touch sys.path unless u really really have no other
> chance. Although this above is another whole
> -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 duplic
Ok, I just tried something that actually worked. WOO HOO!
First, I appended the sys.path var like this (relative, was absolute
before):
sys.path.append( 'vor')
combined with this:
...
module = my_import('vor.'+modname)
...
I realize that this is not ideal. But I'
> aaah, u are _that_ new...
> - use it instead of the __import__() func
> - original python library reference of the version u use;
> e.g.http://docs.python.org/lib/built-in-funcs.html
>
> wow there's a level parameter now... somethin to try
I'm not using 2.5 (2.4 still). I tried the 'my_import
which python reference (url?) are you speaking of?
how does 'import_fullname' work? how would it be applied?
On Jul 21, 11:35 am, [EMAIL PROTECTED] wrote:
> > In other words, should I first attempt to
> > __import__('vor.'+modname) in runJob() ?
>
> see the python reference about how to use __imp
On Jul 20, 10:42 pm, [EMAIL PROTECTED] wrote:
> this ain't SA issue, but if u want a solution, u have to provide more
> data, and do some prints here-there.
>
> > When a scheduled job is run, its specified module is loaded using
> > __import__ . This works fine unless the loaded module has an
>
I am creating a persistent job scheduler utility in my TG application
and have run into a minor issue regarding SqlAlchemy.
When a scheduled job is run, its specified module is loaded using
__import__ . This works fine unless the loaded module has an 'import
model' in it. If so, I get this:
Trace
