2019-07-06 23:40:53 +03:00
|
|
|
from PIL import Image, WmfImagePlugin
|
2017-09-01 13:36:51 +03:00
|
|
|
|
2019-07-06 23:40:53 +03:00
|
|
|
from .helper import PillowTestCase, hopper
|
2016-11-27 19:03:51 +03:00
|
|
|
|
2017-04-20 14:14:23 +03:00
|
|
|
|
2016-11-27 19:03:51 +03:00
|
|
|
class TestFileWmf(PillowTestCase):
|
|
|
|
|
def test_load_raw(self):
|
|
|
|
|
|
|
|
|
|
# Test basic EMF open and rendering
|
Improve handling of file resources
Follow Python's file object semantics. User code is responsible for
closing resources (usually through a context manager) in a deterministic
way.
To achieve this, remove __del__ functions. These functions used to
closed open file handlers in an attempt to silence Python
ResourceWarnings. However, using __del__ has the following drawbacks:
- __del__ isn't called until the object's reference count reaches 0.
Therefore, resource handlers remain open or in use longer than
necessary.
- The __del__ method isn't guaranteed to execute on system exit. See the
Python documentation:
https://docs.python.org/3/reference/datamodel.html#object.__del__
> It is not guaranteed that __del__() methods are called for objects
> that still exist when the interpreter exits.
- Exceptions that occur inside __del__ are ignored instead of raised.
This has the potential of hiding bugs. This is also in the Python
documentation:
> Warning: Due to the precarious circumstances under which __del__()
> methods are invoked, exceptions that occur during their execution
> are ignored, and a warning is printed to sys.stderr instead.
Instead, always close resource handlers when they are no longer in use.
This will close the file handler at a specified point in the user's code
and not wait until the interpreter chooses to. It is always guaranteed
to run. And, if an exception occurs while closing the file handler, the
bug will not be ignored.
Now, when code receives a ResourceWarning, it will highlight an area
that is mishandling resources. It should not simply be silenced, but
fixed by closing resources with a context manager.
All warnings that were emitted during tests have been cleaned up. To
enable warnings, I passed the `-Wa` CLI option to Python. This exposed
some mishandling of resources in ImageFile.__init__() and
SpiderImagePlugin.loadImageSeries(), they too were fixed.
2019-05-25 19:30:58 +03:00
|
|
|
with Image.open("Tests/images/drawing.emf") as im:
|
|
|
|
|
if hasattr(Image.core, "drawwmf"):
|
|
|
|
|
# Currently, support for WMF/EMF is Windows-only
|
|
|
|
|
im.load()
|
|
|
|
|
# Compare to reference rendering
|
|
|
|
|
imref = Image.open("Tests/images/drawing_emf_ref.png")
|
|
|
|
|
imref.load()
|
|
|
|
|
self.assert_image_similar(im, imref, 0)
|
2016-11-27 19:03:51 +03:00
|
|
|
|
|
|
|
|
# Test basic WMF open and rendering
|
Improve handling of file resources
Follow Python's file object semantics. User code is responsible for
closing resources (usually through a context manager) in a deterministic
way.
To achieve this, remove __del__ functions. These functions used to
closed open file handlers in an attempt to silence Python
ResourceWarnings. However, using __del__ has the following drawbacks:
- __del__ isn't called until the object's reference count reaches 0.
Therefore, resource handlers remain open or in use longer than
necessary.
- The __del__ method isn't guaranteed to execute on system exit. See the
Python documentation:
https://docs.python.org/3/reference/datamodel.html#object.__del__
> It is not guaranteed that __del__() methods are called for objects
> that still exist when the interpreter exits.
- Exceptions that occur inside __del__ are ignored instead of raised.
This has the potential of hiding bugs. This is also in the Python
documentation:
> Warning: Due to the precarious circumstances under which __del__()
> methods are invoked, exceptions that occur during their execution
> are ignored, and a warning is printed to sys.stderr instead.
Instead, always close resource handlers when they are no longer in use.
This will close the file handler at a specified point in the user's code
and not wait until the interpreter chooses to. It is always guaranteed
to run. And, if an exception occurs while closing the file handler, the
bug will not be ignored.
Now, when code receives a ResourceWarning, it will highlight an area
that is mishandling resources. It should not simply be silenced, but
fixed by closing resources with a context manager.
All warnings that were emitted during tests have been cleaned up. To
enable warnings, I passed the `-Wa` CLI option to Python. This exposed
some mishandling of resources in ImageFile.__init__() and
SpiderImagePlugin.loadImageSeries(), they too were fixed.
2019-05-25 19:30:58 +03:00
|
|
|
with Image.open("Tests/images/drawing.wmf") as im:
|
|
|
|
|
if hasattr(Image.core, "drawwmf"):
|
|
|
|
|
# Currently, support for WMF/EMF is Windows-only
|
|
|
|
|
im.load()
|
|
|
|
|
# Compare to reference rendering
|
|
|
|
|
imref = Image.open("Tests/images/drawing_wmf_ref.png")
|
|
|
|
|
imref.load()
|
|
|
|
|
self.assert_image_similar(im, imref, 2.0)
|
2016-11-27 19:03:51 +03:00
|
|
|
|
2017-09-01 13:36:51 +03:00
|
|
|
def test_register_handler(self):
|
|
|
|
|
class TestHandler:
|
|
|
|
|
methodCalled = False
|
|
|
|
|
|
|
|
|
|
def save(self, im, fp, filename):
|
|
|
|
|
self.methodCalled = True
|
2019-06-13 18:54:11 +03:00
|
|
|
|
2017-09-01 13:36:51 +03:00
|
|
|
handler = TestHandler()
|
|
|
|
|
WmfImagePlugin.register_handler(handler)
|
|
|
|
|
|
|
|
|
|
im = hopper()
|
|
|
|
|
tmpfile = self.tempfile("temp.wmf")
|
|
|
|
|
im.save(tmpfile)
|
|
|
|
|
self.assertTrue(handler.methodCalled)
|
|
|
|
|
|
|
|
|
|
# Restore the state before this test
|
|
|
|
|
WmfImagePlugin.register_handler(None)
|
|
|
|
|
|
2019-03-30 07:03:57 +03:00
|
|
|
def test_load_dpi_rounding(self):
|
|
|
|
|
# Round up
|
Improve handling of file resources
Follow Python's file object semantics. User code is responsible for
closing resources (usually through a context manager) in a deterministic
way.
To achieve this, remove __del__ functions. These functions used to
closed open file handlers in an attempt to silence Python
ResourceWarnings. However, using __del__ has the following drawbacks:
- __del__ isn't called until the object's reference count reaches 0.
Therefore, resource handlers remain open or in use longer than
necessary.
- The __del__ method isn't guaranteed to execute on system exit. See the
Python documentation:
https://docs.python.org/3/reference/datamodel.html#object.__del__
> It is not guaranteed that __del__() methods are called for objects
> that still exist when the interpreter exits.
- Exceptions that occur inside __del__ are ignored instead of raised.
This has the potential of hiding bugs. This is also in the Python
documentation:
> Warning: Due to the precarious circumstances under which __del__()
> methods are invoked, exceptions that occur during their execution
> are ignored, and a warning is printed to sys.stderr instead.
Instead, always close resource handlers when they are no longer in use.
This will close the file handler at a specified point in the user's code
and not wait until the interpreter chooses to. It is always guaranteed
to run. And, if an exception occurs while closing the file handler, the
bug will not be ignored.
Now, when code receives a ResourceWarning, it will highlight an area
that is mishandling resources. It should not simply be silenced, but
fixed by closing resources with a context manager.
All warnings that were emitted during tests have been cleaned up. To
enable warnings, I passed the `-Wa` CLI option to Python. This exposed
some mishandling of resources in ImageFile.__init__() and
SpiderImagePlugin.loadImageSeries(), they too were fixed.
2019-05-25 19:30:58 +03:00
|
|
|
with Image.open("Tests/images/drawing.emf") as im:
|
|
|
|
|
self.assertEqual(im.info["dpi"], 1424)
|
2019-03-30 07:03:57 +03:00
|
|
|
|
|
|
|
|
# Round down
|
Improve handling of file resources
Follow Python's file object semantics. User code is responsible for
closing resources (usually through a context manager) in a deterministic
way.
To achieve this, remove __del__ functions. These functions used to
closed open file handlers in an attempt to silence Python
ResourceWarnings. However, using __del__ has the following drawbacks:
- __del__ isn't called until the object's reference count reaches 0.
Therefore, resource handlers remain open or in use longer than
necessary.
- The __del__ method isn't guaranteed to execute on system exit. See the
Python documentation:
https://docs.python.org/3/reference/datamodel.html#object.__del__
> It is not guaranteed that __del__() methods are called for objects
> that still exist when the interpreter exits.
- Exceptions that occur inside __del__ are ignored instead of raised.
This has the potential of hiding bugs. This is also in the Python
documentation:
> Warning: Due to the precarious circumstances under which __del__()
> methods are invoked, exceptions that occur during their execution
> are ignored, and a warning is printed to sys.stderr instead.
Instead, always close resource handlers when they are no longer in use.
This will close the file handler at a specified point in the user's code
and not wait until the interpreter chooses to. It is always guaranteed
to run. And, if an exception occurs while closing the file handler, the
bug will not be ignored.
Now, when code receives a ResourceWarning, it will highlight an area
that is mishandling resources. It should not simply be silenced, but
fixed by closing resources with a context manager.
All warnings that were emitted during tests have been cleaned up. To
enable warnings, I passed the `-Wa` CLI option to Python. This exposed
some mishandling of resources in ImageFile.__init__() and
SpiderImagePlugin.loadImageSeries(), they too were fixed.
2019-05-25 19:30:58 +03:00
|
|
|
with Image.open("Tests/images/drawing_roundDown.emf") as im:
|
|
|
|
|
self.assertEqual(im.info["dpi"], 1426)
|
2019-03-30 07:03:57 +03:00
|
|
|
|
2017-03-01 12:20:18 +03:00
|
|
|
def test_save(self):
|
|
|
|
|
im = hopper()
|
|
|
|
|
|
|
|
|
|
for ext in [".wmf", ".emf"]:
|
2019-06-13 18:54:11 +03:00
|
|
|
tmpfile = self.tempfile("temp" + ext)
|
2017-09-01 14:05:40 +03:00
|
|
|
self.assertRaises(IOError, im.save, tmpfile)
|
