On Thu, Oct 25, 2012 at 10:31 AM, Brian Crowell br...@fluggo.com wrote:
The test runner *looks* like it includes support for this module:
http://pypi.python.org/pypi/coverage
I got it working this morning. The results are quite awesome, but
could use some tweaking.
To get it working, I had
On Mon, Oct 29, 2012 at 2:11 PM, Mikhail Korobov kmik...@gmail.com wrote:
1) Test running doesn't work for me.
python Tests/run.py
...
ImportError: No module named __future__
It would be an awfully odd version of Python that didn't recognize a
__future__ import. What version of Python is
On Sun, Oct 21, 2012 at 1:28 PM, Steven Buroff sbur...@optonline.net wrote:
Is there a version of PIL that will run with python 3.3? If not, are there
plans to support 3.3 and, if so, is there any release schedule? Thanks very
much.
We're working on creating a version that works with Python
On Wed, Oct 24, 2012 at 8:34 PM, Christoph Gohlke cgoh...@uci.edu wrote:
FWIW, those are the official PIL tests from
https://bitbucket.org/effbot/pil-2009-raclette/ adjusted to Python 3.
Hello! I had just assumed that Pillow included raclette, or that you
had worked straight off PIL 1.1.7, and
On Wed, Oct 24, 2012 at 8:37 PM, Alex Clark acl...@aclark.net wrote:
Can we run a coverage report? IIRC nose makes that easier, but I don't
recall if anyone's added it to Pillow yet.
The test runner *looks* like it includes support for this module:
http://pypi.python.org/pypi/coverage
You
On Sun, Oct 21, 2012 at 3:54 PM, Alex Clark acl...@aclark.net wrote:
You rock! I'm planning to do another PIllow release this month and will try
to find some time to test this.
The more I look at it, the more areas I'm seeing that Gohlke's tests
don't cover. There are a lot of image plugins
I'm trying to iron out some of the strict-aliasing warnings that come
up when building the code under Python 3. (Strict aliasing is a C rule
against using the same pointer as two different types, which, when
followed, gives the optimizer a huge advantage. This didn't come up
under Python 2,
On Sat, Oct 13, 2012 at 10:56 PM, Brian Crowell br...@fluggo.com wrote:
union {
void *ptr;
int val;
} uresult, uvalp = { *valp }, unewval = { newval };
...and just after I send that, it occurs to me that the code could
just be trying to store an int in the space
On Wed, Oct 10, 2012 at 8:07 PM, Alex Clark acl...@aclark.net wrote:
No. But maybe a single Python 3 support ticket in the relevant branch
(https://bitbucket.org/effbot/pil-2009-raclette). IIUC, PIL has some Python
support added. One possible scenario is that we take that code and release
it.
Hi. I'm interested in helping bring PIL to Python 3.
I contacted Matthias Klose, the package maintainer for PIL, to see
which codebase he thought would be best to do that on, and he pointed
me to Pillow, so I'm here to ask about what's been done so far for
Python 3 support and what I could do.
I
On Mon, Oct 8, 2012 at 6:56 PM, Hajime Nakagami nakag...@gmail.com wrote:
That's most import bug(?) is only support Python2.7 and Python3.3
If you need widely version support, Probabry use 2to3 approach.
Yes, that seems to me to be the main trouble. Anything done to the
Python source will
11 matches
Mail list logo
