Andreas,
Yes, I can see the value behind issuing an error but the user would
also run into an import error when they tried to do anything further
requiring:
>>> import cairo
which would result in an ImportError exception. So I figured Mapnik
just shouldn't crash and pycairo availability
* Dane Springmeyer (dane.springme...@gmail.com) [090727 16:53]:
> It looks like this change against Mapnik trunk solves the issue:
>
>
> Index: bindings/python/python_cairo.cpp
> ===
> --- bindings/python/python_cairo.cpp(revision
It looks like this change against Mapnik trunk solves the issue:
Index: bindings/python/python_cairo.cpp
===
--- bindings/python/python_cairo.cpp(revision 1277)
+++ bindings/python/python_cairo.cpp(working copy)
@@ -57,6 +57
It looks like this change against Mapnik trunk solves the issue:
Index: bindings/python/python_cairo.cpp
===
--- bindings/python/python_cairo.cpp(revision 1277)
+++ bindings/python/python_cairo.cpp(working copy)
@@ -57,6 +57
Andreas,
Nice job hunting this down. I'd been seeing it as well upstream (http://trac.mapnik.org/ticket/392
) but had not taken the time to debug.
I agree that #2 is critical - that we avoid crashes if pycairo python
module is unavailable at import time even if mapnik was compiled with
pyc
Package: python-mapnik
Version: 0.6.0-1
Severity: serious
Tags: patch
Hi,
after installation of python-mapnik I tried to generate images, but I
got segmentation faults.
After some debugging (thanks, Steve) we found that the culprit is that
Pycairo_CAPI is null. This should be set by Pycairo_IMPO
6 matches
Mail list logo
