RE: PyDS 0.7.2 upgrade problems
"Bauer, Georg" <[email protected]> Fri, 14 May 2004 10:48:01 +0200
| Newsgroups | gmane.comp.pythin.pyds.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi! > I upgraded from 0.6.3 (Bob Ippolito's packaged version) to 0.7.2, > re-merged his patches, which was really quite simple, and was > surprised to find all my template changes weren't wiped out; I > expected I would have to redo them. Yay! Templates are copied on first access to your ~/.PyDS/templates directory. New installs only overwrite the base stuff that is copied, but not the copies themselves. > error: uncaptured python exception, closing channel > <medusa.http_server.http_channel connected 127.0.0.1:55418 at > 0x267fb70 channel#: 17 requests:1> (socket.error:(9, 'Bad > file descriptor') Hmm. Weird. That's stuff in asyncore - PyDS itself isn't even in the traceback here. What I do see is that you use Python 2.3. There are known problems with Python 2.3, PyDS is still only compatible with 2.2. So if you want to play on the safe side, you might want to follow the original source installation instructions, as those will install a local copy of Python 2.2 as a unix build under a prefix directory that doesn't conflict with the preinstalled python stuff and so will only use the tested tools. > Is this anything to be worried about? There might be something to worry about, but I can't really tell, as there isn't anything listed from the PyDS stuff in the traceback and so I don't know what part doesn't work. > 2. When using an editor to post via the MetaWeblog API, I cannot post > HTML, only plain text. I have the "Posting format to use as default" > set to "use HTML source code". The metaWeblogAPI recognizes what type to use for postings by looking at the first character. If it is a <, it assumes HTML source. Otherwise it assumes restructured Text. > 3. I needed to enable TopicExchange and Aggregator tools or I could > not upstream anything. I do not use these tools, so it would be nice > to be able to disable them. In the event log I saw: Just move them to a level above 1000 - that way they will still be enabled, but not show up in your menus. They can be disabled, but it might be that you need to restart your PyDS afterwards so that they aren't hooked into other tools any more. Especially the TopicExchange tool hooks into the WeblogTool. In your case the aggregator tool might have been disabled, but it still was actively running - it tried to render it's feed list. bye, Georg