[00:33] <mhall119> Ronnie: that's also way too many queries for a single page :(
[00:33] <Ronnie> mhall119: it indeed is
[00:33] <mhall119> definitely sounds like we need a select_related somewhere
[00:34] <Ronnie> select_related does not help with O2M relations like teamevent->teams
[00:34] <Ronnie> i got it reduced to 2000 queries. but thats still a lot
[00:34] <mhall119> true, but sometimes you can reverse how you're doing the query to make it work
[00:35] <Ronnie>  mhall119, yes i did that on the venue list page, which reduced 800 to 10 queries
[00:35] <mhall119> \o/
[00:35] <Ronnie> but i see no option here
[00:35] <mhall119> aw :(
[00:35] <Ronnie> only this command: https://docs.djangoproject.com/en/dev/ref/models/querysets/#prefetch-related
[00:35] <mhall119> Ronnie: where are you looking?
[00:36] <Ronnie> but thats only available in the dev (1.4) version
[00:36] <Ronnie> mhall119: http://localhost:8000/meetings/history/
[00:38] <mhall119> Ronnie: are the queries coming from the history_meetings() on the model manager, or from something in the template/
[00:38] <Ronnie> the template has a teamevent.teams.all, that means that for each teamevent it should get the teams from the db. also the starttime, which is depended of the first team timezone setting or linked venue (that is shown 4 times per teamevent entry)
[00:38] <mhall119> ?
[00:38] <mhall119> ah, there we go
[00:39] <Ronnie> posted the wrong link. this is the corrent one: http://localhost:8000/events/history/
[00:40] <mhall119> and a select_related on line 72 of meetings/models.py won't help us here?
[00:42] <Ronnie> mhall119: what would you select als related ?
[00:42] <mhall119> the 'teams' field from TeamMeeting
[00:43] <Ronnie> select_related does not select O2Many relations. only O2O and ForeinKeys
[00:45] <mhall119> oh right, it's a M2M
[00:45] <Ronnie> thats the whole problem. and the teamevent.teams is called several times per teamevent
[00:46] <mhall119> right, which sucks because it's almost always going to be only one Team
[00:52] <Ronnie> i got it down to 1817 queries
[00:53] <Ronnie> somehow we should limit per team or month basis
[00:53] <Ronnie> mhall119: whats the point of having a page with all the past meetings ?
[01:20] <svwilliams> this is all so similar to stuff I use every day for work and yet so different
[01:20] <svwilliams> anyone have a good suggestion for a python/dijango tutorial?
[01:21] <svwilliams> maybe a walk through that you build something?
[01:43] <mhall119> svwilliams: the django website had a good 4-part tutorial
[01:44] <mhall119> svwilliams: https://docs.djangoproject.com/en/1.3/intro/tutorial01/
[01:45] <mhall119> Ronnie: I don't recall what the reason was, I think so that people could see what was done in the last month, etc, for UWN
[01:46] <mhall119> I think limiting it to a month at a time is reasonable though
[01:48] <svwilliams> I saw that mhall119 but I thought I'd ask, always good to get peoples opinions who have used the tutorials
[01:48] <svwilliams> I'll give it a try
[01:50] <mhall119> svwilliams: that's how I learned
[02:03] <nigelb> That's how I learned as well.
[02:03] <nigelb> Its interesting that I've never worked on a django project at the start
[02:03] <nigelb> I've always come in between and did lots of stuff
[02:24] <doctormo-other> nigelb: I tried to make a website, although to be fair I came to django because it contained the majority of the functionality I put into PCWE back in 2002
[02:25] <doctormo-other> It has frustrated me no end to have fairly poorly structured templating engines compared to the perl library I have. I mean django only just in 2011 got conditional element parsing.
[02:28] <nigelb> doctormo-other: heh, personally, I like jinja2 compared to django's templating engine.
[02:30] <doctormo-other> Yeah, nigelb I also sit on a hoard of other code that other projects will never really take advantage of.
[02:30] <doctormo-other> But learning code seems a lot more about popularity than technical ability these days.
[02:34]  * nigelb heads out
[10:32] <knome> is there a way to get a table with all cell borders in the ubuntu wiki?
[11:29] <doctormo-other> knome: Yes, see the table/cell style guide for moin wiki
[11:30] <knome> doctormo-other, i looked at that, but if you want all borders, you have to set those for every cell.
[11:30] <doctormo-other> Yes, and now you know why people write websites in html ;-)
[11:35] <knome> yeah well
[11:35] <knome> https://bugs.launchpad.net/ubuntu-website/+bug/889776
[11:35] <ubot4> Launchpad bug 889776 in ubuntu-website "Enable a CSS class for tables for better readability (affects: 2) (heat: 10)" [Undecided,New]
[11:35] <knome> if one could have a css class in the stylesheet, and just apply that for a table that needs borders...
[11:35] <knome> it would be *much* less work.
[11:36] <knome> imo that should be the default, but even something i have to manually set would be better than editing per-cell
[11:43] <doctormo-other> knome: You could, but it would mean editing the moinmoin and getting Canonical IS to redeploy it. Impossible!
[11:44] <knome> i know.
[11:44] <knome> but i've been bugging them too much already.
[11:44] <knome> i will not make their lives easy.
[11:45] <knome> i've been telling in my blog they are waayyyy suboptimal
[11:45] <knome> i will bug them eternally.
[12:33] <cjohnston> is there a way to figure out what is using a certain port
[12:41] <nigelb> yup
[12:42] <cjohnston> nm
[16:48] <cjohnston> daker: i replied again
[19:38] <cjohnston> mhall119: do you have the lp>u.c sso script?
[21:03] <mhall119> cjohnston: https://pastebin.canonical.com/55702/
[21:04] <mhall119> cjohnston: you can also reference https://wiki.canonical.com/InformationInfrastructure/ISD/Docs/SSO/MigratingFromLaunchpadLogin in the email to IS
[23:15] <knome> what's the status of team reporting? is that dead?