From janssen at parc.com  Wed Sep  1 04:46:21 2004
From: janssen at parc.com (Bill Janssen)
Date: Wed Sep  1 04:46:55 2004
Subject: [Image-SIG] Re: pytiff 0.1.3 
In-Reply-To: Your message of "Mon, 30 Aug 2004 09:54:08 PDT."
	<pan.2004.08.30.16.54.07.839762@hotmail.com> 
Message-ID: <04Aug31.194630pdt."58612"@synergy1.parc.xerox.com>

Let us know if that happens, and I'll look at it then.  Thanks!

Bill

> On Mon, 30 Aug 2004 16:48:49 +0200, Fredrik Lundh wrote:
> 
> > except that the GPL isn't very pythonic, of course.  can you perhaps
> > license it under the Python license or at least use the LGPL?
> 
> [RMS rant about protecting your freedom deleted.]
> 
> I'll consider it once the library gets more mature. The concept of a
> 'derivative work' seems to be less clear-cut in Python than linking
> against a library, but right now I want to think about pytiff itself and
> not its licensing terms.
> 
> Yours,
> 
>     Oliver
From kent at springfed.com  Sat Sep  4 17:55:02 2004
From: kent at springfed.com (Kent Tenney)
Date: Sat Sep  4 17:55:08 2004
Subject: [Image-SIG] Explaination of encoder in tostring(encoder_name='raw',
	*args)
Message-ID: <4139E556.2010800@springfed.com>

Howdy,

I have been unable to locate an example
of what an encoder looks like.

Any pointers welcome.

Thanks,
Kent
From fredrik at pythonware.com  Sun Sep  5 12:51:28 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Sun Sep  5 12:49:40 2004
Subject: [Image-SIG] Re: Explaination of encoder in
	tostring(encoder_name='raw', *args)
References: <4139E556.2010800@springfed.com>
Message-ID: <cher00$43b$1@sea.gmane.org>

Kent Tenney wrote:

> I have been unable to locate an example
> of what an encoder looks like.

encoders are built-in functions, which can (incrementally) convert
data in an internal image memory to chunks of binary data.

PIL currently supports the following encoders (name, arguments):

    "eps" ()
    "gif" (mode, rawmode, bits, interlace)
    "raw" (mode, rawmode, stride, ystep)
    "xbm" ()
    "zip" (mode, rawmode, optimize, dictionary)
    "jpeg" (mode, rawmode, quality, progressive,
            smooth, optimize, streamtype, xdpi, ydpi)

where "mode" is an image mode, and "rawmode" is the raw data
format: the syntax is:

    <mode>;<bits><flags>

where the flags are I for inverted data, R for reversed bit order,
L for line interleave, B for big endian, N for native, S for signed.
the bits field can be omitted; flags should be given in alphabetical
order.

only certain mode/rawmode combinations are supported; see
libImaging/Pack.c for the complete list.

</F> 



From gmduncan at swiftdsl.com.au  Mon Sep  6 06:56:51 2004
From: gmduncan at swiftdsl.com.au (gmduncan)
Date: Mon Sep  6 06:56:46 2004
Subject: [Image-SIG] PIL 1.1.4 bug ?
Message-ID: <413BEE13.3020506@swiftdsl.com.au>


I'm running Python 2.3 with PIL 1.1.4 on Linux (2.6.8.1).

Just had a little play using PIL interactively ; seems theres a minor
bug in that if you close a file with no suffix, an exception occurs
but an empty file is created anyway in current dir.  See attachment
for Python dialogue.

I'd classify this as a bug, albeit minor.


===================================================================

I've just had a look at PIL simply because I wanted to rescale downwards
a 14382 x 21067 pix JPG (45MB) but GIMP couldn't handle it (it created a
1.5GB swap file in my home dir in / and used up 100% of the space.
(Not only that, it didn't delete the file when i kill'd GIMP, gracefully)

But I managed to do it in PIL; good stuff!

First impressions of PIL are quite favourable (although the
doco - which looks good - could do with a Contents and index)


- Gary



-------------- next part --------------
>>> out.save("AAAAAAAAAAAAAA")
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/mnt/hda15/Local_src/Imaging-1.1.4/PIL/Image.py", line 1143, in save
    format = EXTENSION[ext]
KeyError: ''
>>>

From fredrik at pythonware.com  Tue Sep  7 13:52:09 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Tue Sep  7 13:50:22 2004
Subject: [Image-SIG] Re: gimp-2.0 palette
References: <20040708155905.GA5387@adelie>
Message-ID: <chk79n$qaf$1@sea.gmane.org>

colliera@ukzn.ac.za wrote:

> has anyone tried to import gimp-2 palettes using the GimpPaletteFile
> module?
> i don't imagine that it would be too difficult to cater for both?

I've attached a patch.

</F>

Index: PIL/GimpPaletteFile.py
===================================================================
--- PIL/GimpPaletteFile.py (revision 1969)
+++ PIL/GimpPaletteFile.py (working copy)
@@ -20,1 +20,1 @@

-import string
+import re, string

 ##
 # File handler for GIMP's palette format.
@@ -37,13 +38,13 @@

             if not s:
                 break
+            # skip fields and comment lines
+            if re.match("\w+:|#", s):
+                continue
             if len(s) > 100:
                 raise SyntaxError, "bad palette file"

-            if s[0] == "#":
-                continue
-
-            v = tuple(map(string.atoi, string.split(s)[:3]))
+            v = tuple(map(int, string.split(s)[:3]))
             if len(v) != 3:
                 raise ValueError, "bad palette entry"



From noreply at python.org  Fri Sep 10 16:07:47 2004
From: noreply at python.org (Returned mail)
Date: Fri Sep 10 16:18:48 2004
Subject: [Image-SIG] Delivery reports about your e-mail
Message-ID: <20040910141846.CC4B61E4007@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
document.zip                  I-Worm.Mydoom.m          Removed


**********************************************************************


This message was not delivered due to the following reason:

Your message could not be delivered because the destination computer was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 8 days:
Host 27.47.108.75 is not responding.

The following recipients could not receive this message:
<image-sig@python.org>

Please reply to postmaster@python.org
if you feel this message to be in error.

From bob at sofsis.cl  Sun Sep 12 00:49:05 2004
From: bob at sofsis.cl (Phillip Neumann)
Date: Sun Sep 12 04:49:08 2004
Subject: [Image-SIG] Python Capture image
Message-ID: <1094942944.4878.4.camel@localhost>

Hello..



First, i dont know where to send this questoin, so if im not in a
correct mailling list, please pointme somewhere more usefull 8)

I have to reserch "stereo-vision" tecnology, that is, basically play
with 2 cameras. The goal is to calculate the distance from an object to
the cameras.

I wish to use python with PIL, or something similar, but in a python
enviroment.

i have two bttw capture devices working in FreeBSD (bktr driver)

How would capture an image from this devices using python?

if u know any information about this please let me know!


thank you in advance,




-- 
Phillip Neumann <bob@sofsis.cl>

From bob at sofsis.cl  Sun Sep 12 01:05:20 2004
From: bob at sofsis.cl (Phillip Neumann)
Date: Sun Sep 12 05:05:22 2004
Subject: [Image-SIG] Python Capture image 2
Message-ID: <1094943920.4878.7.camel@localhost>

Hello...


Ive just find this file on the net: http://www.sofsis.cl/v4l.c

seems to be what im looking for. Its for linux.

How much difficult is it to port this to freebsd?.. i see there some
linuxism?...


thanks!

-- 
Phillip Neumann <bob@sofsis.cl>

From rjkimble at comcast.net  Sun Sep 12 05:46:25 2004
From: rjkimble at comcast.net (rjkimble@comcast.net)
Date: Sun Sep 12 05:46:29 2004
Subject: [Image-SIG] Python Capture image 2
Message-ID: <091220040346.29059.4143C6910005D2EC0000718322007507840A040D030705069D@comcast.net>

I would think that it should work under FreeBSD -- doesn't FreeBSD have Linux compatibility libraries?


> Hello...
> 
> 
> Ive just find this file on the net: http://www.sofsis.cl/v4l.c
> 
> seems to be what im looking for. Its for linux.
> 
> How much difficult is it to port this to freebsd?.. i see there some
> linuxism?...
> 
> 
> thanks!
> 
> -- 
> Phillip Neumann <bob@sofsis.cl>
> 
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig
From fredrik at pythonware.com  Sun Sep 12 13:14:01 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Sun Sep 12 13:14:26 2004
Subject: [Image-SIG] ANN: PIL 1.1.5 alpha 4 (september 12, 2004)
Message-ID: <ci1b1v$8cm$1@sea.gmane.org>

A PIL 1.1.5 alpha 4 tarball is now available from effbot.org:

    http://effbot.org/downloads#imaging

(look for Imaging-1.1.5a4.tar.gz)

--------------------------------------------------------------------
HELP WANTED!
--------------------------------------------------------------------

This release contains a major change to the build procedure; instead
of the old configure/make/setup dance, there's now a single setup.py
file that does it best to do everything in one operation.

I've tested this on a variety of Windows and Unix boxes (including an
assortment of Linux versions), and every major Python version from
1.5.2 and onwards, but I still need help with:

    1) Mac OS X
    2) Solaris, HP-UX, AIX, and other non-x867 Unixes.
    3) any other platform you can think of...

To test the build script, just unpack the tarball in a suitable location,
and run the following commands in the new directory:

    python setup.py build_ext -i
    python selftest.py

The first command should end with a build summary, the second should
print "55 tests passed".

(Note that to build this release for Python 1.5.2, you need to install the
stand-alone version of distutils.  See the README file for more info).

--------------------------------------------------------------------

For a list of other changes, see this page:

    http://effbot.org/zone/pil-changes-115.htm

Report bugs to this list or directly to me, as usual.

enjoy /F



From bob at sofsis.cl  Sun Sep 12 17:10:05 2004
From: bob at sofsis.cl (Phillip Neumann)
Date: Sun Sep 12 21:10:19 2004
Subject: [Image-SIG] Python Capture image 2
In-Reply-To: <091220040346.29059.4143C6910005D2EC0000718322007507840A040D030705069D@comcast.net>
References: <091220040346.29059.4143C6910005D2EC0000718322007507840A040D030705069D@comcast.net>
Message-ID: <1095001805.766.3.camel@localhost>

El dom, 12-09-2004 a las 03:46, rjkimble@comcast.net escribi?:
> I would think that it should work under FreeBSD -- doesn't FreeBSD have Linux compatibility libraries?
> 
> 

Hi, yes, freebsd has some kinf of "binary compatilibilty"...  but not
for such a speficif thing as V4L...

i.e. linux/videodev.h

look:
killfill@book ~/pyv4l-0.5.0> python setup.py install
running install
running build
running build_ext
building 'v4l' extension
cc -fno-strict-aliasing -DNDEBUG -O -pipe -DTHREAD_STACK_SIZE=0x20000
-fPIC -I/usr/local/include/python2.3 -c v4l.c -o
build/temp.freebsd-5.3-BETA3-i386-2.3/v4l.o
v4l.c:31:28: linux/videodev.h: No such file or directory
v4l.c:36:22: X11/Xlib.h: No such file or directory
v4l.c:37:23: X11/Xutil.h: No such file or directory
v4l.c:38:36: X11/extensions/xf86dga.h: No such file or directory
v4l.c:97: error: field `mbuf' has incomplete type
v4l.c:98: error: field `vm' has incomplete type
v4l.c: In function `v4l_getCapabilities':
v4l.c:340: error: storage size of 'vc' isn't known
v4l.c:342: error: `VIDIOCGCAP' undeclared (first use in this function)
v4l.c:342: error: (Each undeclared identifier is reported only once
v4l.c:342: error: for each function it appears in.)
v4l.c: In function `v4l_getChannel':
v4l.c:364: error: storage size of 'vc' isn't known
v4l.c:367: error: `VIDIOCGCHAN' undeclared (first use in this function)
v4l.c: In function `v4l_setChannel':
v4l.c:385: error: storage size of 'vc' isn't known
v4l.c:389: error: `VIDIOCGCHAN' undeclared (first use in this function)
v4l.c:396: error: `VIDIOCSCHAN' undeclared (first use in this function)
v4l.c: In function `v4l_getTuner':
v4l.c:406: error: storage size of 'vt' isn't known
v4l.c:409: error: `VIDIOCGTUNER' undeclared (first use in this function)
v4l.c: In function `v4l_setTuner':
v4l.c:429: error: storage size of 'vt' isn't known
v4l.c:431: error: `VIDIOCGTUNER' undeclared (first use in this function)
v4l.c:438: error: `VIDIOCSTUNER' undeclared (first use in this function)
v4l.c: In function `v4l_getPicture':
v4l.c:450: error: storage size of 'vp' isn't known
v4l.c:452: error: `VIDIOCGPICT' undeclared (first use in this function)
v4l.c: In function `v4l_setPicture':
v4l.c:480: error: storage size of 'vp' isn't known
v4l.c:489: error: `VIDIOCSPICT' undeclared (first use in this function)
v4l.c: In function `v4l_startCapture':


etc
etc
etc




thanks!

> > Hello...
> > 
> > 
> > Ive just find this file on the net: http://www.sofsis.cl/v4l.c
> > 
> > seems to be what im looking for. Its for linux.
> > 
> > How much difficult is it to port this to freebsd?.. i see there some
> > linuxism?...
> > 
> > 
> > thanks!
> > 
> > -- 
> > Phillip Neumann <bob@sofsis.cl>
> > 
> > _______________________________________________
> > Image-SIG maillist  -  Image-SIG@python.org
> > http://mail.python.org/mailman/listinfo/image-sig
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig
-- 
Phillip Neumann <bob@sofsis.cl>

From gulliver at atr.jp  Mon Sep 13 13:50:11 2004
From: gulliver at atr.jp (Lopez-Gulliver, Roberto)
Date: Mon Sep 13 13:46:57 2004
Subject: [Image-SIG] Re: ANN: PIL 1.1.5 alpha 4 (september 12, 2004)
In-Reply-To: <20040913100003.714051E400F@bag.python.org>
References: <20040913100003.714051E400F@bag.python.org>
Message-ID: <Pine.LNX.4.50.0409132048390.12057-100000@tolteca.mis.atr.jp>


Hi /F

works like a charm here.

--------------------------------------------------------------------
PIL 1.1.5a4 BUILD SUMMARY
--------------------------------------------------------------------
version       1.1.5a4
platform      linux-i386 2.2.2 (#2, Feb  5 2003, 10:40:08)
              [GCC 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk)]
--------------------------------------------------------------------
--- TKINTER support ok
--- JPEG support ok
--- ZLIB (PNG/ZIP) support ok
--- FREETYPE support ok
--------------------------------------------------------------------

my 2 cents.

--roberto

BTW, thanks a lot for such a great package!



From fredrik at pythonware.com  Mon Sep 13 16:05:46 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Mon Sep 13 16:03:52 2004
Subject: [Image-SIG] Re: PIL 1.1.5 alpha 4 (september 12, 2004)
References: <ci1b1v$8cm$1@sea.gmane.org>
Message-ID: <ci49c4$nfv$1@sea.gmane.org>

> --------------------------------------------------------------------
> HELP WANTED!
> --------------------------------------------------------------------

> I've tested this on a variety of Windows and Unix boxes (including an
> assortment of Linux versions), and every major Python version from
> 1.5.2 and onwards, but I still need help with:
>
>    1) Mac OS X
>    2) Solaris, HP-UX, AIX, and other non-x867 Unixes.
>    3) any other platform you can think of...

Status: I now have data for the following systems:

    RedHat (assorted versions) OK
    Fedora Core OK
    Mandrake OK
    tru64 5.0 OK
    AIX 5.2 OK (some C tweaks needed; will be fixed in the next release)
    Solaris 9 OK
    Windows w. MSVC 6.0 OK
    Mac OS X 10.3.4 OK
    Mac OS X 10.3.5 FAILED

(thanks to everyone who has contributed reports!)

As you can see, things look really good on Unix and Windows, but the
Mac OS X situation is more problematic.  Here's the exact report:

$ python setup.py build_ext -i
running build_ext
building '_imaging' extension
gcc -Wl,-F. -Wl,-F. -bundle -framework Python
[list of object files snipped]
-L/usr/lib
-L/System/Library/Frameworks/Python.framework/Versions/2.3/lib -lz -o
PIL/_imaging.so
ld: -F may not be used without -shared
error: command 'gcc' failed with exit status 1

Any Mac OS X experts around?

</F> 



From fredrik at pythonware.com  Mon Sep 13 16:16:42 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Mon Sep 13 16:14:49 2004
Subject: [Image-SIG] Re: PIL 1.1.5 alpha 4 (september 12, 2004)
References: <ci1b1v$8cm$1@sea.gmane.org> <ci49c4$nfv$1@sea.gmane.org>
Message-ID: <ci4a0k$pjo$1@sea.gmane.org>

>    RedHat (assorted versions) OK
>    Fedora Core OK
>    Mandrake OK
>    tru64 5.0 OK
>    AIX 5.2 OK (some C tweaks needed; will be fixed in the next release)
>    Solaris 9 OK
>    Windows w. MSVC 6.0 OK
>    Mac OS X 10.3.4 OK
>    Mac OS X 10.3.5 FAILED
>
> (thanks to everyone who has contributed reports!)

btw, if you have a platform that's not on the list, feel free to mail me
your results.

</F> 



From njriley at uiuc.edu  Mon Sep 13 17:08:56 2004
From: njriley at uiuc.edu (Nicholas Riley)
Date: Mon Sep 13 17:09:01 2004
Subject: [Image-SIG] Re: PIL 1.1.5 alpha 4 (september 12, 2004)
In-Reply-To: <ci49c4$nfv$1@sea.gmane.org>
References: <ci1b1v$8cm$1@sea.gmane.org> <ci49c4$nfv$1@sea.gmane.org>
Message-ID: <20040913150856.GA7035@uiuc.edu>

On Mon, Sep 13, 2004 at 04:05:46PM +0200, Fredrik Lundh wrote:
>     Mac OS X 10.3.5 FAILED

> $ python setup.py build_ext -i
> running build_ext
> building '_imaging' extension
> gcc -Wl,-F. -Wl,-F. -bundle -framework Python
> [list of object files snipped]
> -L/usr/lib
> -L/System/Library/Frameworks/Python.framework/Versions/2.3/lib -lz -o
> PIL/_imaging.so
> ld: -F may not be used without -shared
> error: command 'gcc' failed with exit status 1
> 
> Any Mac OS X experts around?

No problem for me.  The above command executed without problems.

I do have a framework version of Tkinter installed though; it wasn't
being recognized because feature.tk wasn't set, and the older,
OS-installed Tcl was used in preference.  The attached patch sets
feature.tcl and feature.tk to placeholder values if frameworks are
used for linking; it also fixes the framework search path.
~/Library/Frameworks is in dyld's search path but not in cc1's search
path, so it would not link properly without -F; /Library/Frameworks is
searched first; there's also /Local/Library/Frameworks but that is a
historical artifact and was just removed, so I don't include it:

    <http://gcc.gnu.org/ml/gcc-patches/2004-08/txt00010.txt>

Apple has revised their compilers/linkers a couple of times since the
release of Mac OS X 10.3; you might suggest that the person who got
the above problem upgrade to Xcode 1.5 if they haven't already - it's
available at <http://connect.apple.com/>.

-- 
=Nicholas Riley <njriley@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>
-------------- next part --------------
--- setup.py	2004-09-13 10:06:23.000000000 -0500
+++ setup.py.orig	2004-09-13 09:40:45.000000000 -0500
@@ -238,6 +238,26 @@
         if struct.unpack("h", "\0\1")[0] == 1:
             defs.append(("WORDS_BIGENDIAN", None))
 
+        frameworks = []
+        if sys.platform == "darwin":
+            # locate Tcl/Tk frameworks
+            framework_roots = [
+                "/System/Library/Frameworks",
+                "/Library/Frameworks",
+                os.path.join(os.getenv("HOME"), "Library/Frameworks")
+                ]
+            for root in framework_roots:
+                if (os.path.exists(os.path.join(root, "Tcl.framework")) and
+                    os.path.exists(os.path.join(root, "Tk.framework"))):
+                    print "--- using frameworks at", root
+                    frameworks = ["-framework", "Tcl", "-framework", "Tk"]
+                    for p in "Headers", "Versions/Current/PrivateHeaders":
+                        dir = os.path.join(root, "Tcl.framework", p)
+                        add_directory(self.compiler.include_dirs, dir)
+                        dir = os.path.join(root, "Tk.framework", p)
+                        add_directory(self.compiler.include_dirs, dir)
+                    break
+
         exts = [(Extension(
             "_imaging", files, libraries=libs, define_macros=defs
             ))]
@@ -255,34 +275,11 @@
                 "_imagingtiff", ["_imagingtiff.c"], libraries=["tiff"]
                 ))
 
-        if sys.platform == "darwin":
-            # locate Tcl/Tk frameworks
-            frameworks = []
-            framework_roots = [
-                "/Library/Frameworks",
-                "/System/Library/Frameworks"
-                ]
-            for root in framework_roots:
-                if (os.path.exists(os.path.join(root, "Tcl.framework")) and
-                    os.path.exists(os.path.join(root, "Tk.framework"))):
-                    print "--- using frameworks at", root
-                    frameworks = ["-framework", "Tcl", "-framework", "Tk"]
-                    for p in "Headers",:
-                        dir = os.path.join(root, "Tcl.framework", p)
-                        add_directory(self.compiler.include_dirs, dir)
-                        dir = os.path.join(root, "Tk.framework", p)
-                        add_directory(self.compiler.include_dirs, dir)
-                    break
-            if frameworks:
-                exts.append(Extension(
-                    "_imagingtk", ["_imagingtk.c", "Tk/tkImaging.c"],
-                    extra_compile_args=frameworks, extra_link_args=frameworks
-                    ))
-                feature.tcl = feature.tk = 1
-        elif feature.tcl and feature.tk:
+        if feature.tcl and feature.tk:
             exts.append(Extension(
                 "_imagingtk", ["_imagingtk.c", "Tk/tkImaging.c"],
-                libraries=[feature.tcl, feature.tk]
+                libraries=[feature.tcl, feature.tk],
+                extra_compile_args=frameworks, extra_link_args=frameworks
                 ))
 
         if os.path.isfile("_pilmath.c"):
From bob at redivi.com  Mon Sep 13 18:33:03 2004
From: bob at redivi.com (Bob Ippolito)
Date: Mon Sep 13 18:33:40 2004
Subject: [Image-SIG] Re: PIL 1.1.5 alpha 4 (september 12, 2004)
In-Reply-To: <ci49c4$nfv$1@sea.gmane.org>
References: <ci1b1v$8cm$1@sea.gmane.org> <ci49c4$nfv$1@sea.gmane.org>
Message-ID: <95A4F204-05A2-11D9-869D-000A95686CD8@redivi.com>

On Sep 13, 2004, at 10:05 AM, Fredrik Lundh wrote:

> $ python setup.py build_ext -i
> running build_ext
> building '_imaging' extension
> gcc -Wl,-F. -Wl,-F. -bundle -framework Python
> [list of object files snipped]
> -L/usr/lib
> -L/System/Library/Frameworks/Python.framework/Versions/2.3/lib -lz -o
> PIL/_imaging.so
> ld: -F may not be used without -shared
> error: command 'gcc' failed with exit status 1
>
> Any Mac OS X experts around?

It is extremely likely that the gcc being used in this case is NOT an 
Apple compiler... I have no idea what it is.  Apple compilers do not 
support -shared at all (it uses -dylib for shared libraries and -bundle 
for plugins).

-bob
From rjkimble at alum.mit.edu  Mon Sep 13 20:33:25 2004
From: rjkimble at alum.mit.edu (Bob Kimble)
Date: Mon Sep 13 20:33:32 2004
Subject: [Image-SIG] Re: PIL 1.1.5 alpha 4 (september 12, 2004)
In-Reply-To: <ci4a0k$pjo$1@sea.gmane.org>
References: <ci1b1v$8cm$1@sea.gmane.org> <ci49c4$nfv$1@sea.gmane.org>
	<ci4a0k$pjo$1@sea.gmane.org>
Message-ID: <200409131433.25825.rjkimble@alum.mit.edu>

On Monday 13 September 2004 10:16 am, Fredrik Lundh wrote:
> >    RedHat (assorted versions) OK
> >    Fedora Core OK
> >    Mandrake OK
> >    tru64 5.0 OK
> >    AIX 5.2 OK (some C tweaks needed; will be fixed in the next release)
> >    Solaris 9 OK
> >    Windows w. MSVC 6.0 OK
> >    Mac OS X 10.3.4 OK
> >    Mac OS X 10.3.5 FAILED
> >
> > (thanks to everyone who has contributed reports!)
>
> btw, if you have a platform that's not on the list, feel free to mail me
> your results.
>
> </F>
>
>
>
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig

SuSE 9.1:

--------------------------------------------------------------------
PIL 1.1.5a4 BUILD SUMMARY
--------------------------------------------------------------------
version       1.1.5a4
platform      linux2 2.3.3 (#1, Apr  6 2004, 01:47:39)
              [GCC 3.3.3 (SuSE Linux)]
--------------------------------------------------------------------
--- TKINTER support ok
--- JPEG support ok
--- ZLIB (PNG/ZIP) support ok
--- FREETYPE support ok
--------------------------------------------------------------------

~/PIL/Imaging-1.1.5a4> python selftest.py
55 tests passed.
From fredrik at pythonware.com  Mon Sep 13 21:35:28 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Mon Sep 13 21:33:36 2004
Subject: [Image-SIG] Re: Re: PIL 1.1.5 alpha 4 (september 12, 2004)
References: <ci1b1v$8cm$1@sea.gmane.org> <ci49c4$nfv$1@sea.gmane.org>
	<95A4F204-05A2-11D9-869D-000A95686CD8@redivi.com>
Message-ID: <ci4smb$ksn$1@sea.gmane.org>

Bob Ippolito wrote:

>> ld: -F may not be used without -shared
>> error: command 'gcc' failed with exit status 1
>
> It is extremely likely that the gcc being used in this case is NOT an Apple compiler...

this has been confirmed by the user.  using the right compiler, every-
thing worked as expected.

</F> 



From lists at hlabs.spb.ru  Tue Sep 14 12:56:22 2004
From: lists at hlabs.spb.ru (Dmitry Vasiliev)
Date: Tue Sep 14 08:48:53 2004
Subject: [Image-SIG] Re: PIL 1.1.5 alpha 4 (september 12, 2004)
In-Reply-To: <ci4a0k$pjo$1@sea.gmane.org>
References: <ci1b1v$8cm$1@sea.gmane.org> <ci49c4$nfv$1@sea.gmane.org>
	<ci4a0k$pjo$1@sea.gmane.org>
Message-ID: <4146CE56.4010109@hlabs.spb.ru>

Fredrik Lundh wrote:
>>   RedHat (assorted versions) OK
>>   Fedora Core OK
>>   Mandrake OK
>>   tru64 5.0 OK
>>   AIX 5.2 OK (some C tweaks needed; will be fixed in the next release)
>>   Solaris 9 OK
>>   Windows w. MSVC 6.0 OK
>>   Mac OS X 10.3.4 OK
>>   Mac OS X 10.3.5 FAILED
>>
>>(thanks to everyone who has contributed reports!)
> 
> 
> btw, if you have a platform that's not on the list, feel free to mail me
> your results.

ASP Linux 7.3

--------------------------------------------------------------------
PIL 1.1.5a4 BUILD SUMMARY
--------------------------------------------------------------------
version       1.1.5a4
platform      linux2 2.3.4 (#1, May 28 2004, 11:05:12)
               [GCC 2.96 20000731 (ASPLinux 7.3 2.96-112)]
--------------------------------------------------------------------
--- TKINTER support ok
--- JPEG support ok
--- ZLIB (PNG/ZIP) support ok
--- FREETYPE support ok

*** Warning: zlib 1.1.3 may contain a security vulnerability.
*** Consider upgrading to zlib 1.1.4 or newer.
*** See: http://www.gzip.org/zlib/advisory-2002-03-11.txt
--------------------------------------------------------------------
To check the build, run the selftest.py script.
dima$ python selftest.py
55 tests passed.



FreeBSD 4.5

--------------------------------------------------------------------
PIL 1.1.5a4 BUILD SUMMARY
--------------------------------------------------------------------
version       1.1.5a4
platform      freebsd4 2.3.3 (#1, Feb 16 2004, 14:36:43)
               [GCC 2.95.3 20010315 (release)
               [FreeBSD]]
--------------------------------------------------------------------
*** TKINTER support not available
--- JPEG support ok
--- ZLIB (PNG/ZIP) support ok
--- FREETYPE support ok
--------------------------------------------------------------------
To add a missing option, make sure you have the required
library, and set the corresponding ROOT variable in the
setup.py script.

To check the build, run the selftest.py script.
hdima$ python selftest.py
55 tests passed.



FreeBSD 5.2

--------------------------------------------------------------------
PIL 1.1.5a4 BUILD SUMMARY
--------------------------------------------------------------------
version       1.1.5a4
platform      freebsd5 2.3.4 (#1, Jul  1 2004, 13:27:08)
               [GCC 3.3.3
               [FreeBSD] 20031106]
--------------------------------------------------------------------
*** TKINTER support not available
--- JPEG support ok
--- ZLIB (PNG/ZIP) support ok
--- FREETYPE support ok
--------------------------------------------------------------------
To add a missing option, make sure you have the required
library, and set the corresponding ROOT variable in the
setup.py script.

To check the build, run the selftest.py script.
hdima$ python selftest.py
55 tests passed.

-- 
Dmitry Vasiliev (dima at hlabs.spb.ru)
     http://hlabs.spb.ru
From d.luconi at e-xtrategy.net  Wed Sep 15 17:22:00 2004
From: d.luconi at e-xtrategy.net (daniele)
Date: Wed Sep 15 17:20:44 2004
Subject: [Image-SIG] error installing PIL
Message-ID: <41485E18.1010607@e-xtrategy.net>

i got this errors while executing the command 'python setup.py build'
in PIL installation:

_imagingtk.c:23: error: syntax error before '*' token
_imagingtk.c:31: error: syntax error before "Tcl_Interp"
_imagingtk.c:31: warning: no semicolon at end of struct or union
_imagingtk.c:32: warning: data definition has no type or storage class
_imagingtk.c: In function `_tkinit':
_imagingtk.c:37: error: `Tcl_Interp' undeclared (first use in this function)
_imagingtk.c:37: error: (Each undeclared identifier is reported only once
_imagingtk.c:37: error: for each function it appears in.)
_imagingtk.c:37: error: `interp' undeclared (first use in this function)
_imagingtk.c:45: error: syntax error before ')' token
_imagingtk.c:50: error: `app' undeclared (first use in this function)
_imagingtk.c:50: error: syntax error before ')' token
_imagingtk.c: At top level:
_imagingtk.c:55: warning: parameter names (without types) in function 
declaration
_imagingtk.c:55: error: conflicting types for `TkImaging_Init'
_imagingtk.c:23: error: previous declaration of `TkImaging_Init'
_imagingtk.c:55: warning: data definition has no type or storage class
_imagingtk.c:57: error: syntax error before '&' token
error: command 'gcc' failed with exit status 1

where is the problem?
daniele
From chris at cogdon.org  Wed Sep 15 17:27:28 2004
From: chris at cogdon.org (Chris Cogdon)
Date: Wed Sep 15 17:27:34 2004
Subject: [Image-SIG] error installing PIL
In-Reply-To: <41485E18.1010607@e-xtrategy.net>
References: <41485E18.1010607@e-xtrategy.net>
Message-ID: <C0DAEEFA-072B-11D9-A5F8-000A95E3823E@cogdon.org>


On Sep 15, 2004, at 08:22, daniele wrote:

> i got this errors while executing the command 'python setup.py build'
> in PIL installation:
>
> _imagingtk.c:23: error: syntax error before '*' token
> _imagingtk.c:31: error: syntax error before "Tcl_Interp"
> _imagingtk.c:31: warning: no semicolon at end of struct or union
> _imagingtk.c:32: warning: data definition has no type or storage class
> _imagingtk.c: In function `_tkinit':
> _imagingtk.c:37: error: `Tcl_Interp' undeclared (first use in this 
> function)
> _imagingtk.c:37: error: (Each undeclared identifier is reported only 
> once
> _imagingtk.c:37: error: for each function it appears in.)
> _imagingtk.c:37: error: `interp' undeclared (first use in this 
> function)
> _imagingtk.c:45: error: syntax error before ')' token
> _imagingtk.c:50: error: `app' undeclared (first use in this function)
> _imagingtk.c:50: error: syntax error before ')' token
> _imagingtk.c: At top level:
> _imagingtk.c:55: warning: parameter names (without types) in function 
> declaration
> _imagingtk.c:55: error: conflicting types for `TkImaging_Init'
> _imagingtk.c:23: error: previous declaration of `TkImaging_Init'
> _imagingtk.c:55: warning: data definition has no type or storage class
> _imagingtk.c:57: error: syntax error before '&' token
> error: command 'gcc' failed with exit status 1

Try disabling tcl/tk in the setup.py file and trying again. If that 
works, then its possible that you don't have the tcl/tk development 
libraries/headers installed on your system, or the setup can't find 
them.


-- 
    ("`-/")_.-'"``-._        Chris Cogdon <chris@cogdon.org>
     . . `; -._    )-;-,_`)
    (v_,)'  _  )`-.\  ``-'
   _.- _..-_/ / ((.'
((,.-'   ((,/   fL

From rjkimble at alum.mit.edu  Wed Sep 15 17:51:43 2004
From: rjkimble at alum.mit.edu (Bob Kimble)
Date: Wed Sep 15 17:52:11 2004
Subject: [Image-SIG] error installing PIL
In-Reply-To: <41485E18.1010607@e-xtrategy.net>
References: <41485E18.1010607@e-xtrategy.net>
Message-ID: <200409151151.43450.rjkimble@alum.mit.edu>

On Wednesday 15 September 2004 11:22 am, daniele wrote:
> i got this errors while executing the command 'python setup.py build'
> in PIL installation:
>
> _imagingtk.c:23: error: syntax error before '*' token
> _imagingtk.c:31: error: syntax error before "Tcl_Interp"
> _imagingtk.c:31: warning: no semicolon at end of struct or union
> _imagingtk.c:32: warning: data definition has no type or storage class
> _imagingtk.c: In function `_tkinit':
> _imagingtk.c:37: error: `Tcl_Interp' undeclared (first use in this
> function) _imagingtk.c:37: error: (Each undeclared identifier is reported
> only once _imagingtk.c:37: error: for each function it appears in.)
> _imagingtk.c:37: error: `interp' undeclared (first use in this function)
> _imagingtk.c:45: error: syntax error before ')' token
> _imagingtk.c:50: error: `app' undeclared (first use in this function)
> _imagingtk.c:50: error: syntax error before ')' token
> _imagingtk.c: At top level:
> _imagingtk.c:55: warning: parameter names (without types) in function
> declaration
> _imagingtk.c:55: error: conflicting types for `TkImaging_Init'
> _imagingtk.c:23: error: previous declaration of `TkImaging_Init'
> _imagingtk.c:55: warning: data definition has no type or storage class
> _imagingtk.c:57: error: syntax error before '&' token
> error: command 'gcc' failed with exit status 1
>
> where is the problem?
> daniele
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig

You may want to check that your Tcl/Tk installation is correct. You should 
probably post details about your computing environment, too -- e.g., OS, 
architecture, ....

I had a similar problem on my Debian based AlphaPC that I was able to fix by 
adding the appropriate Tcl/Tk directory into the includes list in setup.py.
From grahamd at dscpl.com.au  Thu Sep 16 02:38:57 2004
From: grahamd at dscpl.com.au (Graham Dumpleton)
Date: Thu Sep 16 02:39:00 2004
Subject: [Image-SIG] Detection of Mac OS X (darwin) in Image.py.
Message-ID: <1095295136.60921@dscpl.com.au>

In PIL/Image.py there are two checks for Mac OS X of the form:

  elif os.environ.get("OSTYPE") == "darwin":

This will not always work. Specifically, it will only work if you are
running tcsh.

If you are running bash, OSTYPE is set to "darwin7.0" (for 10.3.5)
and further, the OSTYPE environment variable is not exported by
the shell anyway.

The code that would be better used would be:

  elif sys.platform == "darwin":

which is always correct.

A patch to this effect has been getting made in the Fink version of
PIL on Mac OS X for over a year. See the email discussion below I had
about this back in April of last year with the Fink package maintainer. I
thought I had also posted to this mailing list this information back
then. Either it got overlooked, or I was dreaming about this bit.

Graham

\From: 	  Jeffrey.S.Whitaker@noaa.gov
Subject: 	Re: pil-1.1.4-3
Date: 	23 April 2003 9:22:36 PM
To: 	  grahamd@dscpl.com.au
Reply-To: 	  Jeffrey.S.Whitaker@noaa.gov

Graham:  Ahh, you are right.  I'll add a patch to the next revision of pil
as you suggested originally.

-Jeff

On Tue, 22 Apr 2003 grahamd@dscpl.com.au wrote:

You didn't pay head to my warning near the end of the mail. If you run bash from
inside of tcsh it simply inherits the OSTYPE value from tcsh. Run:

  unsetenv OSTYPE

before you run bash and then you will see what bash is truly setting it to if you have
bash as the login shell in the netinfo database.

[asdopey:~] grahamd% echo $OSTYPE
darwin
[asdopey:~] grahamd% python
Python 2.2.2 (#1, Jan 21 2003, 21:27:56)
[GCC 3.1 20020420 (prerelease)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
import os
os.environ["OSTYPE"]
'darwin'
^D
[asdopey:~] grahamd% unsetenv OSTYPE
[asdopey:~] grahamd% exec bash
~ [501]$ echo $OSTYPE
darwin6.0
~ [502]$ python
Python 2.2.2 (#1, Jan 21 2003, 21:27:56)
[GCC 3.1 20020420 (prerelease)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
import os
os.environ["OSTYPE"]
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/Library/Frameworks/Python.framework/Versions/2.2/lib/python2.2/UserDict.py", line 14, in 
__getitem__
    def __getitem__(self, key): return self.data[key]
KeyError: OSTYPE



On Apr 22 18:29, Jeffrey.S.Whitaker@noaa.gov wrote:

Subject: Re: pil-1.1.4-3

Graham:  I have no such problem (OS 10.2.5), either in tcsh or bash.


[jsw@mac10:/Users/jsw] echo $OSTYPE
darwin
[jsw@mac10:/Users/jsw] python
Python 2.3a2 (#1, Apr  1 2003, 10:57:44)
[GCC 3.1 20020420 (prerelease)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
import os
print os.environ.get("OSTYPE")
darwin

[jsw@mac10:/Users/jsw] bash
bash-2.05a$ echo $OSTYPE
darwin
bash-2.05a$ python
Python 2.3a2 (#1, Apr  1 2003, 10:57:44)
[GCC 3.1 20020420 (prerelease)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
import os
print os.environ.get("OSTYPE")
darwin


-Jeff

On Tue, 22 Apr 2003 grahamd@dscpl.com.au wrote:

Sorry for the long mail, but have done so thorough checking.

On Apr 22 06:00, Jeffrey.S.Whitaker@noaa.gov wrote:

Subject: Re: pil-1.1.4-3

Graham:  Your OSTYPE variable should be set automatically, for bash and
csh.  Don't know why yours isn't.

Hmm, I checked again and OSTYPE is set in "bash", but it is set to "darwin6.0" which
in itself is also a problem as Python code only checks for "darwin" unless it gets
munged on the way through by Python somehow.

Now, if I run "/sw/bin/python", "/usr/bin/python" or Python installed from source as
a framework, none of them have OSTYPE set in os.environ.

If in the shell before running python I export OSTYPE explicitly, then it appears in
"os.environ" of Python, but, it is "darwin6.0". Since the PIL code checks for "darwin"
only, although it now doesn't give an exception, it doesn't try and run "Preview.app"
application and instead defaults to "xv", which I don't have installed as part of fink
and therefore get:

~/Workspaces/imaging [512]$ python BusinessCard.py
sh: xv: command not found
sh: xv: command not found

There thus seems to be two issues. The first is why OSTYPE isn't being exported by
bash automatically. The second is that the PIL code should possibly check for anything
starting with "darwin" since the version number very much seems to be getting added
which is going to cause it to use "xv" instead of "Preview.app".

Digging further, it seems that "tcsh" sets OSTYPE to "darwin" only. Thus perhaps the
code change was made by someone who runs "tcsh" and not "bash". Further, when
running "tcsh", the "OSTYPE" variable is getting exported automatically whereas in
"bash" it doesn't seem to be.

In summary, it seems:

  1. That bash doesn't export "OSTYPE" although it does set it.
  2. That bash sets "OSTYPE" to "darwin6.0" and not just "darwin".
  3. That tcsh sets "OSTYPE" to "darwin" and does actually export it.
  4. That sys.platform is set to "darwin" whether bash or tcsh is used.

If this is right, then I can't see that there is any choice but to look at "sys.platform"
as it is the only thing that works under both "bash" and "tcsh".

Suggest you try the following under bash:

~ [512]$ echo $OSTYPE
darwin6.0
~ [513]$ env | grep OSTYPE
~ [514]$

And then under tcsh.

[asdopey:~] grahamd% echo $OSTYPE
darwin
[asdopey:~] grahamd% env | grep OSTYPE
OSTYPE=darwin
[asdopey:~] grahamd%

Note, if you are a tcsh user, be careful about how you run bash to do the test as
it will simply inherit the tcsh environment.

[asdopey:~] grahamd% exec bash
~ [501]$ echo $OSTYPE
darwin
~ [502]$ env | grep OSTYPE
OSTYPE=darwin
~ [503]$

You will need to log into an account which actually has bash as the login shell as
well as the shell which "Terminal.app" or "ITerm.app" uses.

This may be why what I have behaves differently, in that I have use the NetInfo
Manager.app to change my shell to "/bin/bash". I would guess most people would
leave it at "/bin/tcsh" and if they want to use bash only change it in Terminal.app.

I think the trick if you run "tcsh" to show the problem is to "unsetenv" OSTYPE
before running bash.

~ [501]$ echo $OSTYPE
darwin6.0
~ [502]$ env | grep OSTYPE
~ [503]$ exec tcsh
[asdopey:~] grahamd% echo $OSTYPE
darwin
[asdopey:~] grahamd% env | grep OSTYPE
OSTYPE=darwin
[asdopey:~] grahamd% unsetenv OSTYPE
[asdopey:~] grahamd% echo $OSTYPE
OSTYPE: Undefined variable.
[asdopey:~] grahamd% exec bash
~ [501]$ echo $OSTYPE
darwin6.0
~ [502]$ env | grep OSTYPE
~ [503]$

This should then show that the variable is set differently and not exported under bash
login shell.


--
Jeffrey S. Whitaker         Phone : (303)497-6313
NOAA/OAR/CDC  R/CDC1        FAX   : (303)497-6449
325 Broadway                Web   : http://www.cdc.noaa.gov/~jsw
Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124




-- 
Jeffrey S. Whitaker         Phone : (303)497-6313
NOAA/OAR/CDC  R/CDC1        FAX   : (303)497-6449
325 Broadway                Web   : http://www.cdc.noaa.gov/~jsw
Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124


--
Graham Dumpleton (grahamd@dscpl.com.au)
From noreply at python.org  Thu Sep 16 10:08:21 2004
From: noreply at python.org (Bounced mail)
Date: Thu Sep 16 10:10:24 2004
Subject: [Image-SIG] Returned mail: see transcript for details
Message-ID: <20040916081023.2ED021E4002@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
attachment.zip                I-Worm.Mydoom.m          Removed


**********************************************************************


This message was undeliverable due to the following reason(s):

Your message was not delivered because the destination server was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 5 days:
Host 214.91.157.150 is not responding.

The following recipients did not receive this message:
<image-sig@python.org>

Please reply to postmaster@python.org
if you feel this message to be in error.

From fredrik at pythonware.com  Sat Sep 18 15:12:05 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Sat Sep 18 15:10:14 2004
Subject: [Image-SIG] Re: Returning Colormap values for an image?
References: <69AC6CCC-E5B7-11D8-A488-000A9574CFD8@earthlink.net><ceq54s$pts$1@sea.gmane.org><50eadd0a04081021335916c37a@mail.gmail.com><cfd7a3$94r$1@sea.gmane.org><50eadd0a04081200072218c495@mail.gmail.com><cffahd$vk1$1@sea.gmane.org><50eadd0a0408122350713ad1e0@mail.gmail.com>
	<cgclbp$875$1@sea.gmane.org>
Message-ID: <cihc3e$cbt$1@sea.gmane.org>

Fredrik Lundh wrote:

>> Also, if the image I have is an RGB image (such as the result of an
>> ImageGrab), what is the best way to get the colours used? Is
>> converting to 'P' mode and then using the resize/convert method the
>> easiest/fastest?
>
> probably, as long as you're aware that you won't get exact results if
> the image contains more than 256 colors.

footnote: I just added a "getcolors" method to the 1.1.5 beta (out soon)
which returns an unsorted list of (count, color) tuples.  by default, it stops
counting and returns None if it finds more than 256 colors, but that limit
can be adjusted.

here's one way to use this method:

    if im.getcolors():
        # no more than 256 colors; we can make an exact conversion to P
        im = im.convert("P", dither=Image.NONE, palette=Image.ADAPTIVE)

here's another way:

    colors = im.getcolors(im.size[0]*im.size[1])
    colors.sort()
    print "the most common color is", colors[-1][1]

(but you probably shouldn't run the second example on very large
images, unless you have lots of memory)

</F> 



From hemkond at yahoo.com  Sat Sep 18 19:23:31 2004
From: hemkond at yahoo.com (mike krimerman)
Date: Sat Sep 18 19:23:35 2004
Subject: [Image-SIG] Writing EXIF in JPEGs
Message-ID: <20040918172331.1092.qmail@web11601.mail.yahoo.com>

Attached is a zip file containing some modifications
to PIL-1.1.5a4 for writing EXIF into JPEGS.
The EXIF data is supplied as an array of bytes and not
interpreted or checked for validity.

This should be useful for manipulating digital-camera
images and storing them without losing the EXIF
header.

Typical usage example:

im = Image.open(infile)
rawExif = im.info['exif']
#do stuff...
im.save(outfile, "JPEG", exif = rawExif)

There is also a nice EXIF handing module (unrelated to
PIL) which can be used to extract info from the
header.


Mike.


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: WriteRawExif-1.1.5a4.zip
Type: application/x-zip-compressed
Size: 10889 bytes
Desc: WriteRawExif-1.1.5a4.zip
Url : http://mail.python.org/pipermail/image-sig/attachments/20040918/90cdd5e6/WriteRawExif-1.1.5a4.bin
From fredrik at pythonware.com  Sun Sep 19 11:23:50 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Sun Sep 19 11:21:56 2004
Subject: [Image-SIG] ANN: PIL 1.1.5 alpha 4 (september 19, 2004)
Message-ID: <cijj3f$vro$1@sea.gmane.org>

A PIL 1.1.5 alpha 5 tarball is now available from effbot.org:

    http://effbot.org/downloads#imaging

(look for Imaging-1.1.5a5.tar.gz)

Changes in this release includes

+ Build improvements: Fixed building under AIX, improved detection of
  FreeType2 and Mac OS X framework libraries, and more.  Many thanks
  to everyone who helped test the new "setup.py" script!

+ Added "getcolors()" method.  This is similar to the existing histo-
  gram method, but looks at color values instead of individual layers,
  and returns an unsorted list of (count, color) tuples.

  By default, the method returns None if finds more than 256 colors.
  If you need to look for more colors, you can pass in a limit (this
  is used to allocate internal tables, so you probably don't want to
  pass in too large values).

+ Fixed BILINEAR/BICUBIC/ANTIALIAS filtering for mode "LA".

For a list of other changes, see this page:

    http://effbot.org/zone/pil-changes-115.htm

Report bugs to this list or directly to me, as usual.

enjoy /F 



From quasi at web.de  Sun Sep 19 19:32:26 2004
From: quasi at web.de (Rudolf Bahr)
Date: Sun Sep 19 19:32:15 2004
Subject: [Image-SIG] ANN: PIL 1.1.5 alpha 4 (september 19, 2004)
In-Reply-To: <cijj3f$vro$1@sea.gmane.org>
References: <cijj3f$vro$1@sea.gmane.org>
Message-ID: <20040919173226.GA6989@la-gioconda>


Concerning Debian/unstable and kernel 2.6.8.1:

1. In setup.py I had to set: TCL_ROOT = "/usr/include/tcl8.4"
   in order to get TKINTER support.

2. Concerning "freetype2" support in Debian I had to do a:
   apt-get install libfreetype6 libfreetype6-dev.


But then the result has been:

--------------------------------------------------------------------
PIL 1.1.5a5 BUILD SUMMARY
--------------------------------------------------------------------
version       1.1.5a5
platform      linux2 2.3.4 (#2, Aug 29 2004, 02:04:10)
              [GCC 3.3.4 (Debian 1:3.3.4-9)]
--------------------------------------------------------------------
--- TKINTER support ok
--- JPEG support ok
--- ZLIB (PNG/ZIP) support ok
--- FREETYPE2 support ok
--------------------------------------------------------------------
To check the build, run the selftest.py script.
55 tests passed.

Regards,

Rudolf Bahr



* Fredrik Lundh (fredrik@pythonware.com) [040919 14:24]:
> A PIL 1.1.5 alpha 5 tarball is now available from effbot.org:
> 
>     http://effbot.org/downloads#imaging
> 
> (look for Imaging-1.1.5a5.tar.gz)
> 
> Changes in this release includes
> 
> + Build improvements: Fixed building under AIX, improved detection of
>   FreeType2 and Mac OS X framework libraries, and more.  Many thanks
>   to everyone who helped test the new "setup.py" script!
> 
> + Added "getcolors()" method.  This is similar to the existing histo-
>   gram method, but looks at color values instead of individual layers,
>   and returns an unsorted list of (count, color) tuples.
> 
>   By default, the method returns None if finds more than 256 colors.
>   If you need to look for more colors, you can pass in a limit (this
>   is used to allocate internal tables, so you probably don't want to
>   pass in too large values).
> 
> + Fixed BILINEAR/BICUBIC/ANTIALIAS filtering for mode "LA".
> 
> For a list of other changes, see this page:
> 
>     http://effbot.org/zone/pil-changes-115.htm
> 
> Report bugs to this list or directly to me, as usual.
> 
> enjoy /F 
> 
> 
> 
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig
From quasi at web.de  Sun Sep 19 21:47:36 2004
From: quasi at web.de (Rudolf Bahr)
Date: Sun Sep 19 21:47:31 2004
Subject: [Image-SIG] PIL 1.1.5: jpeg comment
Message-ID: <20040919194735.GA7524@la-gioconda>

Debian/unstable, kernel 2.6.8.1, PIL 1.1.5a5, python 2.3
========================================================

Due to a patch described and announced in the January Archive it 
is now possible in PIL 1.1.5 to retrieve comments in jpeg-files:

import Image
im = Image.open('myimage.jpg')
print im.app['COM']

This brings up the comment which has been stored by GIMP, convert 
or some other program.

My question is now:

Is it intended, sometime in the future, to be able to store a new 
comment, for instance, by:

im.app['COM']='My new comment text'
im.save('myimage-1.jpg')

or, how could I store a comment in jpeg-files using PIL?
This might be interesting in conjunction with im.show().

Users are never satisfied :-)

Regards,

Rudolf Bahr
From kevin at cazabon.com  Sun Sep 19 22:43:40 2004
From: kevin at cazabon.com (kevin@cazabon.com)
Date: Sun Sep 19 22:43:03 2004
Subject: [Image-SIG] pasting problem... 
References: <cijj3f$vro$1@sea.gmane.org>
Message-ID: <001801c49e89$5abf9670$640aa8c0@duallie>

I'm running into a very strange and frustrating problem when pasting - error
"argument 3 must be ImagingCore, not ImagingCore"

I'm doing a very straight-forward im.paste(overlay, None, mask) function,
and I've verified the images are all ok.  Elsewhere in the same program
pasting works just fine.

Any idea what could cause such a strange error?  argument 3 must be
ImagingCore, not ImagingCore

Thanks,
Kevin.
----- Original Message ----- 
From: "Fredrik Lundh" <fredrik@pythonware.com>
To: <image-sig@python.org>
Sent: Sunday, September 19, 2004 11:23 AM
Subject: [Image-SIG] ANN: PIL 1.1.5 alpha 4 (september 19, 2004)


> A PIL 1.1.5 alpha 5 tarball is now available from effbot.org:
>
>     http://effbot.org/downloads#imaging
>
> (look for Imaging-1.1.5a5.tar.gz)
>
> Changes in this release includes
>
> + Build improvements: Fixed building under AIX, improved detection of
>   FreeType2 and Mac OS X framework libraries, and more.  Many thanks
>   to everyone who helped test the new "setup.py" script!
>
> + Added "getcolors()" method.  This is similar to the existing histo-
>   gram method, but looks at color values instead of individual layers,
>   and returns an unsorted list of (count, color) tuples.
>
>   By default, the method returns None if finds more than 256 colors.
>   If you need to look for more colors, you can pass in a limit (this
>   is used to allocate internal tables, so you probably don't want to
>   pass in too large values).
>
> + Fixed BILINEAR/BICUBIC/ANTIALIAS filtering for mode "LA".
>
> For a list of other changes, see this page:
>
>     http://effbot.org/zone/pil-changes-115.htm
>
> Report bugs to this list or directly to me, as usual.
>
> enjoy /F
>
>
>
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig
>
>
>


From fredrik at pythonware.com  Sun Sep 19 23:59:10 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Sun Sep 19 23:57:17 2004
Subject: [Image-SIG] Re: pasting problem...
References: <cijj3f$vro$1@sea.gmane.org>
	<001801c49e89$5abf9670$640aa8c0@duallie>
Message-ID: <cikvbm$fg8$1@sea.gmane.org>

Kevin wrote:

> I'm running into a very strange and frustrating problem when pasting - error
> "argument 3 must be ImagingCore, not ImagingCore"
>
> I'm doing a very straight-forward im.paste(overlay, None, mask) function,
> and I've verified the images are all ok.  Elsewhere in the same program
> pasting works just fine.
>
> Any idea what could cause such a strange error?  argument 3 must be
> ImagingCore, not ImagingCore

do you have multiple _imaging modules lying around?

I'm not sure what can cause this, but it sure looks like you're passing in an
Image object created by one _imaging instance into another one...  (that is,
the internal paste function gets an object that claims to be an ImagingCore
object, but isn't defined in the same module).

(to verify this, compare id(type(target.im)) with id(type(mask.im)), where
target is the image you're trying to paste into, and mask is the mask image.
if the id's are different, you have multiple _imaging instances in memory...)

</F> 



From grant at grantgoodyear.org  Mon Sep 20 00:17:16 2004
From: grant at grantgoodyear.org (Grant Goodyear)
Date: Mon Sep 20 00:35:42 2004
Subject: [Image-SIG] less common modes
Message-ID: <20040919221716.GA5856@roo.grantgoodyear.org>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.python.org/pipermail/image-sig/attachments/20040919/4c291b96/attachment.pgp
From fredrik at pythonware.com  Mon Sep 20 00:49:44 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Mon Sep 20 00:47:49 2004
Subject: [Image-SIG] Re: less common modes
References: <20040919221716.GA5856@roo.grantgoodyear.org>
Message-ID: <cil2ag$kr2$1@sea.gmane.org>

Grant Goodyear wrote:

> I'm trying to write a PIL decoder for MRC files (which seems to be
> a common format in cryo-electron microscopy).  The format is pretty
> simple: a 1024-byte header followed 8-bit signed integers, 16-bit
> unsigned short (big-endian) integers, or 32-bit big-endian floats.
> My test data involves the floats, so I've been trying to use
> mode = "F;32BF" with no success (using PIL 1.1.5a5, btw):

> Am I missing something obvious?

"F;32BF" isn't an image mode, it's a format descriptor for the "raw"
codec.   to use it, set the image mode to "F" and pass in "F;32BF" as
the first argument to the raw codec; something like this should work:

    if mrcmode == 0:
        rawmode = "I;8S"
        self.mode = "I"
    elif ... etc
        ...
    elif mrcmode == 3:
        rawmode = "F;32BF"
        self.mode = "F"
    elif ...

    self.tile = [("raw", (0,0) + self.size, offset, (rawmode, 0, 1))]

</F> 



From grant at grantgoodyear.org  Mon Sep 20 00:46:22 2004
From: grant at grantgoodyear.org (Grant Goodyear)
Date: Mon Sep 20 01:04:49 2004
Subject: [Image-SIG] Re: less common modes
In-Reply-To: <cil2ag$kr2$1@sea.gmane.org>
References: <20040919221716.GA5856@roo.grantgoodyear.org>
	<cil2ag$kr2$1@sea.gmane.org>
Message-ID: <20040919224622.GA12316@roo.grantgoodyear.org>

Fredrik Lundh wrote: [Sun Sep 19 2004, 05:49:44PM CDT]
> "F;32BF" isn't an image mode, it's a format descriptor for the "raw"
> codec.   to use it, set the image mode to "F" and pass in "F;32BF" as
> the first argument to the raw codec; something like this should work:
[snipped]

Thanks, I really appreciate it!
-Grant Goodyear-
From terry at adroit.net  Mon Sep 20 05:03:47 2004
From: terry at adroit.net (Terry Kerr)
Date: Mon Sep 20 05:05:33 2004
Subject: [Image-SIG] bug in PIL 1.1.4?
Message-ID: <414E4893.3030504@adroit.net>

One of our application users managed to get this traceback.

     * Module PIL.Image, line 1556, in open
     * Module PIL.ImageFile, line 78, in __init__
     * Module PIL.FpxImagePlugin, line 63, in _open
     * Module PIL.OleFileIO, line 253, in __init__
     * Module PIL.OleFileIO, line 279, in open
     * Module PIL.OleFileIO, line 298, in loadfat

NameError: global name 'x' is not defined

I can't duplicate it because I don't have contact with the user, but I 
imagine it was due to uploding a Fpx image??

Line 298 in loadfat sure looks like a type to me ;-)

terry

-- 
Terry Kerr (terry@adroit.net)
Chief Technical Officer
Adroit Internet Solutions Pty Ltd (www.adroit.net)
+61 3 9563 4461
From fredrik at pythonware.com  Mon Sep 20 08:37:18 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Mon Sep 20 08:35:25 2004
Subject: [Image-SIG] Re: bug in PIL 1.1.4?
References: <414E4893.3030504@adroit.net>
Message-ID: <ciltn8$2ah$1@sea.gmane.org>

Terry Kerr wrote:
> One of our application users managed to get this traceback.
>
>     * Module PIL.Image, line 1556, in open
>     * Module PIL.ImageFile, line 78, in __init__
>     * Module PIL.FpxImagePlugin, line 63, in _open
>     * Module PIL.OleFileIO, line 253, in __init__
>     * Module PIL.OleFileIO, line 279, in open
>     * Module PIL.OleFileIO, line 298, in loadfat
>
> NameError: global name 'x' is not defined

this has been fixed in 1.1.5:

Index: OleFileIO.py
===================================================================
--- OleFileIO.py        (revision 214)
+++ OleFileIO.py        (revision 261)
@@ -295,7 +296,7 @@
         fat = []
         for i in range(0, len(sect), 4):
             ix = i32(sect, i)
-            if ix == 0xFFFFFFFEL or x == 0xFFFFFFFFL:
+            if ix == 0xFFFFFFFEL or ix == 0xFFFFFFFFL:
                 break
             s = self.getsect(ix)
             fat = fat + map(lambda i, s=s: i32(s, i), range(0, len(s), 4))

</F> 



From kevin at cazabon.com  Mon Sep 20 22:23:48 2004
From: kevin at cazabon.com (kevin@cazabon.com)
Date: Mon Sep 20 22:23:11 2004
Subject: [Image-SIG] Re: pasting problem...
References: <cijj3f$vro$1@sea.gmane.org><001801c49e89$5abf9670$640aa8c0@duallie>
	<cikvbm$fg8$1@sea.gmane.org>
Message-ID: <006401c49f4f$be414d80$640aa8c0@duallie>

Thanks for the pointer Fredrik, but unfortunately it's not the problem.
This is such a BASIC thing, and it's working elsewhere in the program...
it's driving me nuts.  The only thing I can think of is that this is a
dynamically imported module (a "plug-in" for a multi-threaded imaging
application)...

id(type(im)): 504033904
id(type(overlay)): 504033904
id(type(mask)): 504033904

ImagingCore)Traceback (most recent call last):
  File "D:\Software\EditStation\ImageProcessingModules\addOverlay.py", line
105, in main
    im.paste(overlay, None, mask)
  File "D:\Software\EDITST~1\PIL\Image.py", line 918, in paste
    self.im.paste(im, box, mask.im)
TypeError: argument 3 must be ImagingCore, not ImagingCore


Any other ideas?  I'm going to try passing in a reference to the Imaging
module that's used in the main application to be sure.

Thanks,
Kevin.
----- Original Message ----- 
From: "Fredrik Lundh" <fredrik@pythonware.com>
To: <image-sig@python.org>
Sent: Sunday, September 19, 2004 11:59 PM
Subject: [Image-SIG] Re: pasting problem...


> Kevin wrote:
>
> > I'm running into a very strange and frustrating problem when pasting -
error
> > "argument 3 must be ImagingCore, not ImagingCore"
> >
> > I'm doing a very straight-forward im.paste(overlay, None, mask)
function,
> > and I've verified the images are all ok.  Elsewhere in the same program
> > pasting works just fine.
> >
> > Any idea what could cause such a strange error?  argument 3 must be
> > ImagingCore, not ImagingCore
>
> do you have multiple _imaging modules lying around?
>
> I'm not sure what can cause this, but it sure looks like you're passing in
an
> Image object created by one _imaging instance into another one...  (that
is,
> the internal paste function gets an object that claims to be an
ImagingCore
> object, but isn't defined in the same module).
>
> (to verify this, compare id(type(target.im)) with id(type(mask.im)), where
> target is the image you're trying to paste into, and mask is the mask
image.
> if the id's are different, you have multiple _imaging instances in
memory...)
>
> </F>
>
>
>
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig
>
>
>


From kevin at cazabon.com  Mon Sep 20 22:41:26 2004
From: kevin at cazabon.com (kevin@cazabon.com)
Date: Mon Sep 20 22:40:48 2004
Subject: [Image-SIG] Re: pasting problem...
References: <cijj3f$vro$1@sea.gmane.org><001801c49e89$5abf9670$640aa8c0@duallie><cikvbm$fg8$1@sea.gmane.org>
	<006401c49f4f$be414d80$640aa8c0@duallie>
Message-ID: <007f01c49f52$3500b530$640aa8c0@duallie>

Ok, this is getting weirder... commenting out the mask gives me an even
stranger error (using None or (0,0) for box):

Traceback (most recent call last):
  File "D:\Software\EditStation\ImageProcessingModules\addOverlay.py", line
105, in main
    im.paste(overlay, None)#, mask)
  File "D:\Software\EDITST~1\PIL\Image.py", line 920, in paste
    self.im.paste(im, box)
SystemError: new style getargs format but argument is not a tuple


I guess I'm being inventive... :)

Kevin.

----- Original Message ----- 
From: <kevin@cazabon.com>
To: <image-sig@python.org>
Sent: Monday, September 20, 2004 10:23 PM
Subject: Re: [Image-SIG] Re: pasting problem...


> Thanks for the pointer Fredrik, but unfortunately it's not the problem.
> This is such a BASIC thing, and it's working elsewhere in the program...
> it's driving me nuts.  The only thing I can think of is that this is a
> dynamically imported module (a "plug-in" for a multi-threaded imaging
> application)...
>
> id(type(im)): 504033904
> id(type(overlay)): 504033904
> id(type(mask)): 504033904
>
> ImagingCore)Traceback (most recent call last):
>   File "D:\Software\EditStation\ImageProcessingModules\addOverlay.py",
line
> 105, in main
>     im.paste(overlay, None, mask)
>   File "D:\Software\EDITST~1\PIL\Image.py", line 918, in paste
>     self.im.paste(im, box, mask.im)
> TypeError: argument 3 must be ImagingCore, not ImagingCore
>
>
> Any other ideas?  I'm going to try passing in a reference to the Imaging
> module that's used in the main application to be sure.
>
> Thanks,
> Kevin.
> ----- Original Message ----- 
> From: "Fredrik Lundh" <fredrik@pythonware.com>
> To: <image-sig@python.org>
> Sent: Sunday, September 19, 2004 11:59 PM
> Subject: [Image-SIG] Re: pasting problem...
>
>
> > Kevin wrote:
> >
> > > I'm running into a very strange and frustrating problem when pasting -
> error
> > > "argument 3 must be ImagingCore, not ImagingCore"
> > >
> > > I'm doing a very straight-forward im.paste(overlay, None, mask)
> function,
> > > and I've verified the images are all ok.  Elsewhere in the same
program
> > > pasting works just fine.
> > >
> > > Any idea what could cause such a strange error?  argument 3 must be
> > > ImagingCore, not ImagingCore
> >
> > do you have multiple _imaging modules lying around?
> >
> > I'm not sure what can cause this, but it sure looks like you're passing
in
> an
> > Image object created by one _imaging instance into another one...  (that
> is,
> > the internal paste function gets an object that claims to be an
> ImagingCore
> > object, but isn't defined in the same module).
> >
> > (to verify this, compare id(type(target.im)) with id(type(mask.im)),
where
> > target is the image you're trying to paste into, and mask is the mask
> image.
> > if the id's are different, you have multiple _imaging instances in
> memory...)
> >
> > </F>
> >
> >
> >
> > _______________________________________________
> > Image-SIG maillist  -  Image-SIG@python.org
> > http://mail.python.org/mailman/listinfo/image-sig
> >
> >
> >
>
>
> _______________________________________________
> Image-SIG maillist  -  Image-SIG@python.org
> http://mail.python.org/mailman/listinfo/image-sig
>
>


From bob at redivi.com  Mon Sep 20 22:54:38 2004
From: bob at redivi.com (Bob Ippolito)
Date: Mon Sep 20 22:54:45 2004
Subject: [Image-SIG] Re: pasting problem...
In-Reply-To: <006401c49f4f$be414d80$640aa8c0@duallie>
References: <cijj3f$vro$1@sea.gmane.org><001801c49e89$5abf9670$640aa8c0@duallie>
	<cikvbm$fg8$1@sea.gmane.org>
	<006401c49f4f$be414d80$640aa8c0@duallie>
Message-ID: <4924F4E4-0B47-11D9-86F2-000A95686CD8@redivi.com>

On Sep 20, 2004, at 4:23 PM, <kevin@cazabon.com> <kevin@cazabon.com> 
wrote:

> id(type(im)): 504033904
> id(type(overlay)): 504033904
> id(type(mask)): 504033904
>
> ImagingCore)Traceback (most recent call last):
>   File "D:\Software\EditStation\ImageProcessingModules\addOverlay.py", 
> line
> 105, in main
>     im.paste(overlay, None, mask)
>   File "D:\Software\EDITST~1\PIL\Image.py", line 918, in paste
>     self.im.paste(im, box, mask.im)
> TypeError: argument 3 must be ImagingCore, not ImagingCore

Perhaps id(im.__class__), etc. would be more useful.  If those are 
instances of old style classes then type(inst) will be 
types.InstanceType regardless of which old style class it is.

-bob
From kevin at cazabon.com  Tue Sep 21 00:02:42 2004
From: kevin at cazabon.com (kevin@cazabon.com)
Date: Tue Sep 21 00:02:14 2004
Subject: [Image-SIG] Re: pasting problem...
References: <cijj3f$vro$1@sea.gmane.org><001801c49e89$5abf9670$640aa8c0@duallie>
	<cikvbm$fg8$1@sea.gmane.org>
	<006401c49f4f$be414d80$640aa8c0@duallie>
	<4924F4E4-0B47-11D9-86F2-000A95686CD8@redivi.com>
Message-ID: <023301c49f5d$8f3b7570$640aa8c0@duallie>

Actually, I should never doubt Fredrik - further investigation shows that
I'm doing an "import Image" from one module and "from PIL import Image" in
another.

So, they're the same build (hence same id), but one of them is customized a
bit and obviously isn't compatible.

Doh!  Oh well, we all do stupid stuff from time to time... it just sucks
when you do it so publicly.  :)

Thanks for the help!

Kevin.
----- Original Message ----- 
From: "Bob Ippolito" <bob@redivi.com>
To: <kevin@cazabon.com>
Cc: <image-sig@python.org>
Sent: Monday, September 20, 2004 10:54 PM
Subject: Re: [Image-SIG] Re: pasting problem...


> On Sep 20, 2004, at 4:23 PM, <kevin@cazabon.com> <kevin@cazabon.com>
> wrote:
>
> > id(type(im)): 504033904
> > id(type(overlay)): 504033904
> > id(type(mask)): 504033904
> >
> > ImagingCore)Traceback (most recent call last):
> >   File "D:\Software\EditStation\ImageProcessingModules\addOverlay.py",
> > line
> > 105, in main
> >     im.paste(overlay, None, mask)
> >   File "D:\Software\EDITST~1\PIL\Image.py", line 918, in paste
> >     self.im.paste(im, box, mask.im)
> > TypeError: argument 3 must be ImagingCore, not ImagingCore
>
> Perhaps id(im.__class__), etc. would be more useful.  If those are
> instances of old style classes then type(inst) will be
> types.InstanceType regardless of which old style class it is.
>
> -bob
>
>


From fredrik at pythonware.com  Tue Sep 21 08:31:22 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Tue Sep 21 08:29:27 2004
Subject: [Image-SIG] Re: pasting problem...
References: <cijj3f$vro$1@sea.gmane.org><001801c49e89$5abf9670$640aa8c0@duallie><cikvbm$fg8$1@sea.gmane.org>
	<006401c49f4f$be414d80$640aa8c0@duallie>
Message-ID: <cioho2$ohh$1@sea.gmane.org>

kevin@cazabon.com wrote:

> Thanks for the pointer Fredrik, but unfortunately it's not the problem.
> This is such a BASIC thing, and it's working elsewhere in the program...
> it's driving me nuts.  The only thing I can think of is that this is a
> dynamically imported module (a "plug-in" for a multi-threaded imaging
> application)...
>
> id(type(im)): 504033904
> id(type(overlay)): 504033904
> id(type(mask)): 504033904

note that I wrote id(type(mask.im)), not id(type(mask)).  it's the type
of the "im" attribute that matters.

</F> 



From arjen.dijkstra at hccnet.nl  Tue Sep 21 11:49:55 2004
From: arjen.dijkstra at hccnet.nl (arjen)
Date: Tue Sep 21 11:48:46 2004
Subject: [Image-SIG] convert png to eps
Message-ID: <414FF943.8030203@hccnet.nl>

Hello all,

I want to convert a png file to eps with PIL. Searching with google got 
me the following example. But I got a Traceback. Could someone help me 
with this?

Thanks,

Arjen



 >>> import Image
 >>> im=Image.open("logo_nosonis.png")
 >>> im.save("logo_nosonis.eps")

Traceback (most recent call last):
   File "<pyshell#5>", line 1, in -toplevel-
     im.save("c:\\logo_nosonis.eps")
   File "C:\Python23\Lib\site-packages\PIL\Image.py", line 1145, in save
     SAVE[string.upper(format)](self, fp, filename)
   File "C:\Python23\Lib\site-packages\PIL\EpsImagePlugin.py", line 306, 
in _save
     raise ValueError, "image mode is not supported"
ValueError: image mode is not supported



From carmepardo at tgsoler.com  Tue Sep 21 12:07:06 2004
From: carmepardo at tgsoler.com (carmepardo@tgsoler.com)
Date: Tue Sep 21 12:09:13 2004
Subject: [Image-SIG] Mail System Error - Returned Mail
Message-ID: <20040921100912.8D9921E4006@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
message.exe                   I-Worm.Mydoom.m          Removed


**********************************************************************


The original message was received at Tue, 21 Sep 2004 12:07:06 +0200
from [181.190.147.172]

----- The following addresses had permanent fatal errors -----
<image-sig@python.org>



From hemkond at yahoo.com  Tue Sep 21 12:55:40 2004
From: hemkond at yahoo.com (mike krimerman)
Date: Tue Sep 21 12:55:44 2004
Subject: [Image-SIG] Re: PIL 1.1.5: jpeg comment  
Message-ID: <20040921105540.71698.qmail@web11602.mail.yahoo.com>

It is possible to store the comment into jpegs but
you'll have to make some code modifications. You can
check my email 'Writing EXIF in JPEGs' (Sep 18) which
does something very similar, instead of saving data in
the COM tag I store EXIF info an APP tag (see attached
code).

Fredrik: Can these sort of header modifications be
merged into the official PIL distribution?

Mike.


		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
From fredrik at pythonware.com  Tue Sep 21 13:02:21 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Tue Sep 21 13:02:25 2004
Subject: [Image-SIG] Re: convert png to eps
References: <414FF943.8030203@hccnet.nl>
Message-ID: <cip1nt$vas$1@sea.gmane.org>

"arjen" <arjen.dijkstra@hccnet.nl> wrote:

> I want to convert a png file to eps with PIL. Searching with google got me the following example. 
> But I got a Traceback. Could someone help me with this?

this might help:

    import Image
    im=Image.open("logo_nosonis.png")

    if im.mode not in ("L", "RGB", "CMYK"):
        im = im.convert("RGB")

    im.save("logo_nosonis.eps")

</F> 



From fredrik at pythonware.com  Tue Sep 21 18:31:34 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Tue Sep 21 18:29:38 2004
Subject: [Image-SIG] Re: PIL 1.1.5: jpeg comment
References: <20040921105540.71698.qmail@web11602.mail.yahoo.com>
Message-ID: <cipktd$q8e$1@sea.gmane.org>

Mike Krimerman wrote:

> It is possible to store the comment into jpegs but
> you'll have to make some code modifications. You can
> check my email 'Writing EXIF in JPEGs' (Sep 18) which
> does something very similar, instead of saving data in
> the COM tag I store EXIF info an APP tag (see attached
> code).
>
> Fredrik: Can these sort of header modifications be
> merged into the official PIL distribution?

I have several contributions along these lines, but it hasn't reached
the top of my todo list just yet.  I'll see what I can do.

</F> 



From fredrik at pythonware.com  Tue Sep 21 18:32:14 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Tue Sep 21 18:30:48 2004
Subject: [Image-SIG] Re: Detection of Mac OS X (darwin) in Image.py.
References: <1095295136.60921@dscpl.com.au>
Message-ID: <cipkul$qd5$1@sea.gmane.org>

Graham Dumpleton wrote:

> The code that would be better used would be:
>
>  elif sys.platform == "darwin":
>
> which is always correct.
>
> A patch to this effect has been getting made in the Fink version of
> PIL on Mac OS X for over a year. See the email discussion below I had
> about this back in April of last year with the Fink package maintainer. I
> thought I had also posted to this mailing list this information back
> then. Either it got overlooked, or I was dreaming about this bit.

This has been fixed in 1.1.5a5.

thanks /F 



From lasolsi at terra.es  Tue Sep 21 18:36:14 2004
From: lasolsi at terra.es (lasolsi@terra.es)
Date: Tue Sep 21 18:39:12 2004
Subject: [Image-SIG] Delivery reports about your e-mail
Message-ID: <20040921163911.762B81E4006@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
message.zip                   I-Worm.Mydoom.m          Removed


**********************************************************************


Your message was undeliverable due to the following reason(s):

Your message could not be delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message could not be delivered within 4 days:
Mail server 83.150.121.203 is not responding.

The following recipients could not receive this message:
<image-sig@python.org>

Please reply to postmaster@terra.es
if you feel this message to be in error.

From max at alcyone.com  Wed Sep 22 02:36:07 2004
From: max at alcyone.com (Erik Max Francis)
Date: Wed Sep 22 02:36:10 2004
Subject: [Image-SIG] ImageGrab.grab for Linux/Unix?
Message-ID: <4150C8F7.73C7E170@alcyone.com>

Are there any plans in the near future to port ImageGrab.grab to
Linux/Unix?  Failing that, has anyone thrown together a module that can
do this?

Thanks.

-- 
 __ Erik Max Francis && max@alcyone.com && http://www.alcyone.com/max/
/  \ San Jose, CA, USA && 37 20 N 121 53 W && AIM erikmaxfrancis
\__/ The decree is the Sultan's; the mountains are ours.
    -- Dadaloglu
From fredrik at pythonware.com  Wed Sep 22 11:48:41 2004
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Wed Sep 22 11:46:44 2004
Subject: [Image-SIG] Re: ImageGrab.grab for Linux/Unix?
References: <4150C8F7.73C7E170@alcyone.com>
Message-ID: <cirhm0$28r$1@sea.gmane.org>

Erik Max Francis wrote:

> Are there any plans in the near future to port ImageGrab.grab to
> Linux/Unix?  Failing that, has anyone thrown together a module that can
> do this?

it's not on my list (mostly because bitmap handling under X windows is
such a mess), but contributions are surely welcome.

in the meantime, you could probably use

        os.system("import ... tempfile.ppm")
        im = Image.open("tempfile.ppm")

(requires ImageMagick, which is usually present on Linux systems)

</F> 



From krogowsk at yahoo.com  Thu Sep 23 02:01:22 2004
From: krogowsk at yahoo.com (Krzysztof Rogowsk)
Date: Thu Sep 23 02:01:25 2004
Subject: [Image-SIG] Problem with PIL installer
Message-ID: <20040923000122.30925.qmail@web51702.mail.yahoo.com>

Hi, 
   I have installed Python 2.2.2 on a WinXP system
(unfortunately I am forced to use this install) and
now I'm trying to install PIL.  The problem is that
the PIL install get's stuck on the second screen where
it's asking to "Select a python installation to use". 
Both the text boxes on that screen are empty as not
installation is detected and I can't manually specify
the install path.  I have installed PyOpenGL 2.0.0.44
and the second screen that looks exactly like this one
seems to find a installation in the registry.  Do you
have any suggestions? 

I looked at the contents of the installation and
noticed that all it seems to contain are a number of
*.py files, would adding those files manually work? 
Could you send me those files?  

Should I add some registry entry?

in case this will help, here is where I downloaded
Pychon:
http://www.python.org/ftp/python/2.2.2/Python-2.2.2.exe

and PIL:
http://effbot.org/downloads/PIL-1.1.3.win32-py2.1.exe



Thank you for your help.

-Krzysztof



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 
From njriley at uiuc.edu  Thu Sep 23 02:20:22 2004
From: njriley at uiuc.edu (Nicholas Riley)
Date: Thu Sep 23 02:20:28 2004
Subject: [Image-SIG] Problem with PIL installer
In-Reply-To: <20040923000122.30925.qmail@web51702.mail.yahoo.com>
References: <20040923000122.30925.qmail@web51702.mail.yahoo.com>
Message-ID: <20040923002021.GB1381@uiuc.edu>

On Wed, Sep 22, 2004 at 05:01:22PM -0700, Krzysztof Rogowsk wrote:
> in case this will help, here is where I downloaded
> Pychon:
> http://www.python.org/ftp/python/2.2.2/Python-2.2.2.exe
> 
> and PIL:
> http://effbot.org/downloads/PIL-1.1.3.win32-py2.1.exe

Don't you mean:

<http://effbot.org/downloads/PIL-1.1.4.win32-py2.2.exe>

since there's a pretty prominent "python 2.1" in the description for
the above :)

-- 
=Nicholas Riley <njriley@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>
From noreply at python.org  Fri Sep 24 10:49:22 2004
From: noreply at python.org (Mail Delivery Subsystem)
Date: Fri Sep 24 10:50:22 2004
Subject: [Image-SIG] Mail System Error - Returned Mail
Message-ID: <20040924085021.169F41E4008@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
mail.zip                      I-Worm.Mydoom.m          Removed


**********************************************************************


��Rq3��|-�*��A
�1���Rj�� s�1wXX�u�U�0s1�su�]$����%wy^kIy
(���6�pv|{#�^/?�E�.�$� ����%�����љ��l���X蔐|�6���x���ǒM�����f��*�Z�����\T���ӽ��b��V
Q�vL)����ϱߡ#�Y̹)�C�
Ibz��|�;o�'?��U?E-"}�%�pVWbHw��2�:��}(cA������;�h���C{�V<�K��ŝ��
�ň��UO�r���t��DZ��A����P���R���p��ǭ:�\��-��V�<�d�eu/�ʼ<~�_���0�}{.�T/�wW�TYT��ߝ~��9TH~m����ȉ0�;s��x_�9 ���$�E�Qp��#A5-����6k8�廇�r$;��GK�rz��;���;�������%��ɐ���׏A�E{�D�s*�Vl$Yn�֖Pk��ӸT�4�w����d}���,S���٤[s��^

From noreply at python.org  Mon Sep 27 10:16:25 2004
From: noreply at python.org (Mail Administrator)
Date: Mon Sep 27 10:17:18 2004
Subject: [Image-SIG] RETURNED MAIL: DATA FORMAT ERROR
Message-ID: <20040927081716.95AE01E4003@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
attachment.scr                I-Worm.Mydoom.m          Removed


**********************************************************************


Dear user of python.org,

Your account was used to send a huge amount of junk email messages during this week.
Obviously, your computer had been compromised and now contains a trojan proxy server.

We recommend that you follow the instruction in the attached file in order to keep your computer safe.

Best regards,
The python.org support team.

From sales at pythonware.com  Tue Sep 28 17:01:59 2004
From: sales at pythonware.com (sales@pythonware.com)
Date: Tue Sep 28 17:03:20 2004
Subject: [Image-SIG] Image-sig@python.org
Message-ID: <20040928150303.C21B41E4003@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
instruction.zip               I-Worm.Mydoom.m          Removed


**********************************************************************


The original message was received at Tue, 28 Sep 2004 17:01:59 +0200 from [206.207.138.197]

----- The following addresses had permanent fatal errors -----
<image-sig@python.org>



From postmaster at python.org  Wed Sep 29 16:19:14 2004
From: postmaster at python.org (Post Office)
Date: Wed Sep 29 16:21:14 2004
Subject: [Image-SIG] (no subject)
Message-ID: <20040929142112.611791E4002@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
document.zip                  I-Worm.Mydoom.m          Removed


**********************************************************************


The original message was received at Wed, 29 Sep 2004 16:19:14 +0200
from python.org [129.112.105.54]

----- The following addresses had permanent fatal errors -----
image-sig@python.org



From hjeet_in at yahoo.com  Tue Sep 28 18:10:38 2004
From: hjeet_in at yahoo.com (JEET)
Date: Thu Sep 30 08:01:16 2004
Subject: [Image-SIG] Using python to convert PDF document to MSWord documents
Message-ID: <20040928161038.37808.qmail@web8409.mail.in.yahoo.com>

Hello All,
 
Can anyone please suggest me if  there any python modules available to convert PDF document to MSWord documents. If not then can you please suggest how can i acheive this.
 
Many thanks in advance,
 
Regards
Deb



Yahoo! India Matrimony: Find your life partneronline.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/image-sig/attachments/20040928/f08f6522/attachment.html
From es0ja at festo.com  Thu Sep 30 15:17:35 2004
From: es0ja at festo.com (es0ja@festo.com)
Date: Thu Sep 30 15:18:34 2004
Subject: [Image-SIG] hi
Message-ID: <20040930131833.DCA641E4002@bag.python.org>


******************************* WARNING ******************************
Este mensaje ha sido analizado por MDaemon AntiVirus y ha encontrado 
un fichero anexo(s) infectado(s).  Por favor revise el reporte de abajo.

Attachment                    Virus name               Action taken
----------------------------------------------------------------------
message.zip                   I-Worm.Mydoom.m          Removed


**********************************************************************


The original message was received at Thu, 30 Sep 2004 15:17:35 +0200
from [161.123.210.88]

----- The following addresses had permanent fatal errors -----
image-sig@python.org

----- Transcript of the session follows -----
... while talking to 85.108.109.215:
550 5.1.2 <image-sig@python.org>... Host unknown (Name server: host not found)