Log file Viewer

[13:45:06] <ronny> sup

[15:40:58] <ionelmc> i got a strage-ish question

[15:41:26] <ionelmc> is it possible to make setup.py install not use eggs while still using setuptools?

[15:41:38] <ionelmc> without using pip

[15:42:38] <ionelmc> essentially that would equate to a distutils-only setup.py but I want some other stuff that are present in setuptools (like find_packages and include_package_data)

[15:43:06] <tos9> you don't need to use setuptools.setup to use find_packages I imagine

[15:43:34] <tos9> And IIRC include_package_data doesn't really "work" -- is there other stuff you want too?

[15:43:56] <ionelmc> tos9: no, i need to, i'm lazy and i don't want to reimplement it

[15:44:12] <tos9> ionelmc: Sorry, which was that a response to?

[15:44:43] <ionelmc> tos9: tos9> you don't need to use setuptools.setup to use find_packages I imagine

[15:44:57] <tos9> ionelmc: Yes, I wasn't saying to reimplement it

[15:45:11] <tos9> ionelmc: I'm saying I can't imagine distutils.core.setup(..., packages=setuptools.find_packages()) doesn't work

[15:45:20] <ionelmc> once you import setuptools your poor old distutils gets monkeypatched

[15:45:22] <tos9> find_packages is probably just a function that does the descending and returns the list.

[15:45:45] <tos9> ionelmc: oh. I don't know about the arcane details of that, but that's even if you import distutils.core first?

[15:46:03] <ionelmc> tos9: it monkeypatch all the distutils commands

[15:46:07] <tos9> Fun.

[15:46:14] <tos9> I don't know then sorry.

[15:46:20] <ionelmc> that's not fun

[15:46:29] <ionelmc> you know what's really fun?

[15:46:40] <ionelmc> monkeypatching what setuptools has patched before

[15:46:51] <ionelmc> hahahah

[15:47:40] <tos9> class FakeDistutils(object): pass; import sys; sys.modules["distutils"] = FakeDistutils(); import setuptools; del sys.modules["distutils"]; import distutils.core; print "CRY"

[15:47:53] <ionelmc> :-)

[15:47:55] <tos9> ionelmc: OOC why do you care about eggs?

[15:48:30] <ionelmc> tos9: well, ok, so you know deb packages right?

[15:48:50] <ionelmc> basically you have a script that installs the package into a temp prefix

[15:48:57] <ionelmc> and that gets into the .deb

[15:49:10] <ionelmc> but i don't want any of that egg stuff in my .deb

[15:49:17] <ionelmc> cause that means dependency on setuptools

[15:51:20] <ionelmc> oh snap!

[15:51:24] <ionelmc> there's --single-version-externally-managed

[15:51:25] <tos9> can you build the deb out of a wheel instead?

[19:48:53] <ronny> dstufft: ping? any idea if there is a way to aks for setup_requires without deeply hacking into setup.py?

[19:49:24] <dstufft> ronny: I don't think so sadly

[19:50:58] <ronny> dstufft: i see, then i shal add one

[19:51:06] <ronny> dstufft: i need it for tox

[19:51:56] <ronny> the plan is to generate dists using setup_requires, wheels install in a separate virtualenv

[21:36:01] <DanielHolth> my setup-requires implementation wasn't the hit I hoped it would be. people seem to want everything to happen in setup.py. Even though setup-requires is something that pip should be doing in its role as a build system

[21:37:22] <jaraco> ronny, I added two comments in the setuptools_scm bug tracker about my response to reading the readme.txt.

[21:37:50] <dstufft> I think that, at least personally, people generally don't want to add more hacks ontop of an already fragile toolchain if they need to

[21:37:55] <dstufft> if they don't need to*

[21:38:12] <jaraco> Other than those two issues, I'm completely happy with the approach.

[21:38:56] <DanielHolth> I have got to update Bento with modern wheel support one of these days

[21:39:25] <DanielHolth> Unfortunately I haven't been writing very many python packages with horribly complex build requirements lately.

[21:40:42] <dstufft> DanielHolth: you and I have very different concepts for what is unfortunate or not

[23:41:16] <AlecTaylor> hi

[23:41:54] <AlecTaylor> How do I specify in my requirements.txt to update the package to the latest?

[23:42:04] <AlecTaylor> Tried: -U bottle