On Apr 11, 2006, at 9:24 PM, Bob Ippolito wrote:
>
> On Apr 11, 2006, at 6:46 PM, William Kyngesburye wrote:
>
>> I just ran into an odd and annoying problem - I'm building a Python
>> library/extension thing for a package (MapServer) and have a library
>> weak-linked (it's to a non-open source p
One way to say what I'm thinking:There might be another way around this. It's another way of using two modules, which might not be desirable, but not quite the "two versions of the same thing, one with expanded functionality" type. Instead, it's "Two different (and more basic/plain-Jane) library
On Apr 11, 2006, at 6:46 PM, William Kyngesburye wrote:
> I just ran into an odd and annoying problem - I'm building a Python
> library/extension thing for a package (MapServer) and have a library
> weak-linked (it's to a non-open source product, this is so others
> don't have to install that if
I just ran into an odd and annoying problem - I'm building a Python
library/extension thing for a package (MapServer) and have a library
weak-linked (it's to a non-open source product, this is so others
don't have to install that if they don't need it and I don't have to
build multiple vers
