-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Raphael Bossek schrieb:
> Hi Torsten,
>
> thank a lot for your input.
>
> For all of them waiting for a bugfix should know that I'm working
> as mutch as I can to solve the problem. There are some Tracebacks
> while bdist_install the 4Suite package. Those Tracebacks do not
> stop the installation but are signals for a problem. I'm convinced
> to provide a final solution for this problem in the next few days.
> I've also deceeded to upgrade to a newer CVS snapshot.
>
Hi Raphael,
there are several occasions where mysterious exceptions are thrown, consinder
this one:
cd 4Suite && python2.2 setup.py bdist_install
-
--root="/home/shlomme/src/fremde/python-4suite-0.99cvs20041008/debian/python2.2-4suite"
Traceback (most recent call last):
File "/tmp/@14331.0.py", line 548, in ?
cmd.run()
File "build/lib.linux-i686-2.2/Ft/Lib/DistExt/BuildDocs.py", line 278, in run
self.doc_modules(index, top_level)
File "build/lib.linux-i686-2.2/Ft/Lib/DistExt/BuildDocs.py", line 390, in
doc_modules
module = self.locate(name)
File "build/lib.linux-i686-2.2/Ft/Lib/DistExt/BuildDocs.py", line 318, in
locate
module = self._builtin_import(path, {}, {}, '*')
File "build/lib.linux-i686-2.2/Ft/Server/Client/Commands/Rdf/__init__.py",
line 18, in ?
import Add, Complete, Remove, Versa
File "build/lib.linux-i686-2.2/Ft/Server/Client/Commands/Rdf/Complete.py",
line 23, in ?
from Ft.Server.Common import Util
File "build/lib.linux-i686-2.2/Ft/Server/Common/Util.py", line 78, in ?
PREFIXES = XPath.Compile("/fres:NsMappings/fres:NsMapping/Prefix/text()")
AttributeError: 'module' object has no attribute 'Compile'
In Ft.Xml.XPath.__init__, line 79:
try:
import XPathParserc
parser = XPathParserc
except ImportError:
import XPathParser
parser = XPathParser
fails because "import XPathParser" also throws an ImportError (just place a
catcher around it to try it out). Thus, it bails out and does not import Compile
from Util (which itself import this __init__. Did I mention that I consider
circular imports eeevil?), but is caught somewhere else and the code runs
happily, until it fails.
Next thing is
cd 4Suite && python2.4 setup.py build --with-docs
<snip>
Traceback (most recent call last):
File "/tmp/tmpKe4Mza.py", line 548, in ?
cmd.run()
File "build/lib.linux-i686-2.4/Ft/Lib/DistExt/BuildDocs.py", line 278, in run
self.doc_modules(index, top_level)
File "build/lib.linux-i686-2.4/Ft/Lib/DistExt/BuildDocs.py", line 390, in
doc_modules
module = self.locate(name)
File "build/lib.linux-i686-2.4/Ft/Lib/DistExt/BuildDocs.py", line 318, in
locate
module = self._builtin_import(path, {}, {}, '*')
File "build/lib.linux-i686-2.4/Ft/Xml/ThirdParty/Xvif/iframe.py", line 7, in ?
import rng
File "build/lib.linux-i686-2.4/Ft/Xml/ThirdParty/Xvif/rng.py", line 1376, in ?
class RngParser(ContentHandler, _Callback, _Pattern):
File "build/lib.linux-i686-2.4/Ft/Xml/ThirdParty/Xvif/rng.py", line 1379, in
RngParser
callbacks= \
AttributeError: 'module' object has no attribute 'Transform'
warning: build_docs: failure during documenting
There's something fishy going on with that _builtin_import (== __import__) call,
but anyway: iframe.py tries to run "from xml.dom.ext.reader.Sax2 import
XmlDomGenerator", which fails, since
/usr/lib/python2.4/site-packages/_xmlplus/dom/ext/reader/Sax2.py is in
python2.4-xml. As far as I have understood the debian/rules, it's the
2.4-generated docs which are finally copied over to the *-doc package, and they
are not build. This of course happens with the 2.3 build, too, but I happened to
have python2.3-xml installed, but not python2.4-xml. This saved my a lot of
nerves.
Hope I could be of help
greetings
Torsten
- --
Torsten Marek <[EMAIL PROTECTED]>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCVDFkfMVFHqJEyFgRAsW8AKCwPsJpnnJnD9xsiiVoHWVjk97NvgCgwML7
XOHrVH/r/5IIMiEAK6ZTF40=
=brod
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
