- Need installation recommendation
Hi, Ok... Before getting into Zope+Gadfly, et al, I played around with installing Gadfly into the /usr/local/lib/python1.5 directory (since I didn't see any harm in having that there, from my perspective)... I see that gadfly is also installed in the Zope lib... I currently have the gadfly code in two places. Now that I'm ready to install the DCOracle stuff, etc... what is the best way to do that? Do you recommend having separate library areas for each thing (like gadfly, DCOracle, etc)? or just jam them all into the same lib? Is there anything about the DCOracle packaged in the Zope adapter that would prevent just using what is placed elsewhere (e.g. /usr/local/lib/python1.5 or subdir)? Now that I'm getting ready to start running a much more fully featured Python... I'm looking for "the voice of experience" in how to lay it out so that it can be managed. -- Cheers, --ldl ----------------------------------------------------------------------------- LD Landis ldl@HealthPartners.Com N0YRQ Voice 612/883-5511 Fax 612/883-6363 HealthPartners, 8100 34th Avenue So, PO Box 1309, Minneapolis, MN 55440-1309 Shape your life not from your memories, but from your hopes. (Borrowed) -----------------------------------------------------------------------------
Just as a data point, I have DCOracle installed in the site-packages directory, and the DA installed under zope. I think that's the best way to do it, as DCOracle is a general-purpose package that will allow you to talk to an Oracle db, while ZOracleDA is the zope-specific bit and needs to be in the Products area. (Same for ZMySQL, as I was already using MySQLmodule). Gadfly as far as I can tell is a _little_ bit different in terms of where it stores it's database (it's not referencing a third-party db), but I would imagine if the ZGadflyDA can do an 'import gadfly' successfully (ie, if gadfly is installed in your python site-specific area), it should work fine? Incidentally, kudos to the guys for DCOracle - I'm going to have to have more of a play with it, see how it stacks up to arb's Oracle module... KevinL (Oh, and if you 'install' DCOracle in the Products directory, you get a non-broken DCOracle product that offers no real Zope interface ;) Don't do that ;)
LD Landis wrote Hi,
Ok... Before getting into Zope+Gadfly, et al, I played around with installing Gadfly into the /usr/local/lib/python1.5 directory (since I didn't see any harm in having that there, from my perspective)...
I see that gadfly is also installed in the Zope lib... I currently have the gadfly code in two places.
Now that I'm ready to install the DCOracle stuff, etc... what is the best way to do that?
Do you recommend having separate library areas for each thing (like gadfly, DCOracle, etc)? or just jam them all into the same lib?
Is there anything about the DCOracle packaged in the Zope adapter that would prevent just using what is placed elsewhere (e.g. /usr/local/lib/python1.5 or subdir)?
Now that I'm getting ready to start running a much more fully featured Python... I'm looking for "the voice of experience" in how to lay it out so that it can be managed.
-- Cheers, --ldl ----------------------------------------------------------------------------- LD Landis ldl@HealthPartners.Com N0YRQ Voice 612/883-5511 Fax 612/883-6363 HealthPartners, 8100 34th Avenue So, PO Box 1309, Minneapolis, MN 55440-1309 Shape your life not from your memories, but from your hopes. (Borrowed) -----------------------------------------------------------------------------
--------------- qnevhf@obsu.arg.nh --------------- Kevin Littlejohn, Technical Architect, Connect.com.au Don't anthropomorphise computers - they hate that.
LD Landis wrote:
Hi,
Ok... Before getting into Zope+Gadfly, et al, I played around with installing Gadfly into the /usr/local/lib/python1.5 directory (since I didn't see any harm in having that there, from my perspective)...
I see that gadfly is also installed in the Zope lib... I currently have the gadfly code in two places.
Now that I'm ready to install the DCOracle stuff, etc... what is the best way to do that?
Do you recommend having separate library areas for each thing (like gadfly, DCOracle, etc)? or just jam them all into the same lib?
This depends alot on your environment and way of doing things. In many ways, I prefer wasting disk space and haveing various copies that are well integrated with applications. Others would reasoably prefer to have only one copy of any package. In other words, there isn't one right answer. Gadfly complicates this slightly because (at least in the last version I looked at): - It's not a package, - It want's a special install script to be run to tell it where certain files are and to cause these files to get created. We've hacked around these with our pre-packaged Gadfly. Maybe this wouldn't be an issue with the current version. (Yes, we do need to upgrade to the latest version. ...)
Is there anything about the DCOracle packaged in the Zope adapter that would prevent just using what is placed elsewhere (e.g. /usr/local/lib/python1.5 or subdir)?
No, as long as it is a top-level package. The Oracle DA imports DCOracle directly, so the package must be in either the DA package or in the Python path.
Now that I'm getting ready to start running a much more fully featured Python... I'm looking for "the voice of experience" in how to lay it out so that it can be managed.
I'm very "product" oriented. I want to distribute Zope products that are as self-contained as possible. This is good for people who want to use Zope and aren't heavy Python users. Python user's are more likely to want to extract parts, like DCOracle or Gadfly. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
participants (3)
-
Jim Fulton -
Kevin Littlejohn -
LD Landis