Read Roberts <rroberts@...> writes:
> My apologies, my first message left out some basic info:
> The problem occurs under Windows 2000 and Windows XP, with a plain
> Python 2.3.4 binary install., and py2exe 0.53
>
>
> I discovered that my Python application for the Japanese market
> doesn't work when moved into a path that has some non-ascii
> characters. Is there any way around this?
This has probably to do with that py2exe builds PYTHONPATH and sys.path
at runtime. You have to look in the source/run.c file in the sources.
Either you can come up with a patch yourself, or maybe you should tell
me how to create a directory with kanjii characters in it, so I can try
it myself.
Thomas

Ali Polatel <alipolatel@...> writes:
> Dear Friends,
> I want to ask if it is possible to pack all those files that I have
> got after a py2exe compile into one single zip/exe file...I mean not a
> setup file but a file which will auto-extract the important files when
> run and will run the exe and then delete the extracted files again
> when shut
There's a sample on the wiki which does exactly this, if I understand
correctly.
Thomas

Dear Friends,
I want to ask if it is possible to pack all those files that I have got after a py2exe compile into one single zip/exe file...I mean not a setup file but a file which will auto-extract the important files when run and will run the exe and then delete the extracted files again when shut
Thanks and regards
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!

My apologies, my first message left out some basic info:
The problem occurs under Windows 2000 and Windows=20
XP, with a plain Python 2.3.4 binary install.,=20
and py2exe 0.53
I discovered that my Python application for the=20
Japanese market doesn't work when moved into a=20
path that has some non-ascii characters. Is there=20
any way around this?
I built a very simple test program:
#test.py, my test app
raise KeyError("Well, the main program did get=20
run.") # so i get a log file output to gmt.log.
# end test app
with a very simple setup.py, cut down from one the one I use for the prodcut=
:
# my setup.py
# execute distutils.core setup
basedir =3D os.path.abspath(os.path.dirname(sys.argv[0]))
distdir =3D os.path.join(basedir, "testpp")
setup(
name =3D "Adobe Glyphet Manager",
description =3D "Adobe SING Glyphet Management Tool",
zipfile =3D =89, # has bogus extension to obscure fact this is a .zip file
windows =3D [
{
"script": "test.py", # application script
}
],
options =3D {
"py2exe": {
"includes": "encodings",
"packages": "encodings",
"dist_dir": distdir,
},
},
)
#end my setup.py
This builds just fine, and the test program runs=20
just fine even under J systems - as long as the=20
dir path to the modules.dll is ascii. If I put=20
the Kanji string ( utf -8 )"" into the path, then=20
it doesn't run. I thought I might be able to=20
promote the sys.path to Unicode by specifying=20
the zipfile as u"modules.dll", but then I get a=20
message from some component named mkpath that the=20
resulting path to the zip file is not a string.
Any suggestions?
- Read Roberts

I discovered that my Python application for the=20
Japanese market doesn't work when moved into a=20
path that has some non-ascii characters. Is there=20
any way around this?
I built a very simple test program:
#test.py, my test app
raise KeyError("Well, the main program did get=20
run.") # so i get a log file output to gmt.log.
# end test app
with a very simple setup.py, cut down from one the one I use for the prodcut=
:
# my setup.py
# execute distutils.core setup
basedir =3D os.path.abspath(os.path.dirname(sys.argv[0]))
distdir =3D os.path.join(basedir, "testpp")
setup(
name =3D "Adobe Glyphet Manager",
description =3D "Adobe SING Glyphet Management Tool",
zipfile =3D =89, # has bogus extension to obscure fact this is a .zip file
windows =3D [
{
"script": "test.py", # application script
}
],
options =3D {
"py2exe": {
"includes": "encodings",
"packages": "encodings",
"dist_dir": distdir,
},
},
)
#end my setup.py
This builds just fine, and the test program runs=20
just fine even under J systems - as long as the=20
dir path to the modules.dll is ascii. If I put=20
the Kanji string ( utf -8 )"" into the path, then=20
it doesn't run. I thought I might be able to=20
promote the sys.path to Unicode by specifying=20
the zipfile as u"modules.dll", but then I get a=20
message from some component named mkpath that the=20
resulting path to the zip file is not a string.
Any suggestions?
- Read Roberts