PMXBOT Log file Viewer

Help | Karma | Search:

#dcpython logs for Friday the 23rd of March, 2012

(Back to #dcpython overview) (Back to channel listing) (Animate logs)
[15:33:35] <jaraco> I configured pmxbot to connect to 'localhost' for the database.
[15:56:17] <aclark> !help
[15:56:17] <pmxbot> !8ball (8) !acronym (ac) !anchorman !annoy (a, bother) !bender (bend) !bitchingisuseless (qbiu) !blame !bless !boo !bottom10 (bottom) !calc !chain !cheer (c) !c
[15:56:18] <pmxbot> ompliment (surreal) !ctlaltdel (cad, controlaltdelete, controlaltdelete, quit, restart) !curse !dance (d) !deal !define (def) !demotivate (dm) !disembowel (dis,
[15:56:18] <pmxbot> eviscerate) !duck (ducky) !embowel (reembowel) !excuse (e ) !featurecreep (fc) !fight !flip !fml !gettowork (gtw) !golfclap (clap) !google (g) !googlecalc (gc)
[15:56:18] <pmxbot> !grail !hal (2001) !hangover !help (h) !hgup (hg, hgpull, update) !hire !imotivate (im, ironicmotivate) !insult !job (card) !karma (k) !keelhaul (kh) !klingon
[15:56:18] <pmxbot> (klingonism) !lunch (lunchpick, lunchpicker) !meaculpa (apologize, apology) !motivate (appreciate, m, thank, thanks) !murphy (law) !nailedit (n, nail) !nastygra
[15:56:19] <pmxbot> m (bcc, nerf, passive) !oregontrail (otrail) !panic (pc) !password (passwd, pw) !paste !pick (p, p:, pick:) !progress !quote (q) !r (r) !roll !rubberstamp (appr
[15:56:19] <pmxbot> ove) !saysomething !simpsons (simp) !stab (shank, shiv) !storytime (story) !strategy !strike !tgif !therethere (comfort, poor) !ticker (t) !time !tinytear (cry,
[15:56:19] <pmxbot> tear, tt) !top10 (top) !translate (googletrans, googletranslate, trans) !troutslap (slap, ts) !urbandict (ud, urb, urbandef, urbandefine, urbandictionary, urbd
[15:56:20] <pmxbot> ef) !weather (w) !where (last, lastseen, seen) !zinger (zing) !zoidberg (zoid)
[15:56:30] <aclark> !motivate jaraco
[15:56:30] <pmxbot> you're doing good work, jaraco!
[15:57:35] <leetrout> oregon trail?!
[15:57:42] <leetrout> oh man
[15:57:52] <leetrout> !oregontrail
[15:57:52] <pmxbot> #dcpython capsized while floating across the river.
[15:57:58] <aclark> hah
[15:58:35] <leetrout> oh nice, and it works with direct queries
[15:59:38] <jaraco> !otrail pmxbot
[15:59:38] <pmxbot> pmxbot has exhaustion.
[15:59:48] <aclark> !simpsons
[15:59:48] <pmxbot> (17574/37428): Bart: You owe me a quarter, I didn't crack my skull.
[15:59:55] <aclark> !lunch
[15:59:55] <pmxbot> Zoiks! An error occurred: 'O' object has no attribute 'lunch_choices'
[15:59:55] <pmxbot> !lunch Pick where to go to lunch
[15:59:59] <leetrout> !fc
[15:59:59] <pmxbot> Empower mission-critical markets!
[16:00:08] <aclark> hah
[16:00:35] <leetrout> whose bot?
[16:00:52] <jaraco> It's pmxbot, developed at Polimetrix (now YouGov).
[16:01:01] <jaraco> Open-source at bitbucket.
[16:01:12] <rzoz> i was about to say i think that's the bot developed at self.former_employer
[16:01:35] <j00bar> rzoz.employers[-2]
[16:01:46] <leetrout> i saw the source, just wondered who brought it in... :D
[16:02:06] <rzoz> yup. never thought i'd see that particular bot again... :)
[16:02:11] <leetrout> i'm reliving my child hood
[16:02:35] <jaraco> heh. I brought it in.
[16:03:18] <leetrout> !grail
[16:03:18] <pmxbot> (13/1106): ARTHUR: We found them.
[16:03:20] <rzoz> it adds a little k-st flavor
[16:04:21] <leetrout> i'm so out of the loop- i didn't know freenode had chanserv
[16:04:57] <rzoz> !tinytear
[16:05:24] <rzoz> ok, now /me feels a little better about these time zone issues.
[16:05:37] <leetrout> uhh
[16:05:40] <leetrout> gag
[16:05:51] <j00bar> time zone issues?
[16:05:52] <leetrout> why can we all not switch to metric system and UTC
[16:05:55] <leetrout> and be done with it
[16:06:18] <rzoz> j00bar: i get in runway usage data for airports, but their in local time zone
[16:06:23] <rzoz> they're*
[16:06:32] <j00bar> ah.
[16:06:52] <j00bar> don't envy our timezone fun
[16:07:07] <j00bar> we gather facebook stats for ad performance
[16:07:14] <j00bar> but they only give you 24-hour snapshots
[16:07:20] <rzoz> the weird thing i just found is, they don't adjust the timezone throughout the day, so it's whatever it starts in at midnight
[16:07:26] <rzoz> screwing things up
[16:07:26] <jaraco> leetrout: I used to think the same - we should all switch to UTC, but then I realized that doesn't solve the time issues either. If everybody switched, then we would have to keep track of what time "things happen" such as what is a reasonable time for work to start in California versus Texas.
[16:07:31] <j00bar> but the 24 hour period is midnight-to-midnight local to the timezone of the ad account's user adjusted to utc
[16:07:49] <rzoz> j00bar: that's similar to what we have
[16:07:56] <rzoz> j00bar: actually... the same
[16:07:58] <j00bar> so east coast accounts run from 4am to 4am or 5am to 5am depending on the year
[16:08:07] <rzoz> j00bar: yeah. it makes me want to cry.
[16:08:08] <j00bar> and west coast accounts 7am to 7am or 8am to 8am
[16:08:40] <j00bar> it makes me cry twice a year when i find some developer incrementing a tz-naïve datetime object by timedelta(days=1)
[16:08:58] <rzoz> ugh
[16:08:59] <jaraco> hours=1 ?
[16:09:37] <aclark> hah
[16:10:09] <j00bar> no - if you ask facebook for the stat from 4am to 4am march 10, 2012, and then try to get the stats for the next day by adding timedelta(days=1), facebook gives you the stinkfinger
[16:10:17] <aclark> that is hella-annoying
[16:10:25] <j00bar> because there are no stats that run from 4am to 4am march 11, 2012 - only 5am to 5am
[16:10:39] <jaraco> oh, that's horrable
[16:10:43] <jaraco> *horrible even
[16:10:52] <rzoz> we have tables of time zone changes which are helpful, but the data are broken too in a way. i have this beautiful foo.convert(airport, datetime) method to which i will now have to add a foo.convert_as_if_it_were_still_midnight_or_something_awful_like_that(airport, datetime)
[16:11:50] <rzoz> i don't understand why this particular data set is in local time. everything else we get from faa is zulu.
[16:11:58] <j00bar> yeah, and we have all of these awful "what day is it and what time does its stats start?" functions where we have to take the local time gmt, adjust it to the local timezone, drop the time part to get the date, add 00:00:00 local, and adjust to utc
[16:12:47] <j00bar> because today's stats at 1am utc for east coast accounts are actually the previous day's (from utc's perspective)
[16:13:19] <j00bar> demonstration #9512 of how facebook's api is super helpful
[16:15:23] <leetrout> hrmm
[16:15:27] <leetrout> i hadn't ran into that
[16:15:30] <leetrout> so very thankful