From fredrik_lundh@ivab.se Wed Nov 6 11:35:24 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Wed, 6 Nov 1996 12:35:24 +0100 Subject: [PYTHON IMAGE-SIG] Problems (and solutions) for Tk 4.2 on Windows In-Reply-To: message from fredrik on 4 Nov 1996 09:38:40 +0100 Message-ID: <9611061135.AA02235@arnold.image.ivab.se> (a similar message was just posted to the wintcl discussion list) As some of you might have noticed, the Tk 4.2 PhotoImage code is seriously broken for 16-bit "HighColor" Windows displays, at least on Windows 95. The first of the attached patches fixes the bug in a rather crude fashion (tested on win95 only). The second patch is a Windows-specific patch that boosts performance for 16/24-bit displays. Here's the result from a sample program which loads two 512x512 greyscale PGM's, and two 512x512 colour PPM's, and displays each of them in a separate toplevel windows. Tcl/Tk was compiled with Visual C 4.0, and run on a P100 under Win95. Image load times are not included in the timings: 8-bit 16-bit 24-bit -------------------------------------------------------------------- 1. original 4.2 code 5.52 s 8.57 s 3.79 s 2. booster patch 5.49 s 1.87 s 1.82 s speedup None 4.6x 2.1x Tk is pretty nice, but Tk with decent performance is even nicer. Regards /F ==================================================================== (Sorry for the patch format; don't have a decent diff on my PC...) 1. For portability and speed, the best thing under Windows is to treat 16-bit displays as if they were 24-bit. The Windows device drivers takes care of the rest. In tkWinImage.c, change: imagePtr->bits_per_pixel = depth; to if (visual->class == TrueColor) /* true colour is stored as 3 bytes: (blue, green, red) */ imagePtr->bits_per_pixel = 24; else imagePtr->bits_per_pixel = depth; NOTE: This turned out to be quite similar to how this was done in 4.1, which worked fine (but much too slow) on 16-bit displays. There's probably some reason for the change; it is mentioned in the CHANGES file as a fix to make sure *image* depths other than 8 and 24 bits works, but I have still to find a machine where 4.2 works for *display* depths other than 8 and 24 bits... 2. The DitherInstance implementation is not good. It's especially bad on highend truecolour displays; it crawls under Windows, it crawls on my fast 64-bit workstation. IMO, it should be rewritten from scratch (stay tuned ;-)... Anyway, the following band-aid makes the situation a little bit better under Windows. This hack trades some marginal quality (no dithering on 16-bit displays) for a dramatic performance boost. Requires patch 1 to be in place. for (; height > 0; height -= nLines) { if (nLines > height) { nLines = height; } dstLinePtr = (unsigned char *) imagePtr->data; yEnd = yStart + nLines; #ifdef __WIN32__ if (colorPtr->visualInfo.class == TrueColor && instancePtr->gamma == 1.0) { /* Windows hicolor/truecolor booster */ for (y = yStart; y < yEnd; ++y) { destBytePtr = dstLinePtr; srcPtr = srcLinePtr; for (x = xStart; x < xEnd; ++x) { destBytePtr[0] = srcPtr[2]; destBytePtr[1] = srcPtr[1]; destBytePtr[2] = srcPtr[0]; destBytePtr += 3; srcPtr += 3; } srcLinePtr += lineLength; dstLinePtr += bytesPerLine; } } else #endif for (y = yStart; y < yEnd; ++y) { srcPtr = srcLinePtr; errPtr = errLinePtr; destBytePtr = dstLinePtr; ==================================================================== ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From admitted@netspace.org Fri Nov 8 03:55:23 1996 From: admitted@netspace.org (admitted) Date: Thu, 07 Nov 1996 22:55:23 -0500 Subject: [PYTHON IMAGE-SIG] Tkinter, Tk image display problems Message-ID: <3282AF2B.2DA0@netspace.org> I am trying to manipulate image files (GIFS, JPEGS, TIFFs, etc.) in Python using Tkinter and the PIL. However, the files that are displayed on the screen are not in the exact colors that they should be. When using xv on the same files, the images displayed using PIL and Tkinter are of much lower quality than those displayed by xv. I've been told that this is a problem with the way Tk interacts with X where it alters the colormap a little bit. Is this the problem? Is Sun working on a fix for it? Are there any ways I can go around this problem? Or are there file formats that Tk displays correctly? I would appreciate any help. Thanks. Tom Lukasiak admitted@netsapce.org ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From Seth_Coe@brown.edu Sat Nov 9 00:45:52 1996 From: Seth_Coe@brown.edu (Seth Coe) Date: Fri, 08 Nov 1996 19:45:52 -0500 Subject: [PYTHON IMAGE-SIG] PIL bands Message-ID: <199611090047.TAA00472@golden.brown.edu> I'm trying to separate a mode = 'RGB' image into its component bands. I've tried 'imageBands = img.split()' but I get an error: for c in self.im.bands: AttributeError: attributeless object It seems that PIL doesn't know about im.bands, though it should. Anybody know what my problem is? Thanks in advance, Seth Coe ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fredrik_lundh@ivab.se Sun Nov 10 17:10:48 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Sun, 10 Nov 1996 18:10:48 +0100 Subject: [PYTHON IMAGE-SIG] PIL bands In-Reply-To: <199611090047.TAA00472@golden.brown.edu> (Seth_Coe@brown.edu) Message-ID: <9611101710.AA23637@arnold.image.ivab.se> > I'm trying to separate a mode = 'RGB' image into its component > bands. I've tried 'imageBands = img.split()' but I get an error The split code in 0.1b1 is broken; here's a better version: def split(self): "Split image into bands" ims = [] self.load() for i in range(self.im.bands): ims.append(self._makeself(self.im.getband(i))) return tuple(ims) Regards /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From Seth_Coe@brown.edu Sun Nov 10 18:31:10 1996 From: Seth_Coe@brown.edu (Seth Coe) Date: Sun, 10 Nov 1996 13:31:10 -0500 Subject: [PYTHON IMAGE-SIG] Image.split() Message-ID: <199611101832.NAA09797@golden.brown.edu> Sorry about that folks, Fred already had that change, I should read my mail more acrefully. Seth *-) ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fredrik_lundh@ivab.se Sun Nov 10 18:35:32 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Sun, 10 Nov 1996 19:35:32 +0100 Subject: [PYTHON IMAGE-SIG] Announcing the Python Imaging Library, release 0.2b1 for Windows Message-ID: <9611101835.AA27303@arnold.image.ivab.se> Tjena allihopa, I just uploaded the Windows release of the Python Imaging Library 0.2b1 to www.python.org. It has been tested with the standard Python 1.4 distribution, as well as with PythonWin. A source distribution for Unix users and Windows hackers will be made available within short. As will updated documentation, btw... As a time-limited offer, the distribution includes DLLs for Tkinter, Tcl 7.6, and Tk 4.2, including hooks for PIL and the infamous "booster" patch. If you have a 16 or 24-bit Windows display and would like to get decent performance when you display images, please give this one a try. And no, it does *not* crash in CW3215.DLL on Windows 95 ;-) Regards /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fdrake@CNRI.Reston.Va.US Mon Nov 11 15:56:12 1996 From: fdrake@CNRI.Reston.Va.US (Fred L. Drake) Date: Mon, 11 Nov 1996 10:56:12 -0500 (EST) Subject: [PYTHON IMAGE-SIG] Plans for PNG support? Message-ID: <199611111556.KAA14176@weyr.CNRI.Reston.Va.US> Is anyone working on supporting PNG for at least "Load" capability? I see that "Open" is supported, but a web browser would really require at least "Load". If "Load" is planned for the near future, I might be convinced to spend a little time on the image handling for Grail. Tk's built-in processing is less reliable than I care for. -Fred -- Fred L. Drake, Jr. fdrake@cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive Reston, VA 20191-5434 ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From Jack.Jansen@cwi.nl Mon Nov 11 23:19:36 1996 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Tue, 12 Nov 1996 00:19:36 +0100 Subject: [PYTHON IMAGE-SIG] Plans for PNG support? In-Reply-To: Message by "Fred L. Drake" , Mon, 11 Nov 1996 10:56:12 -0500 (EST) , <199611111556.KAA14176@weyr.CNRI.Reston.Va.US> Message-ID: <9611112319.AA22500=jack@schelvis.cwi.nl> Recently, "Fred L. Drake" said: > Is anyone working on supporting PNG for at least "Load" capability? > I see that "Open" is supported, but a web browser would really require > at least "Load". > If "Load" is planned for the near future, I might be convinced to > spend a little time on the image handling for Grail. Tk's built-in > processing is less reliable than I care for. I am more-or-less committed to do PNG support for img, so with the img-to-pil bridge that would automatically give PNG support in PIL, I guess. I'm currently working on img, I'll probably do a new distribution some time this month. Nothing really special, mainly support for xbm, bmp and png. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fbowie@resumix.com Tue Nov 12 03:00:24 1996 From: fbowie@resumix.com (fbowie@resumix.com) Date: Mon, 11 Nov 1996 19:00:24 -0800 Subject: [PYTHON IMAGE-SIG] Error Question Message-ID: <199611120300.TAA00048@sonya-blade.resumix.com> Hello I just loaded you November 10th release. If I try (or any program) wants to load 'Tkinter' the following error shows up: "ImportError:dynamic module does not define init function" What should I do? Many Thanks ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fredrik_lundh@ivab.se Tue Nov 12 09:26:02 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Tue, 12 Nov 1996 10:26:02 +0100 Subject: [PYTHON IMAGE-SIG] Plans for PNG support? In-Reply-To: <199611111556.KAA14176@weyr.CNRI.Reston.Va.US> (fdrake@CNRI.Reston.Va.US) Message-ID: <9611120926.AA24181@arnold.image.ivab.se> > Is anyone working on supporting PNG for at least "Load" capability? > I see that "Open" is supported, but a web browser would really > require at least "Load". Since PNG is now a official W3O standard, I don't have much choice, do I? :-) Unfortunately, the current design of the "official" PNG libraries doesn't support incremental decoding, but a "read from file handle only" version would be rather trivial. I'll give that a try RSN. While waiting, you could use something like: im = im.open(file) if im.format == "PNG": size = im.size im = im.open("Guido@30dpi.gif").resize(size) Cheers /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From flight@mathi.uni-heidelberg.DE Tue Nov 12 11:49:13 1996 From: flight@mathi.uni-heidelberg.DE (Gregor Hoffleit) Date: Tue, 12 Nov 96 12:49:13 +0100 Subject: [PYTHON IMAGE-SIG] 0.2b1 source distribution not available ? Message-ID: <9611121149.AA18404@mathi.uni-heidelberg.DE> Hi, I found that the source for the new PIL 0.2b1 is not yet available via the PIL web page ("404 Not Found"), while the Win distribution can be downloaded. Could you perhaps check/correct this ? Thanks in advance, Gregor --- | Gregor Hoffleit Mathematisches Institut, Uni HD | | flight@mathi.uni-heidelberg.de INF 288, 69120 Heidelberg, Germany | | (NeXTmail, MIME) (49)6221 54-5771 fax 54-8312 | | PGP Key fingerprint = 23 8F B3 38 A3 39 A6 01 5B 99 91 D6 F2 AC CD C7 | ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fredrik_lundh@ivab.se Tue Nov 12 12:04:47 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Tue, 12 Nov 1996 13:04:47 +0100 Subject: [PYTHON IMAGE-SIG] 0.2b1 source distribution not available ? In-Reply-To: <9611121149.AA18404@mathi.uni-heidelberg.DE> (message from Gregor Hoffleit on Tue, 12 Nov 96 12:49:13 +0100) Message-ID: <9611121204.AA31979@arnold.image.ivab.se> > I found that the source for the new PIL 0.2b1 is not yet available via > the PIL web page ("404 Not Found"), while the Win distribution can be > downloaded. Could you perhaps check/correct this ? Forgot to remove the link; as I said in the release note, the source distribution is not yet available. Have some other Python-related activities to take care of first, but stay tuned. Sorry /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From patmiller@llnl.gov Tue Nov 12 16:54:02 1996 From: patmiller@llnl.gov (Patrick Miller) Date: Tue, 12 Nov 1996 08:54:02 -0800 Subject: [PYTHON IMAGE-SIG] Missing distribution Message-ID: <3288ABAA.59E2@llnl.gov> Tried to download PIL, but link to beta from main page (http://www.python.org/sigs/image-sig/Imaging.html) http://www.python.org/sigs/image-sig/Imaging-0.2b1.tar.gz was broken. Looked in FTP directory on ftp.python.org, but could not find it. Where can I download from? Pat -- Patrick Miller Mail || at mailto:patmiller@llnl.gov mailto:patmiller@caesoft.com WWW || http://www.caesoft.com/miller Phone || (510) 423-0309 [LLNL], (209) 833-3459, (209) 833-6099 [FAX] ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From Seth_Coe@brown.edu Tue Nov 12 19:18:14 1996 From: Seth_Coe@brown.edu (Seth Coe) Date: Tue, 12 Nov 1996 14:18:14 -0500 Subject: [PYTHON IMAGE-SIG] putpalette Message-ID: <199611121919.OAA19157@golden.brown.edu> I am trying to convert an image to an array, and then back again, and am having trouble with this when my image.mode = 'P', because I am not using the palette to translate the data. I tried to use image.convert('P',palette) , but Image.py calls self.im.dither, which does not exist. I tried to modify it to call self.im.putpalette, but this function seems to be incomplete (it returns None, for one). Anybody have any patches, or alternative solutiosn for me? Thanks, Seth Coe ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fbowie@resumix.com Tue Nov 12 21:56:17 1996 From: fbowie@resumix.com (fbowie@resumix.com) Date: Tue, 12 Nov 1996 13:56:17 -0800 Subject: FW: [PYTHON IMAGE-SIG] Error Question Message-ID: <199611122156.NAA00071@sonya-blade.resumix.com> Hello, I was using 1.4 (10/26/96) on a WIN 95 system. I assume '_tkinter.dll' is the update to 'Tkinter.py' Do I need to rename something? Tried pdb but it wasn't much help. I have set the TK and TCL env and put the other dll files where you suggested. Hmmm......... ---------- From: Fredrik Lundh[SMTP:Fredrik_Lundh@ivab.se] Sent: Tuesday, November 12, 1996 1:49 AM To: fbowie@resumix.com Subject: Re: [PYTHON IMAGE-SIG] Error Question > I just loaded you November 10th release. If I try (or any program) wants > to load 'Tkinter' the following error shows up: > > "ImportError:dynamic module does not define init function" What Python (or PythonWin) version do you have? I've tested the release with Python 1.4 myself, and others have tested it with the most recent versions of PythonWin. Don't know about older versions. /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fbowie@resumix.com Wed Nov 13 22:00:25 1996 From: fbowie@resumix.com (fbowie@resumix.com) Date: Wed, 13 Nov 1996 14:00:25 -0800 Subject: [PYTHON IMAGE-SIG] PYTHON IMAGE-SIG] Just One Error Question :) Message-ID: <199611132200.OAA00048@sonya-blade.resumix.com> Thanks for the response To get a frame of reference I got the NT version with Tkinter running on my system :). My only question now is that the PIL 0.2b1 readme mentions a 'Tkinter' with support for the ImageTK module. When you unzip the archive you find '_tkinter.dll' but none of the other files I see in my NT/Tkinter subdirectory('Tkinter.py,TKconstants.py etc.). Where should I grap the modified 'Tkinter.py' ? Thanks ---------- From: Fredrik Lundh[SMTP:Fredrik_Lundh@ivab.se] Sent: Wednesday, November 13, 1996 12:51 AM To: fbowie@resumix.com Subject: Re: FW: [PYTHON IMAGE-SIG] Error Question > I assume '_tkinter.dll' is the update to 'Tkinter.py' Nope. _tkinter is the low-level module used by Tkinter; you need to have them both in the Python path, and the Tcl/Tk DLL's in the standard path. See the README in the PIL distribution for some additional info. /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From ivantk@hotmail.com Sun Nov 17 22:20:44 1996 From: ivantk@hotmail.com (ivan tkatchev) Date: 17 Nov 1996 22:20:44 -0000 Subject: [PYTHON IMAGE-SIG] Strange Bug Message-ID: <19961117222044.4936.qmail@hotmail.com> Hello. I have noticed a strange bug in the Imaging Library. I have PIL version 0.1b1, and I have just downloaded python 1.4 PIL compiles perfectly. However, when I try to import the _imaging module I get this: >>> import _imaging python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' python: can't resolve symbol 'fgetc' Traceback (innermost last): File "", line 1, in ? ImportError: Unable to resolve symbol >>> Does anyone have any idea what causes this? I tried rebuilding python, and I have tried rebuilding PIL, and always I get the same results. I have Linux 2.0 Pentium 90, GCC 2.7.0 As I said, I just downloaded python 1.4 from their ftp site. Thanks for any help. --------------------------------------------------------- Get Your *Web-Based* Free Email at http://www.hotmail.com --------------------------------------------------------- ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fredrik_lundh@ivab.se Mon Nov 18 08:58:20 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Mon, 18 Nov 1996 09:58:20 +0100 Subject: [PYTHON IMAGE-SIG] Strange Bug In-Reply-To: <19961117222044.4936.qmail@hotmail.com> (ivantk@hotmail.com) Message-ID: <9611180858.AA28631@arnold.image.ivab.se> > >>> import _imaging > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > Traceback (innermost last): > File "", line 1, in ? > ImportError: Unable to resolve symbol Well, PIL actually contains exactly 8 calls to "fgetc", but why that function appears to be missing in your C library is more than I can tell. Here's some things you could try: 1. Check the fgetc man page to see if there's some special library you need to link with. 2. Boldly change fgetc to getc in libImaging/File.c, and see if that helps. (it could be a good idea to update to gcc 2.7.2[.1] as well) Regards /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From Nicolas.Roussel@lri.fr Mon Nov 18 10:56:56 1996 From: Nicolas.Roussel@lri.fr (Nicolas Roussel) Date: Mon, 18 Nov 1996 11:56:56 +0100 Subject: [PYTHON IMAGE-SIG] Release 0.2b1 Message-ID: <329040F7.1D7F@lri.fr> Where can I find sources ? -- ------- Nicolas ROUSSEL ------- mailto:roussel@lri.fr http://www-ihm.lri.fr/~roussel/ ------------------------------- ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From richard.jones@bom.gov.au Tue Nov 19 01:33:43 1996 From: richard.jones@bom.gov.au (Richard Jones) Date: Tue, 19 Nov 1996 01:33:43 GMT Subject: [PYTHON IMAGE-SIG] GIF animation? Message-ID: <199611190136.UAA09515@python.org> Has anyone used Python to produce GIF animations yet? I specifically need a tool that can be used in a batch environment (ie, not win95 based). If not, does anyone have any pointers to the correct method of producing GIF animations using inter-frame compression? Richard ps. if anyone knows of a non-python UNIX tool that I could use that _uses compression between frames_ then I'd greatly appreciate it (send email to me though - it is off-topic). ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From nick@osg.saic.com Tue Nov 19 03:19:10 1996 From: nick@osg.saic.com (nick) Date: Mon, 18 Nov 1996 22:19:10 -0500 (EST) Subject: [PYTHON IMAGE-SIG] Re: GIF animation? In-Reply-To: <199611190136.UAA09515@python.org> Message-ID: On Tue, 19 Nov 1996, Richard Jones wrote: > > Has anyone used Python to produce GIF animations yet? I specifically need > a tool that can be used in a batch environment (ie, not win95 based). I believe GD has python bindings, does it not? nick ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From guido@CNRI.Reston.Va.US Thu Nov 21 06:19:56 1996 From: guido@CNRI.Reston.Va.US (Guido van Rossum) Date: Thu, 21 Nov 1996 01:19:56 -0500 Subject: [PYTHON IMAGE-SIG] Strange Bug In-Reply-To: Your message of "17 Nov 1996 22:20:44 GMT." <19961117222044.4936.qmail@hotmail.com> References: <19961117222044.4936.qmail@hotmail.com> Message-ID: <199611210619.BAA08350@monty> > Hello. I have noticed a strange bug in the Imaging Library. > I have PIL version 0.1b1, and I have just downloaded python 1.4 > PIL compiles perfectly. > > However, when I try to import the _imaging module I get this: > > >>> import _imaging > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > python: can't resolve symbol 'fgetc' > Traceback (innermost last): > File "", line 1, in ? > ImportError: Unable to resolve symbol > >>> Could it be the old problem (on some systems) that symbols which aren't used in the main Python binary aren't exported to shared libraries? I don't think I use fgetc() anywhere in the core -- I always use the macro getc(). This seems strange though since I presume that you are using libc as a shared library on Linux... --Guido van Rossum (home page: http://www.python.org/~guido/) ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fbowie@resumix.com Fri Nov 22 00:13:25 1996 From: fbowie@resumix.com (Bowie, Franklin) Date: Thu, 21 Nov 1996 16:13:25 -0800 Subject: [PYTHON IMAGE-SIG] Path Stuff Message-ID: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_000_01BBD7C6.EE196A00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit (This may seem silly) Hello, I'm using Pythonwin(beta 4) and your latest (Imaging-0_2b1) on WIN95. I had to move the files and now TK /TCL will only look for the libraries from the first installation. The env. variables (TK_LIBRARY/TCL_LIBRARY) have no effect. If I try to add the new path (sys.path.insert(new locations)) it seems to be ignored. This may be more of a TCL/TK question. I think there is a varible I'm not setting someplace....??? ------ =_NextPart_000_01BBD7C6.EE196A00 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+Ih0AAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQWAAwAOAAAAzAcLABUAEAANABkABAAtAQEggAMADgAAAMwHCwAV ABAADQAZAAQALQEBCYABACEAAAA5MzJEMEZFQ0NDNDNEMDExQkZDQzAwODA1RkVBM0M4QQBpBwEN gAQAAgAAAAIAAgABBIABAAsAAABQYXRoIFN0dWZmALUDAQOQBgDkBAAAGQAAAAMAJgAAAAAAAwA2 AAAAAAADAAYQmK345wMABxBiAQAAHgAIEAEAAABlAAAAKFRISVNNQVlTRUVNU0lMTFkpSEVMTE8s SU1VU0lOR1BZVEhPTldJTihCRVRBNClBTkRZT1VSTEFURVNUKElNQUdJTkctMDJCMSlPTldJTjk1 SUhBRFRPTU9WRVRIRUZJTEVTQQAAAAADABAQAAAAAAMAERAAAAAAAgEJEAEAAAAFAgAAAQIAANIC AABMWkZ1+2gswf8ACgEPAhUCpAPkBesCgwBQEwNUAgBjaArAc2V07jIGAAbDAoMyA8YHEwKD+jMT DX0KgAjPCdkCgAqBgw2xC2BuZzEwMxQgFwsKEvIB0CAKhShUaCUEACAAwHkgEfBlbSMaUAMQbHkp CoVIZZka0G8sCoUKhUknGpAGdQCQF7AgUHl0aCMCIAPwbihiEgBhIIg0KSAAcGQgeQhhmiALYHQH kAVAKEkAwAJnHSEtMF8yYjEDHmACICBXSU45NZouHFYgEcAeoHRvGhCob3ZlIdBoIkBmAxATB5Ee gm5vB+BUSyDgL1RDTCAD8BrQIHHjGuAfAG9vayKQBbEKheEiYmxpYnIKwAiQBCD/A1IiVRHgBUAL gB9QB0AfEXJpAiAuICNwInEJ8HZ9KDB2JiEBoCLBCoUZsUsAX0xJQlJBUln/I7IqNh5gEcAiMSNA KJAN0CUFkHQoMUlmIRd0ct8aQCHhIbAhwSJxbgfRCrBDHYAZsHN5cy4ugi6zJ3EEkHQoLkIVkGMn 4/RzKR5gaQVAGmIEICHg9wqFHgAnYGcjQBYBKDMZ9e8yAQRgFgAgcGYecCNwI9D7I7AjkHEKUB9Q KAQtMRng/G5rJTgzsRnxHjAo8ilBXxyzI0Aw8gJAHSJzA3Bl0QtRY2UuOPE/OTAKhQUVIQA6EAAA AB4AcAABAAAACwAAAFBhdGggU3R1ZmYAAAIBcQABAAAAFgAAAAG72AjkdDYSddFDtxHQuT8AoCR2 v4sAAEAAOQDggZX6Cdi7AQMA8T8JBAAAAgFHAAEAAAAvAAAAYz1VUzthPSA7cD1DRVJJRElBTjts PVRISU5HLTk2MTEyMjAwMTMyNVotMTIxMAAAAgH5PwEAAABQAAAAAAAAANynQMjAQhAatLkIACsv 4YIBAAAAAAAAAC9PPUNFUklESUFOL09VPVJFU1VNSVgtQ09SUC9DTj1SRUNJUElFTlRTL0NOPUZC T1dJRQAeAPg/AQAAABAAAABCb3dpZSwgRnJhbmtsaW4AAgH7PwEAAABQAAAAAAAAANynQMjAQhAa tLkIACsv4YIBAAAAAAAAAC9PPUNFUklESUFOL09VPVJFU1VNSVgtQ09SUC9DTj1SRUNJUElFTlRT L0NOPUZCT1dJRQAeAPo/AQAAABAAAABCb3dpZSwgRnJhbmtsaW4AQAAHMOCBlfoJ2LsBQAAIMLBT 3foJ2LsBAwANNP0/AAACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgA9AAEAAAABAAAAAAAA AAsAKQAAAAAACwAjAAAAAAACAX8AAQAAAEMAAAA8Yz1VUyVhPV8lcD1DRVJJRElBTiVsPVRISU5H LTk2MTEyMjAwMTMyNVotMTIxMEB0aGluZy5yZXN1bWl4LmNvbT4AAKs/ ------ =_NextPart_000_01BBD7C6.EE196A00-- ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From MHammond@skippinet.com.au Fri Nov 22 01:52:58 1996 From: MHammond@skippinet.com.au (Mark Hammond) Date: Fri, 22 Nov 1996 11:52:58 +1000 Subject: [PYTHON IMAGE-SIG] Path Stuff Message-ID: <199611220051.LAA26935@minotaur.labyrinth.net.au> > I'm using Pythonwin(beta 4) and your latest (Imaging-0_2b1) on WIN95. > I had to move the files and now TK /TCL will only look for > the libraries from the first installation. The env. variables > (TK_LIBRARY/TCL_LIBRARY) have no effect. If If it is Python that can not locate the files, then you need to change the registry - under HKEY_LOCAL_MACHINE\Software\Python\Python Core\1.4.0\PythonPath. > I try to add the new path (sys.path.insert(new locations)) it seems to > be ignored. This may be more of a TCL/TK question. I think > there is a varible I'm not setting someplace....??? This may have something to do with the "ni" module. After using it, my sys.path changes have no affect. Possibly imaging uses ni() ? Mark. ---------------------------------------------------------------------- Mark Hammond - MHammond@skippinet.com.au Check out Python - _the_ language for the Web/CGI/Windows/MFC/Unix/etc & ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fbowie@resumix.com Fri Nov 22 03:39:53 1996 From: fbowie@resumix.com (Bowie, Franklin) Date: Thu, 21 Nov 1996 19:39:53 -0800 Subject: FW: [PYTHON IMAGE-SIG] Path Stuff Message-ID: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_000_01BBD7E3.C50F1A70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Thanks, I have learned more about registry magic. Python does recognize (sys.path) the changes in the registry but TCL/TK still looks in old path for 'init.tcl'. I keep getting 'can not find usable init.tcl'. I think I'll load the new TCL/TK combo from the sun site. ---------- From: Mark Hammond[SMTP:MHammond@skippinet.com.au] Sent: Thursday, November 21, 1996 5:52 PM To: Bowie, Franklin; image-sig@python.org Subject: Re: [PYTHON IMAGE-SIG] Path Stuff > I'm using Pythonwin(beta 4) and your latest (Imaging-0_2b1) on WIN95. > I had to move the files and now TK /TCL will only look for > the libraries from the first installation. The env. variables > (TK_LIBRARY/TCL_LIBRARY) have no effect. If If it is Python that can not locate the files, then you need to change the registry - under HKEY_LOCAL_MACHINE\Software\Python\Python Core\1.4.0\PythonPath. > I try to add the new path (sys.path.insert(new locations)) it seems to > be ignored. This may be more of a TCL/TK question. I think > there is a varible I'm not setting someplace....??? This may have something to do with the "ni" module. After using it, my sys.path changes have no affect. Possibly imaging uses ni() ? Mark. ---------------------------------------------------------------------- Mark Hammond - MHammond@skippinet.com.au Check out Python - _the_ language for the Web/CGI/Windows/MFC/Unix/etc & ------ =_NextPart_000_01BBD7E3.C50F1A70 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IjcDAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQWAAwAOAAAAzAcLABUAEwAnADUABABmAQEggAMADgAAAMwHCwAV ABMAJwA2AAQAZwEBCYABACEAAAA0MzMxMEZFQ0NDNDNEMDExQkZDQzAwODA1RkVBM0M4QQBSBwEN gAQAAgAAAAIAAgABBIABACIAAABGVzogW1BZVEhPTiBJTUFHRS1TSUddIFBhdGggU3R1ZmYA+QkB A5AGABgIAAAaAAAAAwAmAAAAAAADADYAAAAAAB4AcAABAAAAHgAAAFtQWVRIT04gSU1BR0UtU0lH XSBQYXRoIFN0dWZmAAAAAgFxAAEAAAAbAAAAAbvYDww47A8uoUPMEdC/zACAX+o8igAFhr4RAAMA LgAAAAAAAwAGEOkWAroDAAcQiwQAAB4ACBABAAAAZQAAAFRIQU5LUyxJSEFWRUxFQVJORURNT1JF QUJPVVRSRUdJU1RSWU1BR0lDUFlUSE9ORE9FU1JFQ09HTklaRShTWVNQQVRIKVRIRUNIQU5HRVNJ TlRIRVJFR0lTVFJZQlVUVENML1QAAAAAAwAQEAAAAAADABEQAQAAAAIBCRABAAAAGAUAABQFAAAS CQAATFpGdeb2qTP/AAoBDwIVAqQD5AXrAoMAUBMDVAIAY2gKwHNldO4yBgAGwwKDMgPGBxMCg7oz Ew19CoAIzwnZOxX/eDI1NQKACoENsQtgbvBnMTAzFCALChLyDAESYwBAIFQRwG5rcyYsCoUKhUkg EcB2ZaggbGUKwG4JgCAEYL0WACABoAhgBUAWAGcEACh0cnkdEGEd8GMuQCAgUHl0aAIgIFxkbweR FgAFoGcDAHqCZQqFKHN5cy4KsPkfACkgHwAcgBGxGQAHkRcLgCFDHddiHaFUQ0zwL1RLIB4QAxAD IBWQ/m8bICICBvAdACDyCoUCEAUFwCcLgGl0LnRjLGwnHrEcMGsJ4HAgVyHQAkALgGcl0GMDkW6a bwVAZguAHQB1cwGgXxygIgEmGh8AC4BrHCAn/SPzYR0AIVEKhRzgB+AjVZ8FoAbRJZADYSFDc3UD oBEAkHRlLgqLbGkx5DQ0AtFpLS6TDNAuk7kLWTE2CqADYC1wYwVAvi0xNwqHL+sMMDC2RgNhfjoy PjC2DIIF0ArAKhBIDGFtBGAoUFtTTVSIUDpNNkVAc2sFIBZwC4ASAC4sIS5hdf5dMd8y7QZgAjA0 HzUrGuBBCHBzZGF5LAewb0cccAbQBJAgMjE9UDGAOTk2IDU6NRIgzFBNOL8y7VRvOv81K/RCbwPw ZT1QM9AbAS5wTG47IgAeYWUtAJBn1EBwHvMuBbBnPw85zjh1Ymow8UEvNStSZQFHwFtQWVRIT04B HCBNQUdFLVNJnEddHtAhAQYAdHUN0N8bXAr7FCIMATC2PiohLLDPKIAnYh7kA/BuKD3AAZDcIDQh MABwHQB5CGEckGchAAeQBUAoSR5iGQAtYDBfMmIxITAfIVfwSU45NS2WTlEcQSqx/yxgBGAccSFS KDAcoAQgUDLfJ/ArkSOgI4AjYCAD8CPx/QIgbB5AJCIlk1LHIVIucP5iQ4AIgQQgLIcoMBHgBUDv C4AeEAdAUMFpRPEewBrgaxyACfB2HrB2WBEoonMHUscgkCOQX0xJQlL4QVJZVYJcRiEwHFMn8P9a gA3QMPEmgkutXrAiAFlB/wQgHuUfACEAIYAnxRWQJ7D/LXBUKD1QIVEDoFBxK2Ec8e9TsUwlIZQi PC0ocChQPdEhTCVIS0VZXEBPQyZBXPBKcENIUnBFXKhcU28BgHcKwGVncBse5GgWIAhQZ/IxLjT+ Lg3waCVLEi2WUskeIlOx3yqgKrMrYyDyIJguWWEEkJx0KCtyYYNZ8XMpITD/X+ER8D2gBCBTsFLH PcAiAPsf4B0xZFojYBEAwCLxHIDvHSNnoB1gI0ZxClAjwVoD/ym1VwodQWART+Ba4iiyTnJ3J/IR 8SdTcwNwJvALYGP7LYB3oT934EwlcWccU3cSfynSJ4BTsR9QVcFLMSFSImUDACIdEWR1HKAesUG/ AYA90U60JhA9UEwlbR5AlyC2IYddpmFeNlBvBBB/dcEeQEQSJ2IogAeRAwAo/yEweAZMJTXyLZYx OIOPhJ9/ha8xTjX6ZVE3HzgmG7ZDvSFgYyoQHZIe5WVgXyFRdl9QsRkAdUQxJZMhUlcAZWIvQ0dJ L1cDKEFDEHMvTUZDL1JVAwB4LxIAY0wlPP9M7RqhDGAV4DC1LmAbEB0AgmgCQHA6Ly93kkDvIOBE x0zvTfYmj4+Qn5Gv5UTlLwGAcC9EtJilT3F/ky9N9UwvGggwtps1FSEAAZ4QQAA5AFArtdIm2LsB AwDxPwkEAAACAUcAAQAAAC8AAABjPVVTO2E9IDtwPUNFUklESUFOO2w9VEhJTkctOTYxMTIyMDMz OTUzWi0xMzAxAAACAfk/AQAAAFAAAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAAL089Q0VS SURJQU4vT1U9UkVTVU1JWC1DT1JQL0NOPVJFQ0lQSUVOVFMvQ049RkJPV0lFAB4A+D8BAAAAEAAA AEJvd2llLCBGcmFua2xpbgACAfs/AQAAAFAAAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAA L089Q0VSSURJQU4vT1U9UkVTVU1JWC1DT1JQL0NOPVJFQ0lQSUVOVFMvQ049RkJPV0lFAB4A+j8B AAAAEAAAAEJvd2llLCBGcmFua2xpbgBAAAcwENu/YSbYuwFAAAgwIP380ibYuwEDAA00/T8AAAIB FDQBAAAAEAAAAFSUocApfxAbpYcIACsqJRceAD0AAQAAAAUAAABGVzogAAAAAAsAKQAAAAAACwAj AAAAAAACAX8AAQAAAEMAAAA8Yz1VUyVhPV8lcD1DRVJJRElBTiVsPVRISU5HLTk2MTEyMjAzMzk1 M1otMTMwMUB0aGluZy5yZXN1bWl4LmNvbT4AAPdS ------ =_NextPart_000_01BBD7E3.C50F1A70-- ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From ve6ahm@ve6ahm-1.ampr.ab.ca Wed Nov 20 19:37:10 1996 From: ve6ahm@ve6ahm-1.ampr.ab.ca (Les Davies) Date: Wed, 20 Nov 1996 12:37:10 -0700 (MST) Subject: [PYTHON IMAGE-SIG] Tkinter & callbacks, PIL Message-ID: <199611201937.MAA23070@ve6ahm-1.ampr.ab.ca> I tried to modify pilview.py to actively increase th color every second using Python1.4b3, PIL 2 (temp release), tk 4.0, and kernel 2.0.6. I added two self.after(1000, self.cmd_light) statements - one after the Pilview init and one at the end of the cmd_light statement. See the Pong demo in tkinter examples. The self.after in cmd_light always fails with self.tk_createcommand something about cannort create name. Does anyone have any ideas or any suggestions where to look? I am busy researching the problem but PIL, python, Tkinter etc are all new to me so it is a very interesting learning experience. If necessary I can send out the modified pilview.py. Les(ve6ahm@ve6ahm-1.ampr.ab.ca) ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From bnpikus@weizmann.weizmann.ac.al Thu Nov 28 22:26:18 1996 From: bnpikus@weizmann.weizmann.ac.al (Dmitri Pikus) Date: Fri, 29 Nov 1996 00:26:18 +0200 Subject: [PYTHON IMAGE-SIG] getting python Message-ID: <329E118A.5397@weizmann.weizmann.ac.al> Dear Sirs, please send me info on PYTHON AND HOW I CAN GET IT? Thanks Dimitri ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org ================= From fredrik_lundh@ivab.se Fri Nov 29 08:35:54 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Fri, 29 Nov 1996 09:35:54 +0100 Subject: [PYTHON IMAGE-SIG] getting python In-Reply-To: <329E118A.5397@weizmann.weizmann.ac.al> (message from Dmitri Pikus on Fri, 29 Nov 1996 00:26:18 +0200) Message-ID: <9611290835.AA24691@arnold.image.ivab.se> > please send me info on PYTHON > AND HOW I CAN GET IT? The official information and distribution sites are http://www.python.org and ftp://ftp.python.org. There's also two good books out there, which both include a CD-ROM with Python sources and prebuilt interpreters for most platforms: Internet Programming with Python by Aaron Watters, Guido van Rossum, and James Ahlstrom MIS Press/Henry Holt publishers ISBN: 1-55851-484-8 Programming Python by Mark Lutz O'Reilly & Associates ISBN: 1-56592-197-6 There's an official mailing list which is linked with the newsgroup comp.lang.python; if you don't have access to news, you can subscribe to the mailing list by sending mail to python-list-request@cwi.nl. (A human reads the mail, so no LISTSERV or Majordomo commands please!). Regards /F ================= IMAGE-SIG - SIG on Image Processing with Python send messages to: image-sig@python.org administrivia to: image-sig-request@python.org =================