*** lenscape_ has joined #europython | 00:33 | |
*** voidspace has quit IRC | 01:03 | |
*** fuzzyman has joined #europython | 01:07 | |
*** lenscape_ has quit IRC | 01:40 | |
*** Tv has quit IRC | 04:19 | |
*** Tv has joined #europython | 07:44 | |
*** onyame has joined #europython | 08:02 | |
*** onyame has quit IRC | 08:16 | |
*** onyame has joined #europython | 08:49 | |
*** mgedmin has joined #europython | 11:08 | |
*** onyame has quit IRC | 12:02 | |
*** MrTopf has joined #europython | 12:46 | |
*** Aiste has joined #europython | 14:41 | |
*** lac has joined #europython | 16:23 | |
*** Aiste has quit IRC | 17:11 | |
*** TheSheep has left #europython | 18:08 | |
*** onyame has joined #europython | 19:55 | |
*** mgedmin has quit IRC | 20:11 | |
*** Tv has quit IRC | 20:14 | |
*** pedronis has joined #europython | 20:44 | |
*** Tv has joined #europython | 20:54 | |
*** MrTopf has quit IRC | 20:56 | |
*** ThomasWaldmann is now known as MoinMoin_ThomasW | 21:08 | |
*** MoinMoin_ThomasW is now known as moin_ThomasWaldm | 21:10 | |
*** moin_ThomasWaldm is now known as moin_ThomasW | 21:10 | |
*** pedronis has quit IRC | 21:15 | |
*** Tartley has joined #europython | 21:39 | |
Tartley | lac: hello hello, sorry I'm a little late, just got home | 21:40 |
---|---|---|
lac | hi there | 21:57 |
lac | do you have time this evening for more talk approving? | 21:57 |
*** lac has quit IRC | 22:02 | |
*** lac has joined #europython | 22:02 | |
lac | back | 22:05 |
Tartley | hi lac | 22:05 |
Tartley | how you doing?> | 22:05 |
lac | better than last night, at any rate | 22:07 |
Tartley | glad to hear it | 22:07 |
Tartley | you ready to rock and roll. I'm just opening all my windows. | 22:07 |
Tartley | Is there an easy way to bind a command to reopen windows and documents in a previously stored configuration | 22:08 |
Tartley | alright | 22:08 |
lac | are you using firefox? | 22:08 |
Tartley | we always forget to do an endmeeting | 22:08 |
lac | oh dear. | 22:08 |
Tartley | I am I guess. Can save all tabs, huh? Nice idea. I have a zillion others open too though. may have to rethink my workflow on that. | 22:08 |
lac | are you using ubiquity? | 22:09 |
Tartley | i am not, i don't even know what it is | 22:10 |
lac | aha. I hve just started using it. | 22:10 |
lac | It is a new thing from Mozilla Labs -- Aza Jono and Atul, basically | 22:11 |
lac | https://wiki.mozilla.org/Labs/Ubiquity/Latest_Ubiquity_User_Tutorial | 22:11 |
lac | see | 22:11 |
Tartley | thanks, I'll read all about it after | 22:11 |
lac | I think that it has what you are looking for. | 22:11 |
Tartley | but for now, we're at: | 22:12 |
lac | But I am not sure yet since I am only half way through the tutorial today | 22:12 |
Tartley | lac22 | 22:12 |
Tartley | tartley21 | 22:12 |
Tartley | qwright & pinner4 | 22:12 |
Tartley | qwright2 | 22:12 |
Tartley | pinner4 | 22:12 |
Tartley | moreati1 | 22:12 |
Tartley | should we do | 22:12 |
Tartley | #endmeeting | 22:12 |
Tartley | #startmeeting | 22:12 |
Tartley | ? | 22:12 |
lac | I think so | 22:12 |
Tartley | PRESENT | 22:12 |
lac | PRESENT | 22:12 |
Tartley | I believe we just finished search with python and xapian? | 22:12 |
Tartley | I have it noted down as taken by you? | 22:13 |
Tartley | oh no, we also did zen of web, accepted by me | 22:13 |
Tartley | so, Byte Coat? | 22:13 |
Tartley | TOPIC 57Compiling Python with Byte Coat | 22:13 |
lac | I've never heard of this before | 22:15 |
lac | my big question is 'who wants this for what?* | 22:15 |
lac | is this code obsfuscation? or .... | 22:16 |
Tartley | me neither, sounds interesting, but I think it is obfustication, yes. Which turns me off, but that's just my biases, it's clearly a topic that's important to some people | 22:16 |
lac | ok, I think we can accept this one even though it runs against both of our biases | 22:17 |
Tartley | if this work reveals things that might be applicable to the compilation-for-performance crowd too, then so much the better | 22:17 |
Tartley | yes | 22:17 |
lac | but maybe we should ask what is the intended use case? | 22:17 |
Tartley | I'm lagging a little, so I'll take it unless you're crazy to. Fair point, I'll ask him to clarify that | 22:18 |
lac | ok | 22:18 |
lac | and that great lag is one talk, I think :) | 22:18 |
Tartley | DECISION: Accept 57Compiling Python with Byte Coat, assign to tartley, ask him to clarify intended use cases | 22:18 |
lac | terrific | 22:18 |
Tartley | TOPIC PLY and PyParsing | 22:19 |
lac | I am biased about that one, as Andrew did that work while he was living at my house. or some of it at any rate. | 22:19 |
lac | so I think it is neat stuff. | 22:19 |
Tartley | certainly, it's a perennially interesting and useful topic | 22:20 |
Tartley | great stuff | 22:20 |
lac | I understand it perfectly, so I don't think it needs any changes to the abstract. And Andrew knows how long the talk takes | 22:21 |
lac | do you see any way to improve it? | 22:21 |
Tartley | alright, that seems just fine to me. No I think it makes it very clear what the content of the talk will be, and what attendees will ge tout of it. | 22:21 |
Tartley | woulld you like to take it then, since you know Andrew? | 22:22 |
lac | certainly. | 22:22 |
Tartley | DECISION Accept PLY and PyParsing, assign to lac, no amendments needed. | 22:22 |
*** moin_ThomasW is now known as ThomasWaldmann | 22:23 | |
Tartley | TOPIC Automated testing with Python | 22:23 |
lac | Hi Thomas | 22:23 |
lac | This is a tutorial. Holger has given it before and knows what he is doing. | 22:23 |
lac | I think many people would like to take it. | 22:23 |
Tartley | yes indeed. testing is good. | 22:24 |
lac | :) | 22:24 |
Tartley | alright, if you know Holger and he knows his stuff, then I think we can accept this as it is? | 22:25 |
Tartley | Shall I take this one? Or do you want it if you know him? | 22:25 |
lac | Doesn't matter to me, but I do talk to him regularly. | 22:25 |
Tartley | ok then, I'll toss it to you. | 22:26 |
lac | thank you. | 22:26 |
Tartley | DECISION Accept Automated testing with Python, assign to lac, no amendments needed. | 22:26 |
Tartley | TOPIC Python Foundation Class | 22:27 |
Tartley | ahar! another Pinner entry! | 22:27 |
lac | can we find a way to improve this one? | 22:27 |
lac | yes, expand it more. | 22:28 |
*** CMooney has joined #europython | 22:28 | |
Tartley | you think that for a full day, the content in the abstract could be more fleshed out? | 22:29 |
Tartley | that's not unreasonable | 22:29 |
Tartley | can we simply toss over the wall by assigning to john himself again then? | 22:30 |
lac | What I mostly think is that it is not clear how much python you need to already know before this tutorial will not teach you much new | 22:30 |
lac | I think so, yes | 22:30 |
Tartley | that seems sensible. Could a complete newbie manage? | 22:30 |
Tartley | alright | 22:30 |
lac | thats one end, and could somebody who knows Java very well, but python not, be ok with this? | 22:31 |
lac | vs somebody for whom programming is a pretty new thing altogether? | 22:31 |
lac | What about that Lithuanian guy who is moving from php -- I suspect he should attend this, but its not clear from what John has written | 22:32 |
CMooney | I'm a complete newbie with Python, send it my way and I'll give you my opinion! | 22:32 |
Tartley | DECISION: Accept Python Foundation Class, assign to JohnP in his absence, suggest abstract includes more detail about what is covered, and prerequisite knowledge for attendees - could a Jave expert with no Python keep up? How about a complete programming newbie? | 22:32 |
CMooney | Apologies, Didn't realise I've dropped into the middle of a meeting. | 22:33 |
Tartley | that's ok | 22:33 |
Tartley | hi! how you doing? | 22:33 |
Tartley | :-) | 22:33 |
lac | CMooney: no problem. | 22:33 |
CMooney | Not too bad. | 22:33 |
CMooney | Trying to procrastinate from other important things. IRC is good for that. | 22:33 |
Tartley | topic Advanced automated testing | 22:34 |
Tartley | TOPIC Advanced automated testing | 22:34 |
Tartley | ah | 22:34 |
Tartley | so this is the second of two | 22:35 |
lac | yes | 22:35 |
Tartley | the first half day tutorial is next | 22:35 |
lac | I've changed the title | 22:35 |
lac | no, 62 is a talk | 22:36 |
Tartley | sorry, I meant te first half is no 59 | 22:36 |
lac | this is the tutorial, first is 59 | 22:36 |
Tartley | right | 22:36 |
* lac nods happily | 22:36 | |
Tartley | got it now | 22:36 |
Tartley | should we rename 59 to 'with py.test', instead of 'with Python' | 22:37 |
Tartley | to make it clearer that are associated tutorials about the same thing | 22:37 |
Tartley | oh | 22:37 |
lac | yes | 22:37 |
Tartley | maybe not though, 59 seems to be a little broader than just py.test | 22:38 |
lac | I just changed it. | 22:38 |
Tartley | well. maybe it would be ok. I think 59 is 'using py.test to run - oh. ok. | 22:38 |
Tartley | :-) | 22:38 |
lac | I think that the first tutorial would work fine with nose as well | 22:39 |
lac | but the second one won't | 22:39 |
lac | But I say accept them all, and assign them to me. | 22:40 |
Tartley | seems fair enough. fixing a minor doublespace issue on 61, in description | 22:40 |
lac | It is hard for me to see how clear the proposals are, since I use py,test all the time, so of course it sounds clear to me | 22:41 |
lac | what do you think? | 22:41 |
Tartley | I've never touched py.test, and they sound fine to me. (although I do a lot of testing using plain old unittest) | 22:41 |
lac | ok, assign them to me then and I will talk to npk | 22:42 |
lac | er hpk | 22:42 |
lac | (npk is Näset PaddlarKlubb -- the kayak club. I talk to them a lot, too. :) ) | 22:43 |
Tartley | ok. and 62 too? | 22:43 |
lac | or at least think of them a lot. | 22:43 |
lac | yes please. | 22:43 |
Tartley | hey, how did that go then? have fun the other day? | 22:43 |
Tartley | DECISION Accept all of Holger's testing talks and tutorials, assign to lac, no specific improvements required | 22:45 |
lac | including 63 | 22:45 |
Tartley | TOPIC distributed programming, easy. | 22:45 |
Tartley | ah | 22:45 |
lac | where I changed the title? | 22:45 |
lac | and I think needs some work? | 22:45 |
Tartley | ok. I marked 63 as accepted by you | 22:46 |
Tartley | but for the record, the abstract needs work? | 22:46 |
lac | yes | 22:46 |
lac | what is py.execnet and who can use it | 22:47 |
lac | this is not py.test specific, but hpk doesn't make that clear | 22:47 |
lac | and you can use it for deploying pretty much anything, but that is not clear as well | 22:47 |
Tartley | ok, I didn't know it was related to py.test. I think for someone who doesn't know about py.test there is no reason to think they are related | 22:48 |
lac | ah. well up until last week you had to dl py.test to get it, so lots of people think that. | 22:48 |
Tartley | alright fair enough | 22:48 |
Tartley | and the title, is the 'easy' some sort of pun or reference to something? If not, I'd like to change that. | 22:49 |
Tartley | if only 'made easy' | 22:49 |
Tartley | but maybe could mention py.execnet in the title | 22:50 |
Tartley | or abstract | 22:50 |
Tartley | alright, I'll paste this into the review comments, and we can move on | 22:50 |
Tartley | DECISION, accept distributed programming, easy, assign to lac, with discussed minor improvements to abstract, desc, title. | 22:50 |
Tartley | TOPIC First class JavaScript testing | 22:51 |
lac | I have to withdraw from voting on this one. Clearly I think it is very, very, very cool | 22:52 |
Tartley | ah, you do, I haven't spotted the connection, sorry I'm not very in the know. | 22:53 |
lac | and we're going to open source it some time in May, after our release is done. | 22:53 |
Tartley | ? | 22:53 |
lac | So I think that Samuele should explain things a bit more | 22:53 |
Tartley | alright, fair enough. | 22:54 |
lac | Its not clear, I think, what makes this different from what already exists. Why we wrote this thing. | 22:54 |
lac | It may turn out to be more useful than our app, actually. | 22:54 |
lac | and assuming you vote it in, you can assign it to me for sure. | 22:55 |
Tartley | ok then. It certainly sounds like a talk on a great topic by someone who knows all about it, so yes it's voted in (hooray!) | 22:55 |
Tartley | and I'm happy to you with your insight that it could be better explained - although the explination as it stands seems pretty good to me | 22:56 |
Tartley | presumably client side javascript will only increase in usage, so this will become more imortant going fwd | 22:56 |
Tartley | alrighgt | 22:57 |
lac | Ok. | 22:57 |
Tartley | DECISION Accept First class JavaScript testing, assign to lac, she has some ideas for improving the abstract | 22:57 |
*** CMooney has quit IRC | 22:57 | |
Tartley | TOPIC A better Python for the JVM | 22:57 |
lac | This should be a great talk, did you see the PyCON USA version? | 22:59 |
Tartley | he's given it before at PyCon - in your mind presumably that's a big plus because it means even if we didn't know the submittor and the project, then its reassurance that he's planned and timed and practiced the talk already | 22:59 |
Tartley | I did not | 22:59 |
Tartley | and obviously, we do know the project and submittor, so that reassurance isn't neccesary, but I'm just looking for insight into your process | 23:00 |
Tartley | :-) | 23:00 |
Tartley | alroight | 23:00 |
Tartley | sounds like a simple win then | 23:00 |
Tartley | I'll take a few to balance us up again | 23:00 |
Tartley | DECISION Accept A better Python for the JVM, assign to tartley, no fixes reqd. | 23:01 |
lac | its is a plus and a minus. | 23:02 |
Tartley | TOPIC PyPy - complete and fast | 23:02 |
lac | on the plus side, yes, we can even see it at a blip.tv thing | 23:02 |
lac | and see that the talk is good. | 23:02 |
lac | on the minus, well, we can already see it on blip tv so who needs to see it again? | 23:03 |
Tartley | right. fair enough. makes sense, thanks | 23:03 |
lac | except that this work is progressing at a rapid clip | 23:03 |
lac | so it won't be the same talk | 23:03 |
lac | it can feature 'what we did this spring'. | 23:03 |
lac | This is one of the problems of PyCON. | 23:03 |
lac | They badly want very polished talks. | 23:04 |
lac | which means that for many of us the talks are by definition not all that interesting to us because | 23:04 |
lac | if its been around long enough to be polished, either we already know it, or we don't care. | 23:04 |
lac | its all a matter of which audience you are catering for. | 23:05 |
Tartley | right. gotcha | 23:05 |
lac | but EP is more the 'bleedging edge developers' crowd. | 23:05 |
Tartley | I guess with several tracks going on, even someone who's totally in the loop will always have several options for what to see, so you must tend to err on the side of being glad of well-rehearsed talks | 23:06 |
lac | While PyCON gets a lot of 'we want extremely reliable well established practices and code' | 23:06 |
lac | for our corporate hires whom we are sending here to learn things. | 23:06 |
Tartley | right. now you're making me SUPER excited for EP | 23:07 |
lac | :) | 23:07 |
Tartley | alright, well the abstract is very clear and detailed | 23:07 |
Tartley | I don't have anything to suggest, I think this will be brilliant | 23:08 |
lac | Me too. | 23:08 |
Tartley | excellent | 23:08 |
Tartley | DECISION Accept PyPy - complete and fast. Assign to tartley, no fixes reqd. | 23:08 |
lac | Assuming what fijal and armin are doing now with integration of the JIT really produces the fast code. | 23:09 |
lac | but they swear it is doing so now .... :) | 23:09 |
Tartley | right. It's so promising-sounding, obviously everyone hopes it all turns out well. | 23:09 |
Tartley | I can't even begin to imagine how much those guys must all know about interpretters and JITS, with all the work they've done on that project over the years | 23:10 |
Tartley | TOPIC Tapping into the Web of Data | 23:10 |
lac | Armin is coming to live in Göteborg for a few months after the Spring that is happening in Leysin now. | 23:11 |
lac | He is fantastically terrific company. I will be so glad to get to see him regularly. | 23:11 |
lac | another semantic web thing, to pair with Nicolas | 23:11 |
Tartley | ha! no doubt. I have only met some of the pypy guys a handful of times, but they are a brilliant bunch, in evey sense. | 23:13 |
Tartley | I don't *think* I know Armin. | 23:13 |
Tartley | Alright | 23:13 |
Tartley | um | 23:13 |
lac | Well, make sure I introduce you at EP then. | 23:14 |
Tartley | excellent! thanks! | 23:14 |
Tartley | Well, talk 67 sounds great. | 23:14 |
Tartley | I don't spot any oversights | 23:14 |
Tartley | seems very sensibly described | 23:15 |
Tartley | I saw we accept it | 23:15 |
Tartley | :-) | 23:15 |
lac | me too. | 23:15 |
Tartley | s/saw/say | 23:15 |
Tartley | DECISION: Accept Tapping into the Web of Data, assign to tartley, no fixes reqd | 23:15 |
Tartley | TOPIC Castles in the Cloud | 23:16 |
lac | looks like a real good talk to me. and should be very popular. | 23:17 |
Tartley | yes indeed, I am salivating over it | 23:17 |
Tartley | Alright, accept? Hooray! | 23:18 |
lac | yes. | 23:18 |
Tartley | DECISION Accept Castles in the Cloud, assign to tartley, no fixes reqd. | 23:18 |
lac | :) | 23:18 |
Tartley | I was waiting over the ENTER key | 23:18 |
Tartley | :-) | 23:18 |
Tartley | TOPIC Ctypes Tips & Techniques | 23:19 |
Tartley | oooh | 23:19 |
Tartley | I've been wrestling with ctypes a bunch for the first time lately | 23:19 |
Tartley | intruiging | 23:19 |
Tartley | lots I don't know about it | 23:19 |
lac | We used it for PyPy so we found out lots of odd things about it. Some of our unit tests are very bizarre. :) | 23:20 |
Tartley | heh | 23:20 |
Tartley | no doubt. | 23:21 |
Tartley | my colleague William wrestles with it for IronClad (IronPython to libraries with C-extensions) | 23:21 |
Tartley | and I've paired with him on that, but had to kinda shoulder surf over parts of it | 23:21 |
Tartley | alright | 23:22 |
Tartley | well the talk sounds ace, I'm happy to accept. You have any constructive comments about it? | 23:22 |
lac | I was getting my dinner. let me read it again, | 23:22 |
Tartley | no problem | 23:22 |
lac | no, I think it is fine as it stands | 23:23 |
Tartley | excellent | 23:23 |
Tartley | DECISION Accept Ctypes Tips & Techniques, assign to tartley, no fixes reqd | 23:23 |
Tartley | we're at 28 all, on the talks tally, btw | 23:24 |
Tartley | TOPIC Python MPI | 23:24 |
lac | what is MPI? | 23:24 |
Tartley | needs to expand MPI | 23:25 |
Tartley | ha | 23:25 |
lac | multi processing? | 23:25 |
Tartley | Message Passing Interface | 23:25 |
Tartley | ? | 23:25 |
Tartley | google says | 23:25 |
lac | aha. | 23:25 |
Tartley | so interprocess communication? | 23:25 |
lac | says to me too | 23:25 |
Tartley | right, so it needs more clarity on what mpi is and who you would want to use it | 23:26 |
Tartley | s/who/why | 23:27 |
* lac nods | 23:27 | |
Tartley | fair enouhg | 23:27 |
lac | Just a sentence. The talk aparantly goes into this in detail | 23:27 |
Tartley | otherwise sounds like a worthy topic and would be great. | 23:27 |
Tartley | excellent | 23:27 |
lac | but we needs something so people can find out if they belong in the talk. | 23:27 |
Tartley | right | 23:27 |
lac | s/in/at/ | 23:28 |
Tartley | alright | 23:28 |
Tartley | well, shall I take it? | 23:28 |
Tartley | otherwise we accept? | 23:28 |
lac | yes, and for you since you got his other one. | 23:28 |
Tartley | DECISION Accept Python MPI, assign to tartley, clarification about what MPI and why you would use it needed | 23:29 |
Tartley | Data Processing with MDP | 23:30 |
Tartley | TOPIC Data Processing with MDP | 23:30 |
lac | same comment as the last one. We need the abstract something that will tell people who have never heard of MDP whether they should be in this talk or not. | 23:31 |
lac | s/in/at/ | 23:31 |
Tartley | fair enough | 23:31 |
lac | wow, that is twice. | 23:31 |
Tartley | heh. | 23:31 |
Tartley | alright, but with that minor caveat this sounds like a great talk, I'm all for accepting it all over | 23:32 |
lac | indeed. :) | 23:32 |
Tartley | Oh, whose? Your turn? | 23:32 |
*** lenscape_ has joined #europython | 23:32 | |
lac | mine I believe | 23:33 |
Tartley | DECISON Accept Data Processing with MDP, assign to LAC, minor clarification about what MDP is and why one would use it | 23:33 |
Tartley | TOPIC The MOAI Server | 23:33 |
lac | I am all for taking out the first paragraph of the abstract and calling that the description | 23:34 |
Tartley | Sounds good. Is it missing an expansion of MOAI itself? | 23:34 |
lac | yes, if it is an acronym, which it probably is. | 23:35 |
Tartley | Alright, it needs that, and I just fixed 'facilities' | 23:36 |
lac | :) | 23:36 |
Tartley | we need to answer his question about adding a second presenter. | 23:37 |
lac | yes, tomorrow when john makes it easier? | 23:37 |
Tartley | I wonder if there is any way to slant the description to make the appeal broader | 23:37 |
Tartley | it focusses (rightly) on the library metadata application at hand. | 23:38 |
Tartley | Which is good - to be specific | 23:38 |
Tartley | But Is there any mileage in describing this as an example of something more broad | 23:38 |
lac | library metatdats really is a world in itself. Sometimes, often even, the protocals that librarians have are | 23:38 |
lac | better than the ones that programmers invent. | 23:39 |
lac | so maybe that is worth asking. | 23:39 |
Tartley | heh | 23:39 |
lac | protocols | 23:39 |
Tartley | heh, alright. | 23:39 |
lac | Jacob used to work for the Royal Library and still is the Swedish expert on library standards. I will ask him when we | 23:39 |
Tartley | maybe he could include some note along those lines, to entice people in who aren't even library people | 23:39 |
lac | are done wiht this. | 23:39 |
Tartley | alrighty | 23:40 |
Tartley | with those comments I vote to accept | 23:40 |
lac | see what he says. | 23:40 |
lac | me too. | 23:40 |
lac | and you can leave it with me, which means I am only one behind now, I think. | 23:40 |
Tartley | DECISION Accept The MOAI Server, assign to lac, minor description tweaks as discussed. | 23:41 |
Tartley | TOPIC Lipstick on a Pig | 23:41 |
lac | Love the title. | 23:42 |
Tartley | wow. I'm amazed by the project | 23:43 |
lac | me too. | 23:43 |
Tartley | sort of real-world messy problem that would send me running | 23:43 |
lac | I hope they were well paid for it. | 23:43 |
Tartley | heh | 23:44 |
lac | you get him since you got his ZPT talks as well, ok? | 23:45 |
Tartley | alright, no quibbles from me, I'm happy to accept | 23:45 |
lac | talk | 23:45 |
Tartley | I ifixed a few capitalisation issues | 23:45 |
Tartley | all good | 23:46 |
Tartley | thanks for keeping track of that | 23:46 |
Tartley | DECISION Accept Lipstick on a Pig, assign to tartley, no fixes reqd | 23:46 |
Tartley | TOPIC 74Loving old versions of Python. | 23:47 |
lac | seems straightforward | 23:47 |
lac | good match for talk #77 | 23:47 |
Tartley | yes indeed. Does he need to clarify what some of the benefits are, above the single word 'compatability' | 23:49 |
Tartley | ? | 23:49 |
lac | probably a good idea. | 23:49 |
Tartley | I wonder if a brief sentence about that might hook more people who otherwise think 'why would i care? | 23:49 |
* lac agrees | 23:50 | |
Tartley | ok | 23:50 |
Tartley | othewise brilliant | 23:50 |
lac | I can take this one. I think you are ahead | 23:50 |
Tartley | let's get it on the acceptance train | 23:50 |
Tartley | i think we're even, by my spready | 23:50 |
Tartley | but ok | 23:50 |
Tartley | :-) | 23:50 |
lac | and you're the spreadsheet expert company, :) | 23:50 |
Tartley | DECISION Accept Loving old versions of Python, assign to lac, ask for brief sentence describing what the benefits are. | 23:51 |
Tartley | heh, yes, supposed to be | 23:51 |
Tartley | thing about that is | 23:51 |
Tartley | we set out to be not spreadsheet like - make something which lets you make mathematical models without all the snafus that spreadsheets introduce | 23:51 |
Tartley | a mathematica for finance, if you will | 23:51 |
Tartley | but you stick something in front of finance people, they want it to look like a spreadsheet | 23:52 |
Tartley | ohdear | 23:52 |
Tartley | so we've grudgingly converged | 23:52 |
lac | I saw a sudoku program written as a spreadsheet once. | 23:53 |
lac | amazing thing. | 23:53 |
lac | but you wonder if the guy who wrote it wouldn't have been happier taking a month to learn python instead .... | 23:53 |
Tartley | ha! my boss giles made one in resolver! Not such a co-incidence, I guess me and my colleagues have made a lot of spreadsheets over the last couple of years | 23:53 |
lac | quite understandable. | 23:54 |
Tartley | I know this is going to be tantelising, but apparently I'm having dinner made for me (fancy!) and it sounds like it's just about ready | 23:54 |
Tartley | can we adjourn? | 23:54 |
lac | There are some european governments who are running on spreadsheets that are many decades old. Nobody understnads them. and everbpdy is terrifed to change them. | 23:54 |
lac | Certainly. | 23:55 |
lac | if you tell me what is for dinner | 23:55 |
Tartley | ohgod, I've seen so many bad spreadys in the private sector, I hadn't even begun to think about govt work | 23:55 |
Tartley | ahar | 23:55 |
Tartley | we're having an omlette with veggies in it, because it was quick'n'easy | 23:55 |
Tartley | smells DELICIOUS | 23:55 |
Tartley | because we | 23:55 |
Tartley | we're both starving! | 23:55 |
lac | sounds great, and thank you | 23:56 |
Tartley | I did some local govt work, but managed to avoid the spreadys by focusing on GIS | 23:56 |
Tartley | and thank you too! | 23:56 |
lac | and remember to end the meeting ,,,,,, | 23:56 |
Tartley | always a pleasure! | 23:56 |
Tartley | yay! | 23:56 |
Tartley | #endmeeting | 23:56 |
lac | yippee | 23:56 |
lac | take afe enjoy dinner, we will kill the rest of them tomorrow. | 23:56 |
lac | er care | 23:56 |
Tartley | alright. sounds good, thanks Laura! | 23:56 |
*** Tartley has quit IRC | 23:57 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!