From ken@be.com Mon Oct 4 16:44:51 1999 From: ken@be.com (ken) Date: Mon, 04 Oct 1999 15:44:51 GMT Subject: [Image-SIG] Couple of small problems with the Python Imaging Library, any suggestions? Message-ID: <199910042327.TAA18268@python.org> Hi all. I've just started using PIL, and have encountered the following problems: 1) Under win 98, when I run the included "setup.bat", which sets some necessary environment variables, I get an "Out of environment space" from the DOS shell on the last two commands, which are attempting to set the TCL_LIBRARY and TK_LIBRARY variables. This is with the precompiled Python/Tk/Pil distro. Anyone else seen this? 2) I have PIL compiled and installed under Linux, but am getting a link error off of an X library, I think--says it can't find XPixMap, or something to that effect. I'll look into this in more detail, but though I might post this in case this is a well know problem. Thanks, Ken From KCAZA@cymbolic.com Tue Oct 5 00:58:48 1999 From: KCAZA@cymbolic.com (Kevin Cazabon) Date: Mon, 04 Oct 1999 16:58:48 -0700 Subject: [Image-SIG] Couple of small problems with the Python Imaging Library, any suggestions? Message-ID: As far as I know, if you're using the precompiled Windows binaries, there's only a couple things that need to be set up: -the PIL directory has to be in the PYTHONPATH -the new _tkinter.dll should replace the _tkinter.pyd file in the DLLs folder of Python (if they're both there, Python will load the older .pyd first, and you'll have problems displaying graphics using Tk) You can easily add the PIL directory to the Pythonpath manually, either using the Edit Python Path tool in Pythonwin, or searching the registry (using Regedit) for 'pythonpath' and adding it there. Kevin Cazabon, hacker-at-large. q:] >>> "ken" 10/04/99 08:44AM >>> Hi all. I've just started using PIL, and have encountered the following problems: 1) Under win 98, when I run the included "setup.bat", which sets some necessary environment variables, I get an "Out of environment space" from the DOS shell on the last two commands, which are attempting to set the TCL_LIBRARY and TK_LIBRARY variables. This is with the precompiled Python/Tk/Pil distro. Anyone else seen this? 2) I have PIL compiled and installed under Linux, but am getting a link error off of an X library, I think--says it can't find XPixMap, or something to that effect. I'll look into this in more detail, but though I might post this in case this is a well know problem. Thanks, Ken _______________________________________________ Image-SIG maillist - Image-SIG@python.org http://www.python.org/mailman/listinfo/image-sig From KCAZA@cymbolic.com Tue Oct 5 01:04:54 1999 From: KCAZA@cymbolic.com (Kevin Cazabon) Date: Mon, 04 Oct 1999 17:04:54 -0700 Subject: [Image-SIG] TIFF fixes... Mac and PC Message-ID: A while back, Fred posted a link to a couple TIFF plugin patches that resolved some compatibility issues (so far, perfectly). Have these been built into the current 'release' yet, or forgotten about? From what I can tell, the current postings do not yet have these mods in place. This is especially true with the Mac precompiled releases, which I've been trying to get a hold of (I don't have a Mac compiler at all, nor the patience!) q:] So far, Fred, the patches work perfectly (I've made ~500 files so far under NT, up to 400MB each, and they've given me no problems). Kevin Cazabon From jwt-python@dskk.co.jp Tue Oct 5 03:00:24 1999 From: jwt-python@dskk.co.jp (Jim Tittsler) Date: Tue, 5 Oct 1999 11:00:24 +0900 Subject: [Image-SIG] Win98 Environment Size [was: Couple of small problems with the Python Imaging Library, any suggestions?] In-Reply-To: <199910042327.TAA18268@python.org>; from ken on Mon, Oct 04, 1999 at 03:44:51PM +0000 References: <199910042327.TAA18268@python.org> Message-ID: <19991005110024.A10778@mail.dskk.co.jp> On Mon, Oct 04, 1999 at 03:44:51PM +0000, ken wrote: > 1) Under win 98, when I run the included "setup.bat", which sets some > necessary environment variables, I get an "Out of environment space" from > the DOS shell on the last two commands, which are attempting to set the > TCL_LIBRARY and TK_LIBRARY variables. [...] You can increase the environment size available for COMMAND.COM by adding (or editing) this line in your C:\CONFIG.SYS file: SHELL=C:\COMMAND.COM C:\ /E:1024 /P (assuming you have a copy of COMMAND.COM in C:\) where the /E:nnnn option allows you to specify your environment size. From fredrik@pythonware.com Wed Oct 6 11:53:14 1999 From: fredrik@pythonware.com (Fredrik Lundh) Date: Wed, 6 Oct 1999 12:53:14 +0200 Subject: [Image-SIG] PIL buglet? References: Message-ID: <00fa01bf0fe9$b076de40$f29b12c2@secret.pythonware.com> Perry Stoll wrote: > Can you explain why you are reluctant to change something that is > obviously broken and dangerous, and is going to cause mysterious > and hard to trace errors? because changing this at this time will cause mysterious and hard to trace errors for everyone using PIL together with an external plugin, while keeping things as is won't hurt anyone. after all, Georg's crashes came *after* he'd changed this (and thus ended up with a mismatching tkinter). PIL 1.1 will have an entirely different memory layout, but that's another story. From fredrik@pythonware.com Wed Oct 6 11:58:13 1999 From: fredrik@pythonware.com (Fredrik Lundh) Date: Wed, 6 Oct 1999 12:58:13 +0200 Subject: [Image-SIG] TIFF fixes... Mac and PC References: Message-ID: <00fb01bf0fe9$b0ba28d0$f29b12c2@secret.pythonware.com> Kevin Cazabon wrote: > A while back, Fred posted a link to a couple TIFF plugin patches that resolved some > compatibility issues (so far, perfectly). Have these been built into the current > 'release' yet, or forgotten about? From what I can tell, the current postings do not > yet have these mods in place. This is especially true with the Mac precompiled > releases, which I've been trying to get a hold of (I don't have a Mac compiler at > all, nor the patience!) q:] the new TIFF driver is included in the final 1.0 release. (but I don't have a Mac, so I cannot help you with a precompiled version... so if anyone here has a Mac, a compiler, and a little time to spare, let me know. we can host Mac builds on our site, if necessary). From fredrik@pythonware.com Wed Oct 6 12:01:28 1999 From: fredrik@pythonware.com (Fredrik Lundh) Date: Wed, 6 Oct 1999 13:01:28 +0200 Subject: [Image-SIG] Couple of small problems with the Python Imaging Library, any suggestions? References: <199910042327.TAA18268@python.org> Message-ID: <010d01bf0fea$252bbad0$f29b12c2@secret.pythonware.com> ken wrote: > 2) I have PIL compiled and installed under Linux, but am getting a link > error off of an X library, I think--says it can't find XPixMap, or something > to that effect. I'll look into this in more detail, but though I might post > this in case this is a well know problem. adding -lX11 to the Setup file should do the trick. (this is fixed in the upcoming 1.0.1) From kuncej@mail.conservation.state.mo.us Wed Oct 6 15:38:13 1999 From: kuncej@mail.conservation.state.mo.us (Jeffrey Kunce) Date: Wed, 06 Oct 1999 09:38:13 -0500 Subject: [Image-SIG] PIL 1.0 final for NT Message-ID: Is there a pre-compiled version of PIL 1.0 final for NT? Where can I find it? Thanks. --Jeff From galle@rostock.zgdv.de Fri Oct 8 10:59:59 1999 From: galle@rostock.zgdv.de (Torsten Gallmeister) Date: Fri, 08 Oct 1999 11:59:59 +0200 Subject: [Image-SIG] SunOS Problem? Message-ID: <37FDC09F.7534BF75@rostock.zgdv.de> Hello, if I execute the code below with Pyhton1.5.2 and PIL-1.0 at SunOS 5.6 and I only get an black rectangle. With Linux does it work. Is this an known problem or is there another solution to put colors in a new image? Thanks, Torsten. ###################################### import Image import ImageDraw im = Image.new("P", (400, 400), 0) im.putpalette([ 0, 0, 0, # black background 255, 0, 0, # index 1 is red 255, 255, 0, # index 2 is yellow 255, 153, 0, # index 3 is orange ]) d = ImageDraw.ImageDraw(im) d.setfill(1) d.setink(1) d.polygon((0, 0, 0, 400, 400, 400)) d.setink(2) d.rectangle((100, 100, 300, 300)) d.setink(3) d.ellipse((120, 120, 280, 280)) im.save("out.gif") ############################################################ From akuchlin@mems-exchange.org Fri Oct 8 17:06:01 1999 From: akuchlin@mems-exchange.org (Andrew M. Kuchling) Date: Fri, 8 Oct 1999 12:06:01 -0400 (EDT) Subject: [Image-SIG] Frame grabber support Message-ID: <199910081606.MAA15879@amarok.cnri.reston.va.us> I'm now faced with writing a little C extension that would support Alessandro Rubini's Linux driver for the PXC-200 frame grabber. The last time I had to support an image acquisition device, I wrote a special SANE module. I can just sit down and write a PXC-200 module, but this way potential madness lies; we may end up with 187 different little modules. Fredrik, one of the items included in PIL Plus is simply "Device drivers". Is this support for frame grabbers and other image acquisition devices? Is there some framework for adding new drivers without requiring an entirely different module for each device? If not, I'll probably just do the easy thing, writing a new module for this one specific driver and making it available on our Web site. -- A.M. Kuchling http://starship.python.net/crew/amk/ "I didn't know that there was a downstairs, here." "There's a downstairs in everybody. That's where we live." -- Lyta and the youngest of the Three, in SANDMAN #58: "The Kindly Ones:2" From fredrik@pythonware.com Wed Oct 13 09:08:35 1999 From: fredrik@pythonware.com (Fredrik Lundh) Date: Wed, 13 Oct 1999 10:08:35 +0200 Subject: [Image-SIG] Re: ImageTk.PhotoImage vs. Tkinter.PhotoImage References: <14319.55768.317546.946593@gargle.gargle.HOWL> <3.0.1.32.19990929084720.0090cd90@pop.netmeg.net> Message-ID: <01cb01bf1552$26cf3ac0$f29b12c2@secret.pythonware.com> Les Schaffer wrote: > still, the more illuminating topic would be why the parallel design of > PhotoImage in both Tkinter and ImageTk? why doesnt the latter inherit the > former. why do they co-exist side by side? no special reason; it's just the way it was done the first time... I've added this as a low-priority (I've never seen this as a problem ;-) item to the PIL wishlist... From fredrik@pythonware.com Wed Oct 13 09:02:54 1999 From: fredrik@pythonware.com (Fredrik Lundh) Date: Wed, 13 Oct 1999 10:02:54 +0200 Subject: [Image-SIG] SunOS Problem? References: <37FDC09F.7534BF75@rostock.zgdv.de> Message-ID: <01c301bf1551$6442b1d0$f29b12c2@secret.pythonware.com> Torsten Gallmeister wrote: > if I execute the code below with Pyhton1.5.2 and PIL-1.0 at SunOS 5.6 > and I only get an black rectangle. With Linux does it work. Is this an > known problem or is there another solution to put colors in a new > image? it was a known problem in the 1.0 betas, but I thought this has been fixed in 1.0 final ? can you check that you're really using the latest and greatest version? (Image.VERSION should be "1.0", and the history log at the top of Image.py should have an entry saying: # 99-07-28 fl PIL release 1.0 final) From herzog@online.de Thu Oct 21 10:50:51 1999 From: herzog@online.de (Bernhard Herzog) Date: 21 Oct 1999 11:50:51 +0200 Subject: [Image-SIG] Bug in PNG decoder Message-ID: Hi, a Sketch user has told me about a problem with the PNG decoder. When I try to load the file http://www.online.de/home/sketch/Images/usengl.png I get the following exception: Python 1.5.2 (#3, Apr 21 1999, 16:51:54) [GCC 2.7.2.3] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> import Image >>> Image.open('usengl.png') >>> _.load() Traceback (innermost last): File "", line 1, in ? File "/usr/local/lib/python1.5/site-packages/PIL/ImageFile.py", line 161, in load raise IOError, "decoder error %d when reading image file" % e IOError: decoder error -3 when reading image file >>> -- Bernhard Herzog | Sketch, a drawing program for Unix herzog@online.de | http://www.online.de/home/sketch/ From akuchlin@mems-exchange.org Thu Oct 21 15:48:44 1999 From: akuchlin@mems-exchange.org (Andrew M. Kuchling) Date: Thu, 21 Oct 1999 10:48:44 -0400 (EDT) Subject: [Image-SIG] Bug in PNG decoder In-Reply-To: References: Message-ID: <14351.10188.835919.782736@amarok.cnri.reston.va.us> Bernhard Herzog writes: >Traceback (innermost last): > File "", line 1, in ? > File "/usr/local/lib/python1.5/site-packages/PIL/ImageFile.py", line 161, in load > raise IOError, "decoder error %d when reading image file" % e >IOError: decoder error -3 when reading image file This looks suspiciously like something I ran into, but never solved. A problem with zlib seems likely, because when I dropped back from zlib1.1.3 to 1.1.1 it went away, but it never got boiled down to a simple test case, nor did I ever determine if it was a problem with zlib or a bug in PIL's use of zlib. (I was leaning toward zlib, but never proved that.) If you can reproduce the problem, try compiling PIL with an older version of zlib and see if the error still appears. -- A.M. Kuchling http://starship.python.net/crew/amk/ Destiny smells of dust and the libraries of night. He leaves no footprints. He casts no shadow. -- From SANDMAN: "Season of Mists", episode 0 From herzog@online.de Sun Oct 24 20:51:22 1999 From: herzog@online.de (Bernhard Herzog) Date: 24 Oct 1999 21:51:22 +0200 Subject: [Image-SIG] Bug in PNG decoder In-Reply-To: "Andrew M. Kuchling"'s message of "Thu, 21 Oct 1999 10:48:44 -0400 (EDT)" References: <14351.10188.835919.782736@amarok.cnri.reston.va.us> Message-ID: "Andrew M. Kuchling" writes: > Bernhard Herzog writes: > >Traceback (innermost last): > > File "", line 1, in ? > > File "/usr/local/lib/python1.5/site-packages/PIL/ImageFile.py", line 161, in load > > raise IOError, "decoder error %d when reading image file" % e > >IOError: decoder error -3 when reading image file > > This looks suspiciously like something I ran into, but never solved. > A problem with zlib seems likely, because when I dropped back from > zlib1.1.3 to 1.1.1 it went away, but it never got boiled down to a > simple test case, nor did I ever determine if it was a problem with > zlib or a bug in PIL's use of zlib. (I was leaning toward zlib, but > never proved that.) If you can reproduce the problem, try compiling > PIL with an older version of zlib and see if the error still appears. I've looked a bit into this by generating PNGs with Gimp and loading them with PIL. The only conclusion so far is that PIL definitely doesn't like interlaced PNGs. The particular file I mentioned in my first post is interlaced, so that probably explains the problems. PIL raised the same exception with some other non-interlaced PNGs as well. There may indeed be a zlib related problem because changing the compression level can solve it. -- Bernhard Herzog | Sketch, a drawing program for Unix herzog@online.de | http://www.online.de/home/sketch/