Log file Viewer

[14:35:29] <DonQuestion> Hi! Can me someone explain how to use a setup.cfg with python 2.7? pastebin: http://pastebin.com/RReWSbbE

[14:36:13] <DonQuestion> Essentially i want to use setup.cfg to fill out all the default keywords...

[14:57:31] <DonQuestion> The documentation in this regard is rather lacking, so i was hoping to find someone, who could explain, why my example does not work as intended

[15:01:01] <pf_moore> DonQuestion: I don't think you can do that. For setup.cfg, the section name is the command (e.g. [build]) and the values are command line option names. You can't set metadata via command-line options, though.

[15:07:25] <DonQuestion> @pf_moore: i guess this is a distutils2 example: http://alexis.notmyidea.org/distutils2/setupcfg.html so this is not working with python2-stdlib distutils?

[15:15:48] <DonQuestion> @pf_moore: Turning distutils debug mode on, shows, that distutils takes the metadata provided: http://pastebin.com/urEge3eM

[15:17:39] <DonQuestion> @pf_moore: but it seems to use it as a "metadata" command, so you might be right.

[15:34:38] <pf_moore> DonQuestion: ah, yes, distutils2 is a completely different thing - it never got fully implemented, and is no longer being worked on AFAIK

[15:38:41] <DonQuestion> @pf_moore: is there no way to achieve the same with the current distutils in the stdlib? i took a glance at the source, but quite frankly, my eyes started bleeding after a few seconds ;-)

[19:02:59] <pf_moore> DonQuestion: Sorry, was afk - not really, just put the values in setup.py.

[19:50:53] <sontek> Hey, is there a way to use pip to install sdists in the same location every time instead of by their version?

[19:51:12] <sontek> i.e I don't wont app-1.0-py27.egg-info/ and then app-1.5-py27.egg-info/

[19:51:20] <sontek> I just want app-py27.egg-info/

[20:01:52] <sontek> The problem I'm trying to solve is with zero downtime deploys, when we gracefully reload our application the egg-info directory has moved

[20:02:14] <sontek> but sys.path has already been loaded in the master process, so it thinks it should get the entrypoints from 1.0 instead of 1.5

[22:52:40] <nanonyme> sontek, some people solve this by having fresh new Docker containers with new versions of software, then route to new one instead of old when the new one is ready

[22:53:35] <nanonyme> Zero downtime without a new Python process is rather hacky

[22:54:25] <apollo13> also, one usually has loadbalancers in front anyways, take out one server, update and put back in -- now rinse and repeat

[22:54:30] <doismellburning> s/Docker containers/instances/

[22:55:09] <doismellburning> (spot who's bored of people talking about Docker like it's Magic New OMG)

[22:56:35] <nanonyme> doismellburning, fine. I was just meaning you probably want some light-weight container