467,161 Members | 1,032 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,161 developers. It's quick & easy.

py2exe & pyxml

Does anyone know how to resolve the following problem that I'm getting in
Python 2.2 and 2.3?

PROBLEM: When I try to create a classReader object I get an exception:
"SAXReaderNotAvailable: No parsers found". This only happens when I run the
..EXE; it does not happen if I run the .PY file. When I'm running the .EXE
this exception doesn't happen immediately. It happens as soon as I try to
create a classReader object.

Please see the warnings that I get below when I create the .EXE:
**********
warning: py2exe: * The following modules were not found: warning: py2exe:
* Carbon.Folder warning: py2exe: * Carbon.Folders warning: py2exe: *
DateTime warning: py2exe: * Ft.Lib warning: py2exe: *
Ft.Lib.DumpBgTuple warning: py2exe: * Ft.__init__ warning: py2exe: *
SOCKS warning: py2exe: * XPathParserc warning: py2exe: *
ext.IsDOMString warning: py2exe: * ext.SplitQName warning: py2exe: *
fcntl warning: py2exe: * ic warning: py2exe: * mx.DateTime warning:
py2exe: * rourl2path warning: py2exe: * xml.xslt warning: py2exe: *
xml.xslt.ParsedPattern warning: py2exe:
************************************************ ***************


__________________________________________________ _______________
Try MSN Messenger 6.0 with integrated webcam functionality!
http://www.msnmessenger-download.com...g/reach_webcam
Jul 18 '05 #1
  • viewed: 4393
Share:
8 Replies
"Kathleen Kudzma" <km******@hotmail.com> writes:
PROBLEM: When I try to create a classReader object I get an exception:
"SAXReaderNotAvailable: No parsers found". This only happens when I
run the .EXE; it does not happen if I run the .PY file. When I'm
running the .EXE this exception doesn't happen immediately. It
happens as soon as I try to create a classReader object.


You have to explicitly ask py2exe to include pyexpat in the
executable. RTFM.

Regards,
Martin
Jul 18 '05 #2

"Kathleen Kudzma" <km******@hotmail.com> wrote in message
news:ma**********************************@python.o rg...
Does anyone know how to resolve the following problem that I'm getting in
Python 2.2 and 2.3?

PROBLEM: When I try to create a classReader object I get an exception:
"SAXReaderNotAvailable: No parsers found". This only happens when I run the
.EXE; it does not happen if I run the .PY file. When I'm running the .EXE
this exception doesn't happen immediately. It happens as soon as I try to
create a classReader object.

Please see the warnings that I get below when I create the .EXE:
**********
warning: py2exe: * The following modules were not found: warning: py2exe:
* Carbon.Folder warning: py2exe: * Carbon.Folders warning: py2exe: *
DateTime warning: py2exe: * Ft.Lib warning: py2exe: *
Ft.Lib.DumpBgTuple warning: py2exe: * Ft.__init__ warning: py2exe: *
SOCKS warning: py2exe: * XPathParserc warning: py2exe: *
ext.IsDOMString warning: py2exe: * ext.SplitQName warning: py2exe: *
fcntl warning: py2exe: * ic warning: py2exe: * mx.DateTime warning:
py2exe: * rourl2path warning: py2exe: * xml.xslt warning: py2exe: *
xml.xslt.ParsedPattern warning: py2exe:
************************************************ ***************


Yes, I've just had the same problem -- using py3.2 and py2exe v0.4.2

After spending some time in a debugger following the execution path, I found
out that the module xml.sax.drivers2.drv_pyexpat is the one that is missing.
It gets loaded through a call to __import__ (see _xmlplus.sax.saxexts.py, line
42) which is why py2exe doesn't pick it up as being necessary.

All of which means it has to be explicitly included in the build. So, I was
able to solve the problem with the following setup.py command line:

python setup.py py2exe --includes xml.sax.drivers2.drv_pyexpat

I've no idea what Martin was referring to when he said RTFM, because I could
find nothing about this. (Then again, perhaps I'm misunderstanding what he
means by RTFM?)

--
Mike

Jul 18 '05 #3
"Mike Thompson" <none by e-mail> wrote in message news:<3f***********************@news.optusnet.com. au>...
"Kathleen Kudzma" <km******@hotmail.com> wrote in message
news:ma**********************************@python.o rg...
Does anyone know how to resolve the following problem that I'm getting in
Python 2.2 and 2.3?

PROBLEM: When I try to create a classReader object I get an exception:
"SAXReaderNotAvailable: No parsers found". This only happens when I run the
.EXE; it does not happen if I run the .PY file. When I'm running the .EXE
this exception doesn't happen immediately. It happens as soon as I try to
create a classReader object.

Please see the warnings that I get below when I create the .EXE:
**********
>warning: py2exe: * The following modules were not found: warning: py2exe:
>* Carbon.Folder warning: py2exe: * Carbon.Folders warning: py2exe: *
>DateTime warning: py2exe: * Ft.Lib warning: py2exe: *
>Ft.Lib.DumpBgTuple warning: py2exe: * Ft.__init__ warning: py2exe: *
>SOCKS warning: py2exe: * XPathParserc warning: py2exe: *
>ext.IsDOMString warning: py2exe: * ext.SplitQName warning: py2exe: *
>fcntl warning: py2exe: * ic warning: py2exe: * mx.DateTime warning:
>py2exe: * rourl2path warning: py2exe: * xml.xslt warning: py2exe: *
>xml.xslt.ParsedPattern warning: py2exe:
>************************************************ ***************


Yes, I've just had the same problem -- using py3.2 and py2exe v0.4.2

After spending some time in a debugger following the execution path, I found
out that the module xml.sax.drivers2.drv_pyexpat is the one that is missing.
It gets loaded through a call to __import__ (see _xmlplus.sax.saxexts.py, line
42) which is why py2exe doesn't pick it up as being necessary.

All of which means it has to be explicitly included in the build. So, I was
able to solve the problem with the following setup.py command line:

python setup.py py2exe --includes xml.sax.drivers2.drv_pyexpat

I've no idea what Martin was referring to when he said RTFM, because I could
find nothing about this. (Then again, perhaps I'm misunderstanding what he
means by RTFM?)


RTFM is tech jargon for "read the f**king manual".
Jul 18 '05 #4
Steven Bell wrote:
I've no idea what Martin was referring to when he said RTFM, because I could
find nothing about this. (Then again, perhaps I'm misunderstanding what he
means by RTFM?)


RTFM is tech jargon for "read the f**king manual".


In the Python world this usually reads as "Read The Felicitous Manual" :-)

--
Marc-Andre Lemburg
eGenix.com

Professional Python Software directly from the Source (#1, Oct 09 2003)
Python/Zope Products & Consulting ... http://www.egenix.com/
mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/

__________________________________________________ ______________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
Jul 18 '05 #5
> [ma****@v.loewis.de (Martin v. Lwis)]
You have to explicitly ask py2exe to include pyexpat in the
executable. RTFM.


*If* you are going to say RTFM you'd better make sure it *is* in the
manual. Otherwise you'd better s-h-a-d-d-u-p.

Next time you feel like saying "RTFM" in comp.lang.python either
(1) say it in comp.lang.java
(2) copy and paste the URL to the manual and point out the Section you
feel they should read.

--
Q: How many Democrats does it take to enjoy a good joke?
A: One more than you can find.
Jul 18 '05 #6
hw***@hotmail.com (Will Stuyvesant) writes:
[ma****@v.loewis.de (Martin v. Löwis)]
You have to explicitly ask py2exe to include pyexpat in the
executable. RTFM.


*If* you are going to say RTFM you'd better make sure it *is* in the
manual. Otherwise you'd better s-h-a-d-d-u-p.


See http://starship.python.net/crew/theller/py2exe/,
in "Flags to include or exclude modules or packages:"

Regards,
Martin
Jul 18 '05 #7

"Martin v. Lwis" <ma****@v.loewis.de> wrote in message
news:m3************@mira.informatik.hu-berlin.de...
hw***@hotmail.com (Will Stuyvesant) writes:
[ma****@v.loewis.de (Martin v. Lwis)]
You have to explicitly ask py2exe to include pyexpat in the
executable. RTFM.


*If* you are going to say RTFM you'd better make sure it *is* in the
manual. Otherwise you'd better s-h-a-d-d-u-p.


See http://starship.python.net/crew/theller/py2exe/,
in "Flags to include or exclude modules or packages:"


But, Martin, there's absolutely no mention of 'expat' in this entire document,
much less that section. So, how on earth was the advice 'RTFM' to help?

In the end, I was able to find an answer by stepping through code with a
debugger to find the module which wasn't being included. THAT
('xml.sax.drivers2.drv_pyexpat') was the unknown. THAT was the information
sort, by the original poster, I'm sure. If it wasn't then they needed a lot
more hand-holding than you're terse abuse.

In any case, I'll see if I can get this added to the pyexe documentation,
because I'd imagine this must be a recurring problem ... surely? Oddly I could
find absolutely nothing on this subject, apart from this lone thread, when I
originally googled around for an answer.

--
Mike
Jul 18 '05 #8

"Steven Bell" wrote:
"Mike Thompson":
"Kathleen Kudzma":
Does anyone know how to resolve the following problem that I'm getting in
Python 2.2 and 2.3?

PROBLEM: When I try to create a classReader object I get an exception:
"SAXReaderNotAvailable: No parsers found". This only happens when I run the .EXE; it does not happen if I run the .PY file. When I'm running the ..EXE this exception doesn't happen immediately. It happens as soon as I try to create a classReader object.

Please see the warnings that I get below when I create the .EXE:

>**********
>>warning: py2exe: * The following modules were not found: warning: py2exe: >>* Carbon.Folder warning: py2exe: * Carbon.Folders warning: py2exe: * >>DateTime warning: py2exe: * Ft.Lib warning: py2exe: *
>>Ft.Lib.DumpBgTuple warning: py2exe: * Ft.__init__ warning: py2exe: *
>>SOCKS warning: py2exe: * XPathParserc warning: py2exe: *
>>ext.IsDOMString warning: py2exe: * ext.SplitQName warning: py2exe: *
>>fcntl warning: py2exe: * ic warning: py2exe: * mx.DateTime warning:
>>py2exe: * rourl2path warning: py2exe: * xml.xslt warning: py2exe: *
>>xml.xslt.ParsedPattern warning: py2exe:
>>************************************************ ***************


Yes, I've just had the same problem -- using py3.2 and py2exe v0.4.2

After spending some time in a debugger following the execution path, I found out that the module xml.sax.drivers2.drv_pyexpat is the one that is missing. It gets loaded through a call to __import__ (see _xmlplus.sax.saxexts.py, line 42) which is why py2exe doesn't pick it up as being necessary.

All of which means it has to be explicitly included in the build. So, I was able to solve the problem with the following setup.py command line:

python setup.py py2exe --includes xml.sax.drivers2.drv_pyexpat

I've no idea what Martin was referring to when he said RTFM, because I could find nothing about this. (Then again, perhaps I'm misunderstanding what he
means by RTFM?)


RTFM is tech jargon for "read the f**king manual".

Yes. Except its not in the f**king manual, so I've no idea why Matrin is being
abusive.

--
Mike
Jul 18 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by RJS | last post: by
1 post views Thread by | last post: by
12 posts views Thread by Alessandro Crugnola *sephiroth* | last post: by
2 posts views Thread by David Brownell | last post: by
3 posts views Thread by anthony hornby | last post: by
1 post views Thread by Dan | last post: by
5 posts views Thread by Matthias Kaeppler | last post: by
1 post views Thread by shane.external@gmail.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.