Re: [Spyce-users] macosx installation notes

[John M. <jm...@um...>]

Right. Now I got it. I completely jumped over the Apache config portion 
that was general to all installations and only did the part that was 
specific for fcgi installations. I guess I was in just a bit of a 
hurry. Anyway, I restored my system to the configuration suggested by 
the install instructions and everything is working peachy keen. Thanks 
for pointing out an obvious mistake. A few other comments below:

On Friday, November 8, 2002, at 06:32 PM, Rimon Barr wrote:

> Also thank you for reporting the installation problems on MacOS X. I'd
> have been surprised if it just worked, though it does not sound like 
> the
> problem are that serious. BTW, the installation is NOT dedicated for 
> the
> RPM's use. It is used by the RPM builder, but it can also be used for a
> manual installation.

I only thought so because of a comment in the makefile (line 102):
'''
# install Spyce (used by rpm scripts)
'''

> The install -D option forces install to create the directories that it
> needs. Got a better (read: more portable and just as simple) way to 
> ensure
> the parent of the installation destination exists?

Not me. Someone more knowledgeable about makefiles on bsd systems will 
have to chime in here...

> Regarding your comment about the template example not working. Well, 
> the
> Spyce part of it is work perfectly. It's actually not returning an 
> error,
> but trapping an error from the failure to find the Cheetah engine.
> Perhaps the output could look a little bit less like a failure. :) The
> problem is that the Cheetah engine is not installed. When the Cheetah
> engine is properly installed (see instructions in the template section 
> of
> the documentation), you'll see the filled-in template. I didn't have 
> the
> time to install this on SourceForge, but it does work; I've tested it.

Okay, Cheetah is now successfully installed on my system. I'm not sure 
yet if I'll use it, but I think it may come in handy, so I'm glad it's 
there. One comment about the Cheetah installation instructions that 
come with Spyce: there's a command issued in the site-packages 
directory (after running the install script) that says

chmod a+r -R Cheetah*

This did NOT work on my machine. After consulting the man page on 
chmod, it appeared as though the command had to be:

chmod -R a+r Cheetah*

This DID work. I don't know if this is system specific, or a typo in 
the docs...

> Lastly, regarding your comment about MySQL integration. I don't think
> there's much more to it than importing one of the Python MySQL 
> modules. I
> have never used MySQL under Python (preferring Postgres), so I can not
> recommend one module over any other. The following link may be of help:
>   http://www.python.org/topics/database/

Thanks for this suggestion, and those made by Adrien Plisson too. I've 
just recently come across a recent article on Python persistence 
management by Patrick O'Brien:

http://www-106.ibm.com/developerworks/library/l-pypers.html?n-1-1172

So, I'm thinking and rethinking about whether I want to focus on a 
relational database, like mySQL, or an object database, like ZODB, or 
maybe something else, like Gadfly. If there are any experiences in this 
group using any of these products with Spyce, I'd like to hear about 
them. (I know that's a very general request, and that the choice of 
data storage is highly application specific, nevertheless, I'm trying 
to glean/learn info from other people's prior experiences...)

John Miller
Technology Services
School of Education
University of Michigan