2018-03-12 UTC
tantek, snarfed, [miklb], [kevinmarks], [snarfed], [eddie], [mrkrndvs], schmarty and swentel joined the channel
snarfed and [snarfed] joined the channel
# 15:09 Loqi snarfed has 7 karma in this channel (368 overall)
[eddie], tantek, [cleverdevil], snarfed and snarfed1 joined the channel
# 20:02 bear oh boy - yes "wheee" -- 2.7 with it's forward look lib is a huge boon
[mrkrndvs] and [snarfed] joined the channel
# 20:10 [snarfed] bear: huh. urllib.requests? (I'm using the third party requests library in 2/3 compatible code now and that seems fine so far)
# 20:11 bear it doesn't (that i've seen) have a 3.0 release out for some of it's more fun features
# 20:11 [snarfed] btw porting these projects to circle 2 has gone well so far! a bit tricky getting both Python 2 and 3 usable, had to install python3 pip manually since evidently the one Debian (14?) shipped was broken (?), but otherwise ok
# 20:11 bear most of mine were related to really old uses of it
# 20:12 bear you can specify your own container base image if that helps
# 20:12 bear what is your github org name on circleci - let me see what extras I can enable for you
# 20:13 snarfed1 ooh sure! the repos are just under my username, snarfed. oauth-dropins, granary, bridgy
# 20:14 snarfed oh and i misspoke, i needed a fixed version of py3 venv, not pip. got it with apt-get install -y python3.4-venv
ben_thatmustbeme joined the channel
# 20:17 bear yea, venv and pip and wheel sometimes cause me waves of glitches, but then they settle down
snarfed joined the channel
# 20:31 snarfed porting my work repo, however, will be a whole different beast...
# 20:43 bear so, one of the easier things you can do is to check the box "open source"
# 20:43 bear as long as the project is public you will get a bump from 1 to 4 containers
# 20:45 bear doing that should enable most of your tests to run in parallel
# 20:45 snarfed true! thanks! latency/throughput aren't actually problems or priorities for my open source projects, so i haven't parallelized them yet
# 20:46 bear another thing you could try is to persist your pip/venv working environment in a workflow - workflows share artifacts so once it's installed the other job runs will pick that change up
# 20:55 snarfed ah, interesting, so a more explicit, manageable alternative to cache
tantek joined the channel
# 21:06 bear and the workflow keeps it sync'd across workflow job runs so you don't have to be explicit about it
snarfed, tantek, [eddie], [cleverdevil] and [kevinmarks] joined the channel
[miklb] joined the channel