From tpherndon at gmail.com Sat Apr 1 01:38:26 2006 From: tpherndon at gmail.com (Peter Herndon) Date: Fri, 31 Mar 2006 18:38:26 -0500 Subject: [XML-SIG] XML from scratch and transformation with XSLT In-Reply-To: <442D8731.5010808@gmail.com> References: <442D8731.5010808@gmail.com> Message-ID: <50120A7D-B217-4502-8C0B-995BA3F3D679@gmail.com> On Mar 31, 2006, at 2:46 PM, Marc Garcia wrote: > I want to make a simple program in python that get data from a > database > (or other source), create a new xml document with it and then parse it > with an existing xslt sheet. > Why would you do this? That is, you are pulling data from a database into Python, then transforming it into XML, then running that XML through an XSLT transformation. Why not pull the data into Python, manipulate them in Python, then output as the end-result XML? That is, transcribe from Python directly to the desired final XML format? I can think of a couple of reasons to do it your way -- the XSLT engine might well be faster than the Python transformation, it might be easier to output simple XML and then expand it via XSLT, etc. -- but I'm wondering if you've considered the above simpler path? It might make your life easier. > Do somebody know what is the simplest way to achieve it? I'm having > some > problems with all of it (encoding problems, installation bugs, more > than > one library required...) and I need some expert tips to know what > way I > have to work on. > I'm hardly an expert, and your email doesn't present enough data to make any specific recommendations, but I'd suggest using (c) ElementTree as your XML library, if it meets your requirements. You could pull the data in, do your manipulations in Python, then create your XML using ElementTree. And it will solve your installation issues if you can afford to wait long enough -- it will be in the standard library for Python 2.5. Otherwise, ElementTree itself is pure Python, and is thus easily installed, though there is an optional C extension (cElementTree) that will improve performance. ---Peter From mgarcia at accopensys.com Sun Apr 2 01:11:37 2006 From: mgarcia at accopensys.com (Marc Garcia) Date: Sun, 02 Apr 2006 01:11:37 +0200 Subject: [XML-SIG] XML from scratch and transformation with XSLT In-Reply-To: <50120A7D-B217-4502-8C0B-995BA3F3D679@gmail.com> References: <442D8731.5010808@gmail.com> <50120A7D-B217-4502-8C0B-995BA3F3D679@gmail.com> Message-ID: <442F08A9.2020302@accopensys.com> Thanks for your opinion Peter, it have been useful to me. I'm used to do transformations directly when I get data from database, but I think that this new way make applications easier to maintain, the code is logically divided, and the this is more clear. The ElementTree is good, and for me the best would be use the lxml implementation so it have xslt support, but it isn't a rpm package and is difficult for me install it in my fedora server without development environment. Finally I did it with libxml2/libxslt, after solving some encoding problems. Probably I'll develop my own class, to abstract it, and to make it easy if in the future I want to change this library. Thanks, Marc Peter Herndon wrote: > On Mar 31, 2006, at 2:46 PM, Marc Garcia wrote: > >> I want to make a simple program in python that get data from a database >> (or other source), create a new xml document with it and then parse it >> with an existing xslt sheet. >> > > Why would you do this? That is, you are pulling data from a database > into Python, then transforming it into XML, then running that XML > through an XSLT transformation. Why not pull the data into Python, > manipulate them in Python, then output as the end-result XML? That > is, transcribe from Python directly to the desired final XML format? > > I can think of a couple of reasons to do it your way -- the XSLT > engine might well be faster than the Python transformation, it might > be easier to output simple XML and then expand it via XSLT, etc. -- > but I'm wondering if you've considered the above simpler path? It > might make your life easier. > >> Do somebody know what is the simplest way to achieve it? I'm having >> some >> problems with all of it (encoding problems, installation bugs, more >> than >> one library required...) and I need some expert tips to know what way I >> have to work on. >> > > I'm hardly an expert, and your email doesn't present enough data to > make any specific recommendations, but I'd suggest using (c) > ElementTree as your XML library, if it meets your requirements. You > could pull the data in, do your manipulations in Python, then create > your XML using ElementTree. And it will solve your installation > issues if you can afford to wait long enough -- it will be in the > standard library for Python 2.5. Otherwise, ElementTree itself is > pure Python, and is thus easily installed, though there is an > optional C extension (cElementTree) that will improve performance. > > ---Peter > From toddobryan at mac.com Tue Apr 4 18:28:08 2006 From: toddobryan at mac.com (Todd O'Bryan) Date: Tue, 4 Apr 2006 12:28:08 -0400 Subject: [XML-SIG] PyXML install problems on Mac OS X Message-ID: <87D2A5A0-3709-431F-93E3-044FF1CE32F8@mac.com> I hope this is the right place to ask about this... I have Mac OS X, 10.4.6 (updated this morning) with the new Python 2.4.3 Universal Binary just released at python.org. I'm trying to install PyXML, but having problems. It appears that, for some reason, gcc is not looking in /usr/include for header files. I've tried looking through setup.py to see what was going on, but I'm a Python newbie and just got lost in the code. For reference, /usr/include/limits.h does exist, and which gcc produces /usr/bin/gcc which is a link to /usr/bin/gcc-4.0 which seems to be the binary. Any ideas? Output of python setup.py build is given below. Thanks, Todd running build running build_py running build_ext building '_xmlplus.parsers.pyexpat' extension gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd - fno-common -dynamic -DNDEBUG -g -DXML_NS=1 -DXML_DTD=1 - DBYTEORDER=4321 -DXML_CONTEXT_BYTES=1024 -DHAVE_MEMMOVE=1 - Iextensions/expat/lib -I/Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4 -c extensions/pyexpat.c -o build/ temp.macosx-10.4-fat-2.4/extensions/pyexpat.o gcc: installation problem, cannot exec 'i686-apple-darwin8- gcc-4.0.0': No such file or directory In file included from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:18:20: error: limits.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:21:2: error: #error "Something's broken. UCHAR_MAX should be defined in limits.h." /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:25:2: error: #error "Python's source code assumes C's unsigned char is an 8-bit type." /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:32:19: error: stdio.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:34:5: error: #error "Python.h requires that stdio.h define NULL." /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:37:20: error: string.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:38:19: error: errno.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:39:20: error: stdlib.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:41:20: error: unistd.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:53:20: error: assert.h: No such file or directory In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:55, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:90:76: error: math.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:97:22: error: sys/time.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:98:18: error: time.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:116:24: error: sys/select.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:155:22: error: sys/stat.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:395:21: error: termios.h: No such file or directory In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:55, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:396: warning: 'struct winsize' declared inside parameter list /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:396: warning: its scope is only this definition or declaration, which is probably not what you want /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:396: warning: 'struct termios' declared inside parameter list /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:397: warning: 'struct winsize' declared inside parameter list /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyport.h:397: warning: 'struct termios' declared inside parameter list In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:74, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pymem.h:50: warning: parameter names (without types) in function declaration /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pymem.h:51: error: parse error before "size_t" In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:76, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ object.h:227: error: parse error before "FILE" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ object.h:371: error: parse error before "FILE" In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:77, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ objimpl.h:97: warning: parameter names (without types) in function declaration /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ objimpl.h:98: error: parse error before "size_t" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ objimpl.h:292: warning: parameter names (without types) in function declaration In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:81, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ unicodeobject.h:55:19: error: ctype.h: No such file or directory /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ unicodeobject.h:118:21: error: wchar.h: No such file or directory In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:81, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ unicodeobject.h:511: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ unicodeobject.h:529: error: parse error before '*' token In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:84, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ longobject.h:63: error: parse error before "_PyLong_NumBits" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ longobject.h:63: warning: data definition has no type or storage class /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ longobject.h:79: error: parse error before "size_t" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ longobject.h:102: error: parse error before "size_t" In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:90, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ stringobject.h:10:20: error: stdarg.h: No such file or directory In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:90, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ stringobject.h:63: error: parse error before "va_list" In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:101, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:12: error: parse error before "FILE" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:12: warning: no semicolon at end of struct or union /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:15: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:28: error: parse error before '}' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:28: warning: data definition has no type or storage class /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:38: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:39: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:40: warning: data definition has no type or storage class /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:57: error: parse error before "FILE" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:58: error: parse error before "Py_UniversalNewlineFread" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:58: error: parse error before "size_t" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ fileobject.h:58: warning: data definition has no type or storage class In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:112, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyerrors.h:226: error: parse error before "size_t" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pyerrors.h:228: error: parse error before "size_t" In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:116, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ modsupport.h:20: error: parse error before "va_list" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ modsupport.h:22: error: parse error before "va_list" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ modsupport.h:23: error: parse error before "va_list" In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:117, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:32: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:33: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:35: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:36: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:40: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:41: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:42: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:43: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:44: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:45: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:46: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:49: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:55: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:59: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:60: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:64: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:66: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:82: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:123: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ pythonrun.h:125: error: parse error before '*' token In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:119, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ sysmodule.h:12: error: parse error before '*' token /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ sysmodule.h:12: error: parse error before "FILE" /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ sysmodule.h:12: warning: data definition has no type or storage class In file included from /Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4/Python.h:121, from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ import.h:25: error: parse error before "size_t" In file included from extensions/pyexpat.c:5: /Library/Frameworks/Python.framework/Versions/2.4/include/python2.4/ Python.h:131: error: parse error before "size_t" In file included from extensions/pyexpat.c:10: extensions/expat/lib/expat.h:189: error: parse error before "size" extensions/expat/lib/expat.h:190: error: parse error before "size_t" extensions/expat/lib/expat.h:936: error: parse error before "size_t" extensions/expat/lib/expat.h:939: error: parse error before "size_t" extensions/pyexpat.c: In function 'set_error_attr': extensions/pyexpat.c:112: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c:112: error: (Each undeclared identifier is reported only once extensions/pyexpat.c:112: error: for each function it appears in.) extensions/pyexpat.c: In function 'set_error': extensions/pyexpat.c:134: warning: incompatible implicit declaration of built-in function 'sprintf' extensions/pyexpat.c:138: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'have_handler': extensions/pyexpat.c:151: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'get_handler_name': extensions/pyexpat.c:158: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'conv_string_to_unicode': extensions/pyexpat.c:177: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c:181: warning: incompatible implicit declaration of built-in function 'strlen' extensions/pyexpat.c: In function 'conv_string_len_to_unicode': extensions/pyexpat.c:190: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'conv_string_to_utf8': extensions/pyexpat.c:207: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'conv_string_len_to_utf8': extensions/pyexpat.c:220: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'getcode': extensions/pyexpat.c:255: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'trace_frame': extensions/pyexpat.c:310: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'trace_frame_exc': extensions/pyexpat.c:337: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'call_with_frame': extensions/pyexpat.c:375: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'string_intern': extensions/pyexpat.c:431: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'call_character_handler': extensions/pyexpat.c:448: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'flush_character_buffer': extensions/pyexpat.c:482: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_CharacterDataHandler': extensions/pyexpat.c:493: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c:510: warning: incompatible implicit declaration of built-in function 'memcpy' extensions/pyexpat.c: In function 'my_StartElementHandler': extensions/pyexpat.c:537: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_EndElementHandler': extensions/pyexpat.c:636: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_ProcessingInstructionHandler': extensions/pyexpat.c:640: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_UnparsedEntityDeclHandler': extensions/pyexpat.c:646: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_EntityDeclHandler': extensions/pyexpat.c:676: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_XmlDeclHandler': extensions/pyexpat.c:696: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'conv_content_model': extensions/pyexpat.c:709: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_ElementDeclHandler': extensions/pyexpat.c:737: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_AttlistDeclHandler': extensions/pyexpat.c:785: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_SkippedEntityHandler': extensions/pyexpat.c:798: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_NotationDeclHandler': extensions/pyexpat.c:806: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_StartNamespaceDeclHandler': extensions/pyexpat.c:816: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_EndNamespaceDeclHandler': extensions/pyexpat.c:823: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_CommentHandler': extensions/pyexpat.c:828: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_StartCdataSectionHandler': extensions/pyexpat.c:832: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_EndCdataSectionHandler': extensions/pyexpat.c:836: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_DefaultHandler': extensions/pyexpat.c:849: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_DefaultHandlerExpandHandler': extensions/pyexpat.c:855: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_NotStandaloneHandler': extensions/pyexpat.c:862: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_ExternalEntityRefHandler': extensions/pyexpat.c:866: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_StartDoctypeDeclHandler': extensions/pyexpat.c:881: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'my_EndDoctypeDeclHandler': extensions/pyexpat.c:889: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'get_parse_result': extensions/pyexpat.c:897: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'xmlparse_Parse': extensions/pyexpat.c:920: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'readinst': extensions/pyexpat.c:932: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c:970: warning: incompatible implicit declaration of built-in function 'memcpy' extensions/pyexpat.c: In function 'xmlparse_ParseFile': extensions/pyexpat.c:986: error: 'FILE' undeclared (first use in this function) extensions/pyexpat.c:986: error: 'fp' undeclared (first use in this function) extensions/pyexpat.c:987: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'xmlparse_SetBase': extensions/pyexpat.c:1050: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'xmlparse_GetBase': extensions/pyexpat.c:1066: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'xmlparse_GetInputContext': extensions/pyexpat.c:1080: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'xmlparse_ExternalEntityParserCreate': extensions/pyexpat.c:1112: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c:1134: warning: incompatible implicit declaration of built-in function 'malloc' extensions/pyexpat.c:1175: warning: incompatible implicit declaration of built-in function 'malloc' extensions/pyexpat.c: In function 'xmlparse_SetParamEntityParsing': extensions/pyexpat.c:1208: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: In function 'xmlparse_UseForeignDTD': extensions/pyexpat.c:1226: error: 'NULL' undeclared (first use in this function) extensions/pyexpat.c: At top level: extensions/pyexpat.c:1261: error: 'NULL' undeclared here (not in a function) extensions/pyexpat.c:1261: error: initializer element is not constant extensions/pyexpat.c:1261: error: (near initialization for 'xmlparse_methods[8].ml_name') extensions/pyexpat.c:1261: error: initializer element is not constant extensions/pyexpat.c:1261: error: (near initialization for 'xmlparse_methods[8].ml_meth') extensions/pyexpat.c:1261: error: initializer element is not constant extensions/pyexpat.c:1261: error: (near initialization for 'xmlparse_methods[8]') extensions/pyexpat.c: In function 'newxmlparseobject': extensions/pyexpat.c:1377: warning: incompatible implicit declaration of built-in function 'malloc' extensions/pyexpat.c: In function 'xmlparse_setattr': extensions/pyexpat.c:1581: warning: incompatible implicit declaration of built-in function 'malloc' extensions/pyexpat.c: At top level: extensions/pyexpat.c:1677: error: initializer element is not constant extensions/pyexpat.c:1677: error: (near initialization for 'Xmlparsetype.ob_type') extensions/pyexpat.c: In function 'pyexpat_ParserCreate': extensions/pyexpat.c:1728: error: initializer element is not constant extensions/pyexpat.c:1728: error: (near initialization for 'kwlist[3]') extensions/pyexpat.c:1734: warning: incompatible implicit declaration of built-in function 'strlen' extensions/pyexpat.c: At top level: extensions/pyexpat.c:1784: error: initializer element is not constant extensions/pyexpat.c:1784: error: (near initialization for 'pyexpat_methods[2].ml_name') extensions/pyexpat.c:1784: error: initializer element is not constant extensions/pyexpat.c:1784: error: (near initialization for 'pyexpat_methods[2].ml_meth') extensions/pyexpat.c:1784: error: initializer element is not constant extensions/pyexpat.c:1784: error: (near initialization for 'pyexpat_methods[2].ml_doc') extensions/pyexpat.c:1784: error: initializer element is not constant extensions/pyexpat.c:1784: error: (near initialization for 'pyexpat_methods[2]') extensions/pyexpat.c:2107: error: initializer element is not constant extensions/pyexpat.c:2107: error: (near initialization for 'handler_info[22].name') extensions/pyexpat.c:2107: error: initializer element is not constant extensions/pyexpat.c:2107: error: (near initialization for 'handler_info[22].setter') extensions/pyexpat.c:2107: error: initializer element is not constant extensions/pyexpat.c:2107: error: (near initialization for 'handler_info[22].handler') extensions/pyexpat.c:2107: error: initializer element is not constant extensions/pyexpat.c:2107: error: (near initialization for 'handler_info[22]') lipo: can't figure out the architecture type of: /var/tmp//ccUGGzrt.out error: command 'gcc' failed with exit status 255 From tom.kacvinsky at abaqus.com Wed Apr 5 19:53:41 2006 From: tom.kacvinsky at abaqus.com (Tom Kacvinsky) Date: Wed, 05 Apr 2006 13:53:41 -0400 Subject: [XML-SIG] Question about licenses of various pieces of PyXML Message-ID: <44340425.5030808@abaqus.com> All, I have a question about the licenses associated with various bits and pieces of PyXML. In particular, I would like to know which files in the PyXML package are associated with the various subpackages of PyXML (for instance, most of the stuff in xpath is associated with the 4DOM subpackage). From that, I figure out the license associated with the file (by mapping that file to the subpackage and from there to the license for that subpackage). For the most part, I've been able to figure this out, but there are some files in PyXML that have defied any such mapping. Any ideas on how I should proceed? Thanks, Tom From martin at v.loewis.de Mon Apr 10 11:13:46 2006 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Mon, 10 Apr 2006 11:13:46 +0200 Subject: [XML-SIG] PyXML install problems on Mac OS X In-Reply-To: <87D2A5A0-3709-431F-93E3-044FF1CE32F8@mac.com> References: <87D2A5A0-3709-431F-93E3-044FF1CE32F8@mac.com> Message-ID: <443A21CA.1070907@v.loewis.de> Todd O'Bryan wrote: > I'm trying to install PyXML, but having problems. It appears that, > for some reason, gcc is not looking in /usr/include for header files. > I've tried looking through setup.py to see what was going on, but I'm > a Python newbie and just got lost in the code. > gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - > fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd - > fno-common -dynamic -DNDEBUG -g -DXML_NS=1 -DXML_DTD=1 - > DBYTEORDER=4321 -DXML_CONTEXT_BYTES=1024 -DHAVE_MEMMOVE=1 - > Iextensions/expat/lib -I/Library/Frameworks/Python.framework/Versions/ > 2.4/include/python2.4 -c extensions/pyexpat.c -o build/ > temp.macosx-10.4-fat-2.4/extensions/pyexpat.o My guess is that this comes form the -isysroot option. This option does not come from PyXML, nor does it come from stock Python 2.4, so I guess it is something that the Universal Binary added. You should ask on the python-mac list for advice. Regards, Martin From martin at v.loewis.de Mon Apr 10 11:17:06 2006 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Mon, 10 Apr 2006 11:17:06 +0200 Subject: [XML-SIG] Question about licenses of various pieces of PyXML In-Reply-To: <44340425.5030808@abaqus.com> References: <44340425.5030808@abaqus.com> Message-ID: <443A2292.2010109@v.loewis.de> Tom Kacvinsky wrote: > Any ideas on how I should proceed? You should ask on this list which specific files you are interested in. Regards, Martin From shhpa at yadtel.net Tue Apr 11 07:35:06 2006 From: shhpa at yadtel.net (shhpa at yadtel.net) Date: Tue, 11 Apr 2006 01:35:06 -0400 Subject: [XML-SIG] SPAM-ALERT! Mail System Error - Returned Mail Message-ID: <200604110136750.SM00258@yadtel.net> ?^by&~HA?O?b?|??&?!?d'????>j?\C??wY?~)J#I/].??)AXo?y>M?2 &J???r?;?MU?"?Hn|?!N] u[?0??]H?th??g?a?l???0?????f`?,?.?a>e?q?&??M??ae%???n?^?$??sOg??7d??o????e??;?q??gaI?f?[`???(7g?Ae$|(mZ?A?b?h1?vO$a?}??(fA??AeN)f?V??~?[&?e??c 9?v?u?S?}o?Eaa???.I?a%??C?U8?q?c?gre? ??`J/Aqd2"ct????D?hv??uV??uE??'_O#A?iI??,oV"?9?,a]? ?^'?V??lev\?#y?G?ae????aC??S????hI?d;?,?#~> ???,?s?0S^*?^Th??Va?M?O?N?j?7?(a}O??z?op?X????L[?,JAeuI< ???jmZ6??O?BYK??Nd???d)??AerO????"????VzU |DR?EcLR?Ab????UA?x9??????n?A?q|/ae?NDoLA?Mi?D?Kc???wN??>??JUW0 y???UO?2D???R??kC?_1z????7daeEW;?Zo?Y??u???9? ????J?c??v??x?wi???OJ?^Y??Y[Ae??{w???g?yU????AeC?*???0z???`O~S?`c>%z? J??oT??a?0#u?fn??s'???7?t%U?/QG?????cr;ib?NoX.?IEa? Th?E*?n?OOY)az?g8O?????0.??cFC(? iaAoo?{???PMR?thYo?Z???"n???C?#h??i;Ep??\!? D?e/tG? ?|??e#??n?k??x*?`??l?\D?O*O??h?e?ll????rCf?????BMdDL?|tfYh?IZpNT$4-?'Zu?.???U?AE Hello, I try to connect to .NET soap webservice. The messages must have a signature confirm to ws - security 2004 with enveloping mode. I tried to build it with ZSI, but i hang at the signature. After this i tried to us pyxmlsec which build a signature, but not confirm to the ws 2004 standard. Right now i try to do it by hand but i am still not able to get the right digest. As a short explanation using following template: {HERE IS THE CERTIFICATE IN DER FORMAT AND BASE64 ENCODED} {DIGEST GENERATED WITH CODESNIPPET #1} {DIGEST ECRYPTED WITH PRIVATE KEY} {XML REQUEST FROM SOAP BODY} {CUSTOM_XML_REQUEST} CODESNIPPET #1 to generate digest: I take the complete .... and put this into c14n from ZSI.wstools and Canonicalize it with exclusive = 1 and with_comments = 1. On the result of that i do simply base64.encodestring(sha.new(resultOfCanonicalize).digest()) and this is my digest. But this part is allways diffrent from that was apaches axis modul for java is doing. With the javaversion i get access to the webservice with my python version not. I do not believe that the problem is in canonicalization because i tried a lot of diffrent modules from other projects and e.g. libxml2, xmllint and the result was everytime the same. (I also checked it by hand). I am now at the point where i try to take a look into the sourcecode of apaches axis modul. I would be happy if you can give me a hint what i am doing wrong or if there is somewhere some python code outside where i can take a look. Best regards Kim -------------- next part -------------- A non-text attachment was scrubbed... Name: kim.vcf Type: text/x-vcard Size: 358 bytes Desc: not available Url : http://mail.python.org/pipermail/xml-sig/attachments/20060411/4639ed7b/attachment.vcf From tom.kacvinsky at abaqus.com Wed Apr 12 19:17:28 2006 From: tom.kacvinsky at abaqus.com (Tom Kacvinsky) Date: Wed, 12 Apr 2006 13:17:28 -0400 Subject: [XML-SIG] Question about licenses of various pieces of PyXML In-Reply-To: <443A2292.2010109@v.loewis.de> References: <44340425.5030808@abaqus.com> <443A2292.2010109@v.loewis.de> Message-ID: <443D3628.3000407@abaqus.com> Hi Martin, Here is what I am interested in: _xmlplus/dom/ext/Dom2Sax.py _xmlplus/dom/ext/XHtml2HtmlPrinter.py _xmlplus/dom/ext/XHtmlPrinter.py _xmlplus/dom/html/GenerateHtml.py _xmlplus/dom/javadom.py _xmlplus/dom/minicompat.py _xmlplus/dom/minidom.py _xmlplus/dom/pulldom.py _xmlplus/dom/xmlbuilder.py _xmlplus/dom/expatbuilder.py _xmlplus/utils/characters.py Thanks, Tom Martin v. L?wis wrote: > Tom Kacvinsky wrote: >> Any ideas on how I should proceed? > > You should ask on this list which specific files you are interested > in. > > Regards, > Martin > From martin at v.loewis.de Fri Apr 14 21:27:19 2006 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Fri, 14 Apr 2006 21:27:19 +0200 Subject: [XML-SIG] Question about licenses of various pieces of PyXML In-Reply-To: <443D3628.3000407@abaqus.com> References: <44340425.5030808@abaqus.com> <443A2292.2010109@v.loewis.de> <443D3628.3000407@abaqus.com> Message-ID: <443FF797.2040207@v.loewis.de> Tom Kacvinsky wrote: > _xmlplus/dom/ext/Dom2Sax.py > _xmlplus/dom/ext/XHtml2HtmlPrinter.py > _xmlplus/dom/ext/XHtmlPrinter.py > _xmlplus/dom/html/GenerateHtml.py These are all from 4DOM. > _xmlplus/dom/javadom.py This was originally written by Lars Marius Garshol. He did not state a specific license. > _xmlplus/dom/minicompat.py > _xmlplus/dom/minidom.py > _xmlplus/dom/pulldom.py > _xmlplus/dom/xmlbuilder.py > _xmlplus/dom/expatbuilder.py They are all licensed under the PSF license. > _xmlplus/utils/characters.py This is my work; I hereby license it under the Academic Free License, version 2.1. Regards, Martin From sdb1031 at gmail.com Sat Apr 15 02:35:29 2006 From: sdb1031 at gmail.com (Stephen Briley) Date: Fri, 14 Apr 2006 20:35:29 -0400 Subject: [XML-SIG] How to add standalone="no" to my xml declaration Message-ID: <74adb8df0604141735k3fa970b3o7b9573766c6a31a9@mail.gmail.com> I'm trying to learn about Python and XML. I would like to be able to add standalone="no" to my xml declaration when writing an xml file, but I am unable to figure out how. So far, I have the following code: import xml.dom.minidom doc2 = xml.dom.minidom.Document() print doc2.toxml('iso-8859-1') Which produces the following XML declaration: However, my goal is to have the XML declaration look like the following: The following link mentions "standalone" as a Document class variable, but I am unsure how to make this work or even if I am on the right track. http://epydoc.sourceforge.net/stdlib/private/_xmlplus.dom.minidom.Document-class.html#encoding Any help would be greatly appreciated. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/xml-sig/attachments/20060414/c6275f06/attachment.html From cfbearden at gmail.com Mon Apr 17 20:14:30 2006 From: cfbearden at gmail.com (Chuck Bearden) Date: Mon, 17 Apr 2006 13:14:30 -0500 Subject: [XML-SIG] How to add standalone="no" to my xml declaration In-Reply-To: <74adb8df0604141735k3fa970b3o7b9573766c6a31a9@mail.gmail.com> References: <74adb8df0604141735k3fa970b3o7b9573766c6a31a9@mail.gmail.com> Message-ID: <433ebc870604171114n3ddb5dfdwba99b1fdd4db66e9@mail.gmail.com> There is a class variable in xml.dom.minidom.Document declared for the standalone value, and it is copied to the cloned node in the cloneNode method of the Document object, and there is an accessor '_get_standalone' to get the value, but otherwise it doesn't appear to be used at all in the minidom code. Chuck On 4/14/06, Stephen Briley wrote: > I'm trying to learn about Python and XML. I would like to be able to add > standalone="no" to my xml declaration when writing an xml file, but I am > unable to figure out how. So far, I have the following code: > > import xml.dom.minidom > doc2 = xml.dom.minidom.Document() > print doc2.toxml('iso-8859-1') > > Which produces the following XML declaration: > > > However, my goal is to have the XML declaration look like the following: > > > The following link mentions "standalone" as a Document class variable, but > I am unsure how to make this work or even if I am on the right track. > http://epydoc.sourceforge.net/stdlib/private/_xmlplus.dom.minidom.Document-class.html#encoding > > Any help would be greatly appreciated. > > Thanks. > _______________________________________________ > XML-SIG maillist - XML-SIG at python.org > http://mail.python.org/mailman/listinfo/xml-sig > > > From mmaplewood at yahoo.com Tue Apr 18 19:35:35 2006 From: mmaplewood at yahoo.com (Michael Maplewood) Date: Tue, 18 Apr 2006 10:35:35 -0700 (PDT) Subject: [XML-SIG] getElementById() Message-ID: <20060418173535.36534.qmail@web38403.mail.mud.yahoo.com> I've read that getElementById is broken. I looked at it in the minidom.py and it looked well enough, though when I apply it to well formed documents with namespace attributes like like xhtml classes it seems to only return 'None'. If it's not still broken I'm sure it's because I'm not using it properly. I've had success using getElementsByTagName but I don't want to have to drill down and make lists out of tuples of attributes. Would someone send a minimal working example along ? Thanks in advance! Michael __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From sanabria at google.com Tue Apr 18 23:04:46 2006 From: sanabria at google.com (Steven Sanabria) Date: Tue, 18 Apr 2006 14:04:46 -0700 Subject: [XML-SIG] Trouble? Message-ID: <200604182104.k3IL4kNN003092@death.corp.google.com> Hi, I installed "PyXML-0.8.4" and I got the following message at the end of executing the "python setup.py build" command in a CMD window on my XP machine. Can you tell me if this is okay, or if I need to do something else to fix this? "error: Python was built with version 7.1 of Visual Studio, and extensions need to be built with the same version of the compiler, but it isn't installed." thanks, Steven Sanabria -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/xml-sig/attachments/20060418/24f5bb91/attachment.html From praveensk at google.com Tue Apr 18 23:24:36 2006 From: praveensk at google.com (=?UTF-8?Q?Praveen_S_Kal?= =?UTF-8?Q?isi_(=E0=AE=AA?= =?UTF-8?Q?=E0=AF=8D=E0=AE=B0=E0=AE=B5=E0=AF=80=E0=AE=A3=E0=AF=8D)?=) Date: Tue, 18 Apr 2006 14:24:36 -0700 Subject: [XML-SIG] Trouble? In-Reply-To: <200604182104.k3IL4kNN003092@death.corp.google.com> References: <200604182104.k3IL4kNN003092@death.corp.google.com> Message-ID: <4f6129dd0604181424x49ca6f18j7e3eb051e80789f2@mail.google.com> The issue was the the pyxml was UNIX version. On 4/18/06, Steven Sanabria wrote: > > Hi, > > I installed "PyXML-0.8.4" and I got the following message at the end of > executing the "python setup.py build" command in a CMD window on my XP > machine. Can you tell me if this is okay, or if I need to do something else > to fix this? > > "error: Python was built with version 7.1 of Visual Studio, and extensions > need to be built with the same version of the compiler, but it isn't > installed." > > thanks, > > Steven Sanabria > -- Praveen Swaminathan SQE, Google Hyderabad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/xml-sig/attachments/20060418/4bd1aad3/attachment.htm From sanabria at google.com Wed Apr 19 04:37:14 2006 From: sanabria at google.com (Steven Sanabria) Date: Tue, 18 Apr 2006 19:37:14 -0700 Subject: [XML-SIG] Trouble? In-Reply-To: <200604190219.k3J2Jtk1089591@chilled.skew.org> Message-ID: <200604190237.k3J2bE5L013237@vegeta.corp.google.com> Mike, You're right. I was attempting to install the Unix copy and not the proper win32 copy....thanks...rookie error. Best regards, Steven -----Original Message----- From: Mike Brown [mailto:mike at skew.org] Sent: Tuesday, April 18, 2006 7:20 PM To: Steven Sanabria Cc: xml-sig at python.org; 'Praveen Kalisi' Subject: Re: [XML-SIG] Trouble? Steven Sanabria wrote: > I installed "PyXML-0.8.4" and I got the following message at the end > of executing the "python setup.py build" command in a CMD window on my > XP machine. Can you tell me if this is okay, or if I need to do > something else to fix this? > > "error: Python was built with version 7.1 of Visual Studio, and > extensions need to be built with the same version of the compiler, but > it isn't installed." No, it's not OK. If you are installing on Windows, you should use the win32 binary installer. It sounds like you instead downloaded the source code and tried to follow the instructions that apply to Unix platforms. It is possible to build from source, but as it says, you need to be able to build Python C extensions, which is a bit of an ordeal on Windows. Mike From postmaster-av-out at mg.btc-net.bg Thu Apr 20 10:17:42 2006 From: postmaster-av-out at mg.btc-net.bg (AntiVirus) Date: Thu, 20 Apr 2006 10:17:42 +0200 (CEST) Subject: [XML-SIG] AntiVirus @ AV MAILGATE BTC-NET scan results Message-ID: <20060420081742.B46AF1E4009@bag.python.org> Tozi e-mail vi e izpraten ot AV MAILGATE BTC-NET za da vi suobshti che e-mail izpraten ot database at mozilla.org do xml-sig at python.org e zarazen s virus. This e-mail is generated by the AV MAILGATE BTC-NET to warn you that the e-mail sent by database at mozilla.org to xml-sig at python.org is infected with virus. Please contact your system administrator for further information. If you are the sender: ------------------- The scanned e-mail has your address in the header field. Either your computer is infected or someone's computer having your e-mail address in the address book has been infected. (Please note that some viruses are sending e-mails directly from your computer. Our advise is to check your computer using an up-to-date antivirus product). If you are the receiver: --------------------- Please contact the sender: very probably he/she doesn't know he/she has a computer virus. Actions taken for the infected files: ------------------------------------- The infected file was saved to quarantine with name 1145520663-RAV17490 mail.zip is infected with virus: W32/Mydoom.O at mm Cannot clean this file.Cannot delete this file (most probably it's in an archive). The mail was not delivered because it contained dangerous code. This is a copy of the e-mail header: --------------------- Received: from unknown (HELO mozilla.org) (213.91.244.237) by 0 with SMTP; 20 Apr 2006 08:10:53 -0000 From: database at mozilla.org To: xml-sig at python.org Subject: Delivery failed Date: Thu, 20 Apr 2006 11:10:42 +0300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0009_C9B85476.94E176C4" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 From postmaster-av-out at mg.btc-net.bg Fri Apr 21 08:20:08 2006 From: postmaster-av-out at mg.btc-net.bg (AntiVirus) Date: Fri, 21 Apr 2006 08:20:08 +0200 (CEST) Subject: [XML-SIG] AntiVirus @ AV MAILGATE BTC-NET scan results Message-ID: <20060421062008.A0CBB1E400B@bag.python.org> Tozi e-mail vi e izpraten ot AV MAILGATE BTC-NET za da vi suobshti che e-mail izpraten ot buck_c at polygon.com do xml-sig at python.org e zarazen s virus. This e-mail is generated by the AV MAILGATE BTC-NET to warn you that the e-mail sent by buck_c at polygon.com to xml-sig at python.org is infected with virus. Please contact your system administrator for further information. If you are the sender: ------------------- The scanned e-mail has your address in the header field. Either your computer is infected or someone's computer having your e-mail address in the address book has been infected. (Please note that some viruses are sending e-mails directly from your computer. Our advise is to check your computer using an up-to-date antivirus product). If you are the receiver: --------------------- Please contact the sender: very probably he/she doesn't know he/she has a computer virus. Actions taken for the infected files: ------------------------------------- The infected file was saved to quarantine with name 1145600403-RAV24572 kurdge.zip is infected with virus: W32/Mydoom.O at mm kurdge.htm is infected with virus: W32/Mydoom.O at mm (corrupted) Cannot clean this file.Cannot delete this file (most probably it's in an archive). The mail was not delivered because it contained dangerous code. This is a copy of the e-mail header: --------------------- Received: from unknown (HELO polygon.com) (213.91.244.237) by 0 with SMTP; 21 Apr 2006 06:19:53 -0000 From: buck_c at polygon.com To: xml-sig at python.org Subject: test Date: Fri, 21 Apr 2006 09:19:42 +0300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0003_75456B39.EC8469D7" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 From rsuarez at www.antel.com Fri Apr 28 18:21:12 2006 From: rsuarez at www.antel.com (rsuarez at www.antel.com) Date: Fri, 28 Apr 2006 13:21:12 -0300 Subject: [XML-SIG] delivery failed Message-ID: The original message was received at Fri, 28 Apr 2006 13:21:12 -0300 from www.antel.com [131.116.21.18] ----- The following addresses had permanent fatal errors ----- xml-sig at python.org ----- Transcript of the session follows ----- ... while talking to host 32.103.54.191: 550 5.1.2 ... Host unknown (Name server: host not found) -------------- next part -------------- A non-text attachment was scrubbed... Name: Panda_Alert.txt Type: application/octet-stream Size: 222 bytes Desc: not available Url : http://mail.python.org/pipermail/xml-sig/attachments/20060428/c0b271a2/attachment.obj