At 09:30 PM 6/5/2001 -0400, Jay Love wrote:
> > Chuck Esterbrook wrote:
> > >
> > > - Got rid of WebwarePathLocation usage. A script always knows where
> > > it's at with:
> > > os.path.dirname(os.path.join(os.getcwd(), sys.argv[0]))
> >
> > That might work. Good idea.
>
>Whoops, this'll need
At 08:56 PM 6/5/2001 -0400, Jay Love wrote:
>Chuck Esterbrook wrote:
>
>>I ran into a problem where an "import Foo" was picking up the Foo in
>>WebKit. Launch.py was previously tweaked to fix this but then got tweaked
>>back. However, we don't ever want "import Foo" to assume WebKit.
>
>Because
At 08:56 PM 6/5/2001 -0400, Jay Love wrote:
>Chuck Esterbrook wrote:
>
>>I ran into a problem where an "import Foo" was picking up the Foo in
>>WebKit. Launch.py was previously tweaked to fix this but then got tweaked
>>back. However, we don't ever want "import Foo" to assume WebKit.
>
>Because
> Chuck Esterbrook wrote:
> >
> > - Got rid of WebwarePathLocation usage. A script always knows where
> > it's at with:
> > os.path.dirname(os.path.join(os.getcwd(), sys.argv[0]))
>
> That might work. Good idea.
Whoops, this'll need some work. On Linux, sys.argv[0] will be different
depen
Chuck Esterbrook wrote:
> I ran into a problem where an "import Foo" was picking up the Foo in
> WebKit. Launch.py was previously tweaked to fix this but then got
> tweaked back. However, we don't ever want "import Foo" to assume WebKit.
Because WebKit is a package, any modules in the WebKit p
I ran into a problem where an "import Foo" was picking up the Foo in
WebKit. Launch.py was previously tweaked to fix this but then got tweaked
back. However, we don't ever want "import Foo" to assume WebKit.
I made the following changes:
- Incorporated Geoff's path cleaning code from Cookie.py
