[04:57] <lotuspsychje> good morning to all
[07:15] <ducasse> good morning
[08:07] <lotuspsychje> hey ducasse
[08:20] <ducasse> hi lotuspsychje
[08:20] <ducasse> how are you today?
[08:20] <lotuspsychje> fine mate, just had breakfast
[08:22] <ducasse> haven't gotten that far yet here :)
[08:22] <lotuspsychje> hehe
[08:30] <lotuspsychje> ok prepare for work again..
[08:30] <lotuspsychje> ttyl guys :p
[08:31] <ducasse> ttyl
[08:31] <lotuspsychje> have a nice1 ducasse
[12:45] <BluesKaj> Hi folks
[17:28] <nacc> TJ-: finally figured out the u-s-s stuff we were talking about
[17:29] <nacc> TJ-: supported by community is not all of universe
[17:29] <nacc> it's stuff that specifically has teams signed up to support them
[17:29] <nacc> so there's a subset of universe that is not that way
[17:29] <nacc> and therefore is 'unsupported'
[17:30] <TJ-> Yes, I've been watching the discussion
[17:30] <TJ-> I still think the word 'supported' is wrong; it should be 'maintained'
[17:47] <nacc> right
[19:18] <TJ-> nacc: do you happen to know if there's an easy way to access all Python "@property"s with a single 'print()' or similar - I'm looking at u-s-s and wanting to print all the available properties of the apt.Version() class ( from python-apt) in the for pkg in apt.Cache loop
[19:22] <nacc> TJ-: dir() ?
[19:22] <nacc> TJ-: there's also vars()
[19:23] <TJ-> Yes, I was trying var() but only getting changelog objects ;p
[19:25] <TJ-> ahhh, maybe I've got to drill down the _pkg
[19:25] <TJ-> no worries, I can see the light now
[19:35] <nacc> TJ-: cool