Log file Viewer

[08:52:58] <svenstaro> hey, could you guys make a new release for the ft 2.5.1 fix?

[08:53:09] <svenstaro> right now, stuff doesn't even make from pypi if you have that version of ft

[08:54:07] <svenstaro> a pillow 2.2.2 for this rather soon would be appreciated :)

[21:25:27] <jazwec> hello guys... ive just installed PIL and im looking for some basic tutorials and examples for it, but i cant find them anywhere.. stuff like chessboard, triangle, circle and so on. do you know where can i find something like that?

[22:30:18] <jazwec> anybode here who could help me, please?

[22:45:17] <wiredfool1> jazwec: have you looked at the PIL handbook?

[22:48:19] <jazwec> wiredfool1 i did but i havent found any examples there...but now i also have bigger problems, i cant successfully install and use the library

[22:49:35] <wiredfool1> ah. what platform and versions are you using?

[22:53:29] <jazwec> unfortunately, im using 64 bit windows 8..and python 2,7

[22:54:22] <wiredfool1> have you tried pillow, or are you committed to pil1.1.7?

[23:00:19] <aclark> needs more stability fixes

[23:01:08] <svenstaro> aclark: to

[23:01:10] <svenstaro> yo

[23:01:19] <svenstaro> let's discuss here

[23:01:21] <wiredfool1> aclark: heya

[23:01:22] <svenstaro> instead of on github

[23:01:34] <svenstaro> I think a 2.2.2 can easily be done

[23:02:02] <wiredfool1> I'm building a branch

[23:02:24] <wiredfool1> or at least, giving it a show

[23:03:07] <svenstaro> well git checkout -b 2.2.2; git cherry-pick fa7f9aa; git tag 2.2.2 or something like that

[23:03:15] <svenstaro> and then automatic pypi release stuff

[23:03:19] <aclark> svenstaro: o/

[23:03:20] <wiredfool1> yeah, there are versions

[23:03:24] <wiredfool1> in the code

[23:03:50] <svenstaro> I usually put that in the release script, I always forget to manually set those

[23:03:56] <wiredfool1> yeah

[23:04:05] <wiredfool1> though. there they are

[23:04:24] <aclark> shouldn't Pillow be broken for me if I'm on OS X?

[23:04:54] <svenstaro> if you have an up to date system maintained by brew, yes

[23:05:10] <aclark> so if i do: brew update right now that should break my Pillow, right?

[23:05:16] <svenstaro> probably

[23:05:27] <wiredfool1> that's why it went boom all of a sudden

[23:05:29] <aclark> and is there anyone to revert to an older freetype with brew?

[23:05:46] <aclark> I'm not a huge fan of releasing a new Pillow to fix some broken shit with another project

[23:05:55] <svenstaro> freetype fixed something

[23:05:59] <svenstaro> a long standing bug

[23:06:30] <aclark> But I understand it could be helpful… it really depends on how "noisy" it gets on the issue tracker. Most folks are happy to just run master for < 30 days

[23:06:51] <wiredfool1> breaks the easy install path

[23:06:56] <svenstaro> well I noticed this bug when I automatically deployed on my production systems

[23:06:59] <svenstaro> yes

[23:07:11] <svenstaro> deployment should be hands-off imo

[23:07:30] <svenstaro> the way freetype2 is now should be considered fixed

[23:07:41] <svenstaro> it used to have prefix/freetype2/freetype/someshit.h

[23:07:50] <svenstaro> now it's prefix/freetype2

[23:08:00] <svenstaro> + a config subdir that hopefully goes away

[23:12:54] <wiredfool1> aclark: did you kill the old 1.7.x branch?

[23:15:25] <wiredfool1> ok, here's a 2.2. release branch: https://github.com/python-imaging/Pillow/tree/rel_2.2

[23:16:13] <wiredfool1> aclark: if we tag that 2.2.2, does it do the release push?

[23:16:43] <aclark> wiredfool1: "release push" ?

[23:17:11] <wiredfool1> whatever it is that makes pypi pick it up

[23:17:24] <aclark> python setup.py upload :-)

[23:18:04] <wiredfool1> ah. so that would be you.

[23:18:27] <aclark> right

[23:18:49] <aclark> you can tag it, i'll ponder a release thanks

[23:19:34] <wiredfool1> ok, should be tagged

[23:20:31] <wiredfool1> and /me takes the pillow repo back to read only on my dev box

[23:20:38] <aclark> seems reasonable-ish

[23:21:00] <wiredfool1> I cherry picked the fix commit

[23:21:03] <wiredfool1> not the merge commit

[23:21:11] <wiredfool1> touched up the versions and the change log

[23:21:25] <aclark> right

[23:25:49] <svenstaro> \o/

[23:26:54] <wiredfool1> so fwiw, I'm planning on pinging the debian maintainer post 2.3 for an update into their systems

[23:27:08] <wiredfool1> hopefully to manage to get into ubuntu 14.04lts

[23:27:21] <wiredfool1> so that we're not supporting whatever version it is that manages to get there

[23:28:09] <aclark> wiredfool1: cool

[23:28:19] <wiredfool1> In doing that, we'll probably end up with a defacto long term support branch

[23:28:27] <aclark> good good

[23:29:07] <wiredfool1> so, the practice for pushing out a cherry picked fix is probably a good thing

[23:31:13] <wiredfool1> rather, that we're not supporting 2.0.0, which is what I think is the current one in deb/ubuntu

[23:32:34] <aclark> absolutely, we need to be handle these circumstances. I just don't like to do release unless it's absolutely necessary because that starts the binaries machine (which likely won't happen for 2.2.2, or at least I'd rather wait for 2.3.0 to provide a new set of binaries. But it's up to gohlke i guess.)

[23:34:26] <svenstaro> do you really need to provide binaries for anybody?

[23:34:37] <svenstaro> wouldn't people using pillow build their own chain anyhow?

[23:34:38] <wiredfool1> Is this issue going to affect windows people? This is a compile time issue

[23:34:49] <wiredfool1> windows binaries

[23:34:52] <svenstaro> sure, windows people would grab the most recent freetype version

[23:35:21] <wiredfool1> rather, is this going to affect the windows binary people?

[23:35:43] <aclark> wiredfool1: no idea, i assume not.

[23:35:58] <aclark> svenstaro: but the binary is already compiled, presumably

[23:36:15] <aclark> svenstaro: and yes, we need to provide windows binaries

[23:36:40] <aclark> svenstaro: too hard for mortals to build Pillow on Windows

[23:36:41] <wiredfool1> you know, the reason I roiginally contributed code was that I wanted someone else to take over building my windows binaries

[23:36:42] <svenstaro> don't you have an cross compiler set up for that?

[23:37:11] <wiredfool1> windows binaries are a fpita

[23:37:12] <aclark> svenstaro: i don't do it, this guy does: http://www.lfd.uci.edu/~gohlke/

[23:37:18] <aclark> (thankfully)

[23:37:42] <aclark> wiredfool1: hah! what did you contribute originally?

[23:37:53] <wiredfool1> libtiff

[23:38:08] <wiredfool1> I'd been maintaining an awful patch for ~6 years

[23:38:12] <svenstaro> I think windows people should just stop trying to write software imo :P

[23:38:17] <wiredfool1> then rewrote it to use public libtiff interfaces

[23:39:08] <wiredfool1> not sure I've pushed out a rev of my windows software since I did that, come to think of it.

[23:39:28] <svenstaro> it's so painful

[23:39:57] <wiredfool1> yah. but all my customers are on windows

[23:42:48] <svenstaro> I had that too once and set up a nice cross compiler system

[23:42:58] <svenstaro> fairly painless after that

[23:53:19] <wiredfool1> I want a puppet/chef/something script that will startup an ec2 instance and blat on a compiler and the dependencies for windows

[23:53:57] <wiredfool1> but, I want that less than a lot of other things since cgohlke is doing the builds

[23:59:07] <aclark> ooo

[23:59:24] <aclark> right