--- Day changed Fri Sep 07 2018 01:12 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #joinmarket 01:27 -!- undeath [~undeath@unaffiliated/undeath] has joined #joinmarket 03:04 -!- undeath [~undeath@unaffiliated/undeath] has quit [Quit: WeeChat 2.2] 03:24 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket 03:46 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds] 03:49 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #joinmarket 04:18 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket 04:28 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket 07:41 -!- undeath [~undeath@unaffiliated/undeath] has joined #joinmarket 08:08 -!- undeath [~undeath@unaffiliated/undeath] has quit [Quit: WeeChat 2.2] 09:21 -!- grubles_ [~grubles@gateway/tor-sasl/grubles] has joined #joinmarket 10:37 -!- grubles_ [~grubles@gateway/tor-sasl/grubles] has quit [Quit: Leaving] 11:21 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #joinmarket 14:51 < belcher_> is there a way to use joinmarket's install.sh with "pip -e" ? so its installed only in the same directory, can be edited and doesnt interfere with other installations 14:51 < belcher_> im reading install.sh now but i dont know the details of bash, might be quicker to ask here 15:20 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 15:24 < waxwing> belcher, there's two different things there i think; one is, it installs into a virtualenv (as per instructions), so it won't interfere with other installations, but 2/ is that you can pass --develop to the install script so that code edits get used by the virtualenv 15:24 < waxwing> basically the pip -e thing you mention, so you're just installing a link in the virtualenv, not a copy of the code 18:20 -!- grubles [~grubles@gateway/tor-sasl/grubles] has quit [Ping timeout: 256 seconds] 19:11 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #joinmarket