Log file Viewer

[00:00:05] <glyph> dstufft: metasetup should have a command to _generate_ it, but then you don't edit it

[00:00:09] <dstufft> glyph: even if it looked like this http://bpaste.net/show/Ek5PD4tBBzsY7oTpCizh/

[00:00:41] <glyph> dstufft: don't lead with the solution, lead with the problem. why would I do this?

[00:01:41] <dstufft> glyph: So you're doing a bunch of hacky stuff to serialize modules and then reconstitute them inside of a setup.py, what if we just don't do that, and use the setuptools functionality (sort of) to do this

[00:02:06] <dstufft> I say sort of, because it requires a little bit of monkeypatch

[00:02:16] <dstufft> This is what d2to1, and pbr do

[00:03:08] <glyph> dstufft: that would be a good idea if setuptools worked

[00:03:12] <glyph> dstufft: but, too bad, it doesn't

[00:03:37] <glyph> dstufft: also, I don't see how that helps me at all with the plugin-generation case

[00:04:30] <dstufft> glyph: afaik this part of setuptools works

[00:05:02] <dstufft> hrm

[00:05:48] <dstufft> I might try to PoC this

[00:06:31] <dstufft> monkeypatching distutils.core.Distribution or w/e the hell the location is, makes me feel far less janky than trying to serialize + reconstitute a bunch of modules

[00:06:56] <dstufft> it would work for setup.py develop && pip install -e

[00:07:51] <dstufft> hrm, the hard part would be hooking in for at_setup_time after setup_requires, but before setup()

[00:09:37] <dstufft> hum

[00:09:43] <dstufft> I might try to PoC that

[00:09:52] <dstufft> I think I can hook it in at the right place

[00:09:53] <dstufft> to make it work

[00:13:18] <glyph> dstufft: I'd be happy to receive a PR :)

[00:13:58] <Alex_Gaynor> glyph: FWIW the setup_requires=["foo"], foo=True method is what pbr uses, and lots of people use that

[00:14:14] <Alex_Gaynor> like, pbr has more downloads than django

[00:14:14] <dstufft> yea, but pbr doesn't support hooks at install time

[00:14:40] <dstufft> although

[00:14:41] <dstufft> durr

[00:14:45] <dstufft> pbr itself runs after setup_requires

[00:14:53] <dstufft> so I don't have to even do anything special

[00:15:00] <dstufft> just run the hooks

[02:14:51] <Ivo> huh

[02:15:18] <Ivo> PyPI's PIL is only 1.1.6, from 2006, latest is 1.1.7, from 2009

[02:54:02] <glyph> Ivo: 'pip install pillow'

[02:55:10] <Ivo> glyph: you assume I don't know that? This being considerate of people using project they're not maintainers of that have PIL as a dependency

[02:56:43] <Ivo> moving to pip 1.5 has made stuff that worked before quite a pain for a few people, while sometimes its judged to be necessary for improving things, its always nice to minimize that wherever possible

[02:57:08] <Ivo> I was hoping to track down contact details for PIL's maintainer, turns out he's a hard man to get an email address for

[02:58:46] <Ivo> *more than a few

[02:59:53] <glyph> Ivo: sorry, I didn't mean to be dismissive :)

[03:00:02] <glyph> Ivo: I myself only learned that it was basically compatible recently.

[03:01:24] <Ivo> glyph: sorry too, I am probably overly confrontational...

[03:01:43] <glyph> no, it's cool, that comment was pretty flippant

[03:01:57] <Ivo> have a problem with not providing enough context to initial statements

[03:38:18] <dstufft> I already emailed effbot

[03:38:21] <dstufft> I got zero response

[03:38:37] <dstufft> from way before my time, but from what i'm told, effbot got shit on awhile back

[03:38:45] <dstufft> and has more or less disappeared since then

[03:39:00] <Ivo> by the python community?

[03:39:08] <dstufft> yea

[03:39:12] <dstufft> that's what Richard said anyways

[03:39:38] <dstufft> way before my time he said, so I don't know all the details, so this is like 3rd hand or whatever :/

[03:39:53] <dstufft> but apparently there was some big thing

[03:39:55] <dstufft> idk what

[03:39:55] <Ivo> still made a release for it in 2009 tho

[03:40:55] <dstufft> and he's maintained the download server

[03:41:12] <dstufft> so its not like he peaced out and left everyone to rot or anything

[03:41:20] <Ivo> how long does an 'important' package maintainer need to be completely afk for before we can think about updating their pypi page for them...

[03:41:29] <dstufft> Richard talked about that

[03:41:40] <dstufft> he's hesitant to do it for PIL because of the big thing that happened

[03:41:59] <Ivo> specifically upload 1.1.7 tar.gz and 2.6/2.7 exes

[03:42:39] <Ivo> damn humanity

[03:42:43] <Ivo> always fucking shit up

[16:08:54] <dropdrive> Is pip install --editable or setup.py develop recommended?

[20:13:04] <paranoidi> we've had many confused users in #flexget who have tried to use pip from wrong version of python

[20:13:42] <paranoidi> it would help a lot if pip would have this info visible somewhere (eg --help)

[21:15:11] <Ivo> dropdrive: the former pretty much does the latter

[21:15:42] <Ivo> paranoidi: perhaps file an issue over on github to discuss

[21:25:08] <dstufft> paranoidi: pip --version has this info

[21:25:40] <dstufft> $ pip --version

[21:25:40] <dstufft> pip 1.5.4 from /Users/dstufft/.virtualenvs/pip/lib/python3.4/site-packages (python 3.4)

[21:26:16] <paranoidi> dstufft: oh, excellent .. I tried couple argumenta but not that

[22:07:51] <Ivo> aliased as pip -V