On 6/22/06, Lawrence D'Oliveiro <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> "Martin Blais" <[EMAIL PROTECTED]> wrote:
>
> >On 18 Jun 2006 05:25:14 -0700, John Roth <[EMAIL PROTECTED]> wrote:
> >
> >> The general rule is: don't do that. It doesn't work, and the
> >> hoops you hav
In article <[EMAIL PROTECTED]>,
"Martin Blais" <[EMAIL PROTECTED]> wrote:
>On 18 Jun 2006 05:25:14 -0700, John Roth <[EMAIL PROTECTED]> wrote:
>
>> The general rule is: don't do that. It doesn't work, and the
>> hoops you have to go through to force it to work are so
>> complex and bizzare that t
On 18 Jun 2006 05:25:14 -0700, John Roth <[EMAIL PROTECTED]> wrote:
> Martin Blais wrote:
> > Hi
> >
> > I'm a tad confused over a problem involving cycles between
> > packages.
>
> [lengthy example snipped]
>
> >
> >
> > I don't see why the reference to module a.alice could not be
> > available v
Martin Blais wrote:
> Hi
>
> I'm a tad confused over a problem involving cycles between
> packages.
[lengthy example snipped]
>
>
> I don't see why the reference to module a.alice could not be
> available via the "from" syntax, even if it is still incompletely
> initialized at the time of import
Hi
I'm a tad confused over a problem involving cycles between
packages.
Assume the following sets of files::
driver.py
a/__init__.py
a/alice.py
b/__init__.py
b/bob.py
Basically, two packages a and b. Driver simply imports one of the
two. This is the file that gets run::
, (driv