[EMAIL PROTECTED] wrote:
> oops. lost my train of thought. I was gonna say, I wonder if some of
> these image manipulation routines are using multiple threads?
PIL doesn't use threading by itself, and I know of quite a few PIL-based
systems running on multi-processor hardware (not to mention mul
oops. lost my train of thought. I was gonna say, I wonder if some of
these image manipulation routines are using multiple threads?
--
http://mail.python.org/mailman/listinfo/python-list
I wonder if there are other threads accessing image? Maybe image isn't
fully initialized by some other thread before this code accesses it?
It's hard to say what's going wrong. I don't believe that an SMP system
would have any bearing on an application unless it uses multiple
threads of execution.
OK, this is the code:
"""
image is the object instance of Image class which contains all
informations
"""
pil = Image.open( os.path.join( image.path,image.name ) )
if image.rotation_angle != 2:
try:
pil = pil.rotate( rotation_lev
> If this application work on a PC mono-processor, I don't have any
>problems.
>If this application work instead on a PC bi-processor, the process
>elaborates an image "corrupted":
Sounds like you've got some thread synch issue. On a mono-processor
system, your threads are running serially, but on
Hi guys,
I've a problem, but very big!
So, i have a python/PIL application that manipulate images ( rotate,
crop, save, etc etc ).
If this application work on a PC mono-processor, I don't have any
problems.
If this application work instead on a PC bi-processor, the process
elaborates an image "cor
