=== Saviq is now known as Saviq|QtCS === vrruiz_ is now known as rvr === kenvandine_ is now known as kenvandine [14:32] barry, I have a weird python error I'm wondering if you might be able to help me with. The error only occurs on the device; OverflowError: timestamp out of range for platform time_t. [14:36] balloons: could be a 32bit thing perhaps? [14:38] barry, mm.. yes. I need a way to define an arbitrary time (hours and minutes) with no regards to date or timezone.. and not get this error [14:39] balloons: what is the code that triggers this error? [14:40] barry, I started to share, but I'm seeing a qml error that makes me think it might still be something in the code [14:40] regardless, let me paste [14:41] barry, here's a simplified snippet of code.. http://paste.ubuntu.com/7634006/. It fails in the set_picker function [14:42] the traceback [14:42] http://paste.ubuntu.com/7634011/ [14:44] balloons: it would be interesting to know what self[0] is [14:48] barry, thanks.. this session is almost over and I'll hack on it a bit more and ping you again if needed [14:49] balloons: sounds good === Saviq|QtCS is now known as Saviq [17:33] balloons: do you have time for a review? [17:33] https://code.launchpad.net/~elopio/ubuntu-filemanager-app/clean_context_menu_tests/+merge/222888 [20:52] barry: got time for a quick hangout call in 10-15 minutes? [20:55] thomi: hey. yeah [21:03] barry: nuclearbob: https://plus.google.com/hangouts/_/g7m47jdjaxzu35ctiy2u4a3w2qa?authuser=1&hl=en [21:11] https://launchpad.net/~fkrull/+archive/deadsnakes [21:19] nuclearbob: https://wiki.canonical.com/UbuntuEngineering/2014/Debconf2014 [21:29] excellent. steve can be very convincing too :) [21:29] I'd love to be a fly on the wall in that discussion :) [21:30] :) [21:30] nuclearbob: I'm doing a dist-upgrade, then I'll re-try your pyramid package [21:31] thomi: my test branch is here, if it ends up being useful: lp:~nuclearbob/+junk/pyramid-test [21:31] I think it's time for me to dist-upgrade too [21:31] nuclearbob: awesome, thanks [21:31] nuclearbob: sp [21:32] nuclearbob: so I'll spend today trying to get a basic pyramid app + the database set up [21:32] nuclearbob: I'll stick the work in a branch that we both have write access to [21:32] nuclearbob: and I'll email you at my EOD so you can pick up where I left off tomorrow - sounds good? [21:32] thomi: that works [21:41] nuclearbob: got another bug report: pserve segfaults [21:42] err, I mean "crashes" [21:42] nuclearbob: looks like a problem in chameleon [21:43] nuclearbob: http://pastebin.ubuntu.com/7635676/ [21:47] thomi: that's interesting [21:47] "interesting" is one word for it [21:47] I can use two if you want [21:47] way interesting [21:50] hmm [21:50] so you have this in a container, or somewhere else? [21:55] nuclearbob: just on my laptop [21:59] thomi: can you pip in chameleon and see if that fixes it? [22:11] nuclearbob: sure, one sec [22:12] nuclearbob: can't use a virtualenv with pserve [22:13] thomi: hmm [22:14] I could have sworn the pyramid tutorial started with a virtualenv [22:14] I do everything in containers so I can just pip in stuff will-nilly and toss it if I need to [22:14] oh, probably if I install pyramid as well [22:14] thomi: what user are you using? can you pip stuff with --user [22:14] right, it was part of the install [22:14] but pserve's #! line doesn't use 'env' [22:15] I bet it gets rewritten by the packaging [22:15] I think it's debian policy to not use env in python shebang lines [22:16] yeah, so I get the same error when trying to import the brand new scaffolded pyramid app [22:16] so it's not just pserve [22:16] python [22:16] oops [22:17] similar traceback [22:18] nuclearbob: you basically cannot import pyramid.config.Configurator, which seems pretty central to pyramid apps :-/ [22:19] thomi: indeed. I'm taking a look in my container [22:19] works with the packages I built there, I'll try a new container and the packages from the ppa [22:19] same error on your branch FWIW [22:20] thomi: thanks. Knowing that that import fails should make it easy to track down [22:20] nuclearbob: reproducer is: python3 -c "import pyramid.config" [22:23] getting a new container spun up [22:23] doot doot doo [22:36] okay, blowing up with the packages, let's see how much I have to pull in from other sources to fix it [22:55] okay, importing chameleon at all blows up [22:55] nuclearbob: hmmm [22:55] and if I install pyramid via pip, I don't get chameleon [22:55] oh yeah [22:55] hmmm [22:55] maybe the chameleon dependency is dropped in 1.5? [22:58] nuclearbob: we should probably be packaging 1.5 anyway? [22:58] thomi: yes, I just grabbed 1.4 because it was already packaged for trusty, but 1.5 does remove the chameleon dependency [22:59] thomi: I'll get that packaged, I'm only on for another hour today, so I'll see if I make it [22:59] nuclearbob: I've already done it for python 2 annyway - perhaps you can re-use that work? [22:59] thomi: I think between your work and mine it should be easy [22:59] but things I think should be easy still sometimes take a couple hours to get built into ppas [23:00] thomi: can you throw me your branch url again? [23:00] nuclearbob: there's no branch, just a debian bug and a diff [23:01] thomi: is the diff in the packaging email thread or somewhere else? [23:01] nuclearbob: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751067 [23:01] Debian bug 751067 in python-pyramid "python-pyramid: Bump upstream version" [Normal,Open] [23:14] all right, this package can import pyramid.config [23:14] let's get it uploaded [23:16] threw it at my ppa [23:16] nuclearbob: which ppa? [23:19] thomi: I threw it at mine first to make sure it got accepted, I'll push it to the ci one once it builds [23:20] ugh, 9 minutes. I can't wait for that. I'll push it to the ci one too and they can race [23:21] nuclearbob: awesome, thanks man [23:23] nuclearbob: I'll send you an email at my EOD with whatever I got done [23:23] have a good evening! [23:32] thomi: cool, thanks