[19:29:09] <jamescarr> If I build a wheel of my application
[19:29:22] <jamescarr> does it also build and include all the dependencies?
[19:30:53] <ronny> jamescarr: no, wheels do not contain and include dependencies, instead they refer to them, then pip takes a look before installing the wheel and installs them as well
[19:32:52] <DanielHolth> pip wheel does build the dependencies as separate wheels
[19:47:49] <plathrop> Any chance of ever changing that? I'd love to single-artifact-deploy my python apps.
[19:48:40] <ronny> plathrop: there is a new format for single artifact apps that are zippable
[19:48:55] <ronny> plathrop: as for the wheels, just make a bundle of all required wheels?
[19:49:03] <ronny> plathrop: what kinda apps do you deploy?
[19:49:45] <plathrop> ronny: several different types, from tornado-based web applications to CLI tools to django webapps
[19:50:34] <plathrop> We've been struggling to find the right way to manage single-artifact repeatable builds/deploys, and learning the ins and outs of setup.py vs. requirements.txt, etc.
[19:51:12] <plathrop> The fact that virtualenvs aren't relocatable has been rough
[19:51:24] <plathrop> But we've kinda settled on building debian packages of things
[19:52:34] <plathrop> We've got a package.sh that basically creates a virtualenv, installs the app and dependencies into it, uses virtualenv-tools to make the virtualenv relocatable, and then makes a debian package out of the resulting directory structure.
[19:52:38] <ronny> plathrop: hmm, hmm, tommorow will decide if sunday a relocatable replacement for virtualnv will exist ^^
[19:53:00] <plathrop> But I'm not sure if we're just Doing It Wrong or what :-)
[19:53:20] <plathrop> ronny: Oh really? Interesting. I'lm exciting to see where that goes.
[19:53:32] <plathrop> excited. Ugh, not enough caffeine
[19:55:41] <plathrop> Part of our problem is just not being modern, of course. We're still stuck on pip==1.4.1 because reasons that will bore you but I assure you make sense in our environment for now.
[19:57:35] <dstufft> plathrop: pex is a decent thin if you want a single file deployment (minus Python itself)
[20:21:02] <_habnabit> plathrop, dh_virtualenv is a project that tries to make debs out of virtualenvs and it's really bad; pex is a better solution, and i'm writing up a thing about how to use pex with debian to make .debs that deploy single-artifact python apps
[20:21:55] <plathrop> _habnabit: I'll happily be a beta reader for you :-)
[20:22:11] <_habnabit> plathrop, cool; i'll keep that in mind
[20:22:45] <plathrop> Totally out of the kindness of my own heart, obviously. No way I'll profit from getting my grubby little hands on that tchnique...