Chuck Esterbrook <echuck@...> wrote:
> Uh, no. I'm pretty sure those are only in the main CVS branch. They came
> too late and were too big to make it into 0.5.1.
Okay, now I'm working with the CVS version.
Still get the problem.
Here's what sys.path looks like when it does the import:
'/usr/lib/python2.0', <a bunch of other system paths>,
To do the import I added a function to my SitePage:
if not hasattr(self, "_store"):
self._store = MySQLObjectStore(user='root', passwd='inter')
So I've given it the file:
But Sarah/MK hasn't been added to the path at all.
> >Where Poetry is used to identify the object. I think it's a nice URL
> >(nice URLs were something I really liked about Zope). I can't decide
> >whether I prefer /Book/Edit/Poetry, /BookEdit/Poetry/, or
> >/Book/Poetry/Edit... but I digress. Anyway, it doesn't make sense to
> >pluralize Book here, so I get a name conflict.
> Understood. BTW I like Book/Poetry/Edit. You might as well string the nouns
> together and typically most apps have you browse "objects" until you find
> what you want and then you apply an action to them. Like Word, Excel,
> Illustrator, etc.
Yes, I prefer this too -- it's more difficult, because then servlets
don't quite map by URL. But that's just an annoyance, not a serious
> What if you want to manipulate multiple items? That's what the GET args
> gives you:
I'd do Books/Preview?id=45&id=78&id=87 --
But, yes, that's a problem. The hierarchical URL simply can't
Could you use forwardRequest to call Preview over and over for each
ID? Either way you don't get repetition for free, and I don't think
it's a big burden to support URL and GET variables.
> Uh, yeah. initFromRow is a msg sent to descendants of MiddleObject. It's
> hitting the servlet first, creating it and then sending it that non-servlet
> message. Both servlets and middle objects can be created with no args to
> the constructor. I suspose it should check for issubclass(someClass,
> MiddleObject) first which would give a more meaningful error at an earlier
That would be helpful -- just an assert right after the import,
probably. The error message confused me a bit.