On Mar 10, 9:33 pm, a...@pythoncraft.com (Aahz) wrote:
> In article
> <60848752-2c3f-4512-bf61-0bc11c919...@i20g2000prf.googlegroups.com>,
> Carl Banks wrote:
>
>
>
> >The problem comes when a different part of the upstream package also
> >subclasses or creates a Box. When an upstream function
In article <60848752-2c3f-4512-bf61-0bc11c919...@i20g2000prf.googlegroups.com>,
Carl Banks wrote:
>
>The problem comes when a different part of the upstream package also
>subclasses or creates a Box. When an upstream function creates a box,
>it creates an upstream.packaging.Box instead of a
>min
Ok, I think I know I want to do this, but I thought I'd run it by yins
guys
I have a fairly large and complex application with two top-level
packages, which we'll call upstream and mine. The "upstream" package
isn't really upstream. I own both packages, but I think of the
upstream package as a t
