Log file Viewer

[20:45:32] <dstufft> jaraco: ping

[20:45:41] <jaraco> hi dtsufft

[20:45:55] <dstufft> jaraco: any opinion on setuptools dropping support for 3.2?

[20:47:33] <jaraco> I’m generally in favor. I hope the fallout will be minimal.

[20:47:53] <jaraco> I’d rather drop support for Python 2.7 ;)

[20:48:02] <jaraco> just kidding, really.

[20:48:04] <dstufft> jaraco: me too :(

[20:48:23] <dstufft> jaraco: fwiw https://caremad.io/images/a-year-of-pypi-downloads/stacked-py3-pct.png across all of PyPI ~6 months ago

[20:49:09] <jaraco> Very cool.

[20:49:14] <dstufft> jaraco: I ask, because I'd like to drop 3.2 support from pypa/packaging, but I wont' do it as long as setuptools still supports 3.2

[20:49:57] <jaraco> Should the next release of setuptools hard fail if it encounters 3.2, or only remove stated support?

[20:49:59] <lifeless> Nakato_: StevenK: ping / anything to sync on ?

[20:50:18] <lifeless> jaraco: I'd rather a hard fail than a time bomb

[20:50:41] <lifeless> jaraco: I still support 3.2 in my toolchains that are built on setuptools

[20:51:13] <lifeless> jaraco: and if setuptools says '3.2 is dead to me' then I can sanely say 'we don't support 3.2 anymore either, if you want to change, go talk to setuptools' :)

[20:51:42] <lifeless> whereas if it sometimes breaks sometimes works, we'll pay support debt longer

[20:52:13] <lifeless> jaraco: noone does, but the reality is the bottom of the toolchain defines whats supported :)

[20:52:42] <lifeless> jaraco: if I remove 3.2 support from mock, folk that need it will have to pin mock - thats understandable and the way they need to deal

[20:52:57] <jaraco> lifeless, dstuff: what do you think about a setuptools 19 that deprecates support for Python 3.2 (issuing a warning) and a subsequent release in a few months that fails fast?

[20:53:13] <lifeless> jaraco: while supporting 3.2 is cheap I'm happy to do that, when supporting 3.2 becomes hard, then I'll drop it like a hot potato ;)

[20:53:34] <lifeless> jaraco: I think a visible warning might get some data about whether folk actually care

[20:53:52] <lifeless> jaraco: I dropped 2.6 support for mock and got folk to step up and help maintain the backports

[20:53:59] <lifeless> [and we re-introduced 2.6 support]

[20:59:24] <dstufft> jaraco: seems sane to me

[21:00:02] <dstufft> for completeness sake, pip 8 drops support for 3.2 (and will likely be released early 2016)

[21:00:13] <jaraco> I’ve decided 18.5 for the warning, and 19.0 (or similar) for the dropped support.

[21:02:01] <lifeless> I'm going to start a couple of threads about this on tip and the openstadk dev lists

[21:02:09] <lifeless> just in case there's a surprise lurking

[21:02:27] <pmxbot> jaraco pushed 1 commit to setuptools (https://bitbucket.org/pypa/setuptools/) :

[21:02:27] <pmxbot> Dropping support for Python 3.2 and earlier Python 3 versions. Currently only log a warning, but future versions will fail.

[21:23:56] <jaraco> lifeless: if there’s any response worth noting in those threads, I’ll probably miss it, so would you comment on that commit (https://bitbucket.org/pypa/setuptools/commits/1cbe02d87fa9b23c3798ef45f3e80e6c75426452) to draw it to my attention?

[21:24:25] <lifeless> jaraco: if anything significant or contentious turns up I shall do that

[21:24:35] <lifeless> jaraco: but it would need to be pretty big

[21:24:46] <jaraco> !thanks lifeless

[21:24:46] <pmxbot> you're doing good work, lifeless!

[21:25:57] <xafer> jaraco, since it is currently only a warning you might want to keep testing 3.2 in travis ?

[21:30:03] <lifeless> jaraco: from tip

[21:30:04] <lifeless> PyPy only supports 3.2 right now. The 3.3 release is almost ready,

[21:30:04] <jaraco> xaver: I could, and I will if I end up maintaining an 18.x branch.

[21:30:05] <lifeless> first rc went out today. It may make sense to hold off on this until

[21:30:05] <lifeless> PyPy has made it's next release.

[21:53:07] <dstufft> jaraco: you might find this interesting https://youtu.be/hM1wKsOYOIc

[21:53:51] <dstufft> (I'm fucking around with gource :D)

[21:54:39] <jaraco> That’s really cool.

[21:56:43] <dstufft> it's a little weird on setuptools because of the fork and merge

[23:47:32] <Nakato_> lifeless: I don't think so currently. I need to write an email for http://lzma.so/BTQUTU and I'm working on getting data out of ElasticSearch which is coming along nicely.

[23:48:03] <lifeless> cool