Hi Markus
Parts of PIL should work with IronPython if you're willing to import
ironclad first ( http://code.google.com/p/ironclad ). If you're still
using ipy 2, the latest binary release should work for you.
(If you're using 2.6, it definitely won't work right now, because ipy
2.6 can't parse PIL.Image)
Incidentally, the reason I specify 'parts of' PIL is that it doesn't
come with tests. I do have a few homebrew test cases that check for
identical output when cpy and ipy do the same things -- and they do work
-- but I can't claim any serious coverage.
If you try Ironclad, please let me know how it works for you.
Cheers
William
Markus Törnqvist wrote:
Hi!
Clearly PIL doesn't exist for IronPython, right?
I figured I'd debug the weird 404 behaviour with the debug server, but
bumped into PIL not existing.
I'm very surprised NWSGI/IIS allows the program to even start, as it
doesn't start with runserver :/
Maybe this is related to the 404s in some very roundabout way?
Anyway, to the point:
My application uses ImageFields in the code, so although I exchanged
all my own PIL stuff for System.Drawing stuff through clr, I'm still
using ImageField. Which clearly does not work.
Does anyone know if there exists a clr/ironpython ImageField implementation
that doesn't use PIL? A quick Google didn't turn up anything...
Thanks!
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
