IRC log for #storm on 20071118

00:00.17*** join/#storm wallflower (n=wallflow@ip-205-246-113-216.pool.grokthis.net)
00:30.11*** join/#storm Key_Gena (i=lok@gateway/tor/x-c76196cbd9b6b9e4)
01:39.02*** join/#storm Key_Gena (i=lok@gateway/tor/x-ca6e04faf45fea25)
02:57.14*** join/#storm pyCube_ (n=jmayfiel@ip72-208-138-205.ph.ph.cox.net)
05:58.22*** join/#storm pyCube (n=jmayfiel@ip72-208-138-205.ph.ph.cox.net)
07:35.39*** join/#storm pyCube_ (n=jmayfiel@ip72-208-138-205.ph.ph.cox.net)
07:43.33*** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at)
09:26.31*** join/#storm EnTeQuAk (n=EnTeQuAk@dslb-088-072-217-083.pools.arcor-ip.net)
10:23.31*** join/#storm EnTeQuAk (n=EnTeQuAk@dslb-088-072-217-083.pools.arcor-ip.net)
10:30.57*** join/#storm Fujitsu (n=fujitsu@ubuntu/member/fujitsu)
11:08.07*** join/#storm EnTeQuAk_ (n=EnTeQuAk@dslb-088-074-040-011.pools.arcor-ip.net)
11:15.40*** join/#storm EnTeQuAk (n=EnTeQuAk@dslb-088-074-040-011.pools.arcor-ip.net)
11:21.31*** join/#storm dotz (n=dotz@chello089078004026.chello.pl)
11:23.48*** join/#storm Fujitsu (n=fujitsu@ubuntu/member/fujitsu)
11:42.57*** join/#storm bozzo (n=bozzo@BSN-210-226-120.dial-up.dsl.siol.net)
11:46.09*** join/#storm EnTeQuAk (n=EnTeQuAk@dslb-088-074-040-011.pools.arcor-ip.net)
12:32.55*** join/#storm Fujitsu (n=fujitsu@ubuntu/member/fujitsu)
13:18.24*** join/#storm Key_Gena (i=lok@gateway/tor/x-8c3186343d9d3206)
13:36.18*** join/#storm pyCube_ (n=jmayfiel@ip72-208-138-205.ph.ph.cox.net)
13:36.29*** join/#storm bozzo (n=bozzo@BSN-210-226-120.dial-up.dsl.siol.net)
14:08.16*** join/#storm niemeyer (n=niemeyer@200-138-134-89.ctame705.dsl.brasiltelecom.net.br)
15:03.52*** join/#storm bigdog (n=scmikes@72-197-8-8-arpa.cust.cinci.current.net)
16:33.45*** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at)
16:35.29*** join/#storm EnTeQuAk (n=EnTeQuAk@dslb-088-074-044-001.pools.arcor-ip.net)
17:48.22*** join/#storm goschtl (n=goschtl@pD9E5C6B8.dip.t-dialin.net)
17:49.02goschtlhi is there an implementation of an zope container for storm.zope ?
18:24.57*** join/#storm dobee (n=dobeee@81-223-53-162.dornbirn.xdsl-line.inode.at)
18:47.00*** join/#storm jkakar (n=jkakar@dhcp802-1-85.dsl.ucc-net.ca)
19:09.59*** join/#storm goschtl (n=goschtl@pD9E5C6B8.dip.t-dialin.net)
19:47.15*** join/#storm Key_Gena (i=lok@gateway/tor/x-bf13a85b99428474)
19:54.56*** join/#storm Zenom (n=Zenom@unaffiliated/aj1973)
20:15.25*** join/#storm dobee (n=dobeee@81-223-53-162.dornbirn.xdsl-line.inode.at)
20:44.22*** join/#storm weatherman (n=weatherm@dhcp802-1-85.dsl.ucc-net.ca)
20:44.22weathermanstorm/trunk r195 committed by gustavo@niemeyer.net
20:44.22weathermanIn the SQLite backend, ensure that we're able to recommit a
20:44.23weathermantransaction after "database is locked" errors.  Also make sure
20:44.27weathermanthat when this happens the timeout is actually the expected
20:44.31weathermanone (original patch by Richard Boulton) [r=radix,niemeyer]
20:44.54*** join/#storm goschtl (n=goschtl@pD9E5C6B8.dip.t-dialin.net)
20:45.50niemeyergoschtl: I don't think so.. the idea of a container is tightly integrated with ZODB
20:46.48niemeyergoschtl: There was someone working to integrate ZODB and Storm-based objects (he's probably here.. sorry, I forgot who was doing it)
20:47.15goschtlniemeyer: yes that it´s true. I will try to make an implementation of a container for zope.strom.
20:48.33goschtlThere is a container implementation for sqlalchemy for zope, zalchemy. I try to steal some ideas from there ;)
20:49.00niemeyergoschtl: Sweet! :-)
20:49.04niemeyergoschtl: Let me know how it goes
20:50.04goschtlniemeyer: and congrats for storm. it´s realy easy from what i have seen so far. I like the "inclass" definitions of objects..
20:58.26niemeyerTHanks :)
21:15.41weathermanstorm/trunk r196 committed by gustavo@niemeyer.net
21:15.41weathermanClose locally created stores in store tests, and also the
21:15.42weathermanconnection in database tests (reported by Ali Afshar). [trivial]
21:32.22niemeyerAlright!
21:32.28niemeyerReview queue is almost empty
21:32.56niemeyerThere are only things that need additional reviews (i.e. not from me) there
21:38.04Zenomniemeyer: good work :)
21:38.18niemeyerThanks :)
21:38.18niemeyer0.12 is coming!
21:38.22niemeyerI mean, not now.. :-)
21:38.26*** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at)
21:38.29niemeyerBut after we finish these reviews
21:40.33Zenomcool i will be upgrading, so far i have not run into any other issues
21:43.17niemeyerZenom: Good to know!
22:11.31aa_thanks for 196 :) I am using storm on windows, but now the tests actually run...
23:21.15niemeyeraa_: Ohh, that's good to know!
23:21.24niemeyeraa_: I wasn't sure if it had actually fixed it or not
23:21.35niemeyeraa_: (don't have any windows boxes around)
23:21.46niemeyeraa_: We should probably have a buildbot running on Windows now..
23:22.39niemeyeraa_: Sidnei da Silva is working on a SQL Server backend, btw
23:23.06aa_oh I'll definitely play with that when it lands
23:23.30aa_niemeyer: by the way I haven't actually tested the tests since r196
23:23.45aa_(will have to wait until I get to work in the morning, but I'll let you know)
23:24.26niemeyeraa_: Cool, thanks!
23:24.35niemeyeraa_: Hmm.. I think 196 is still the head right now
23:24.49niemeyerEven though we'll probably land a few branches soon
23:25.13aa_I am really liking storm :) and I am well known for hating everything
23:26.16niemeyerLOL
23:26.33aa_niemeyer: I still use sqlalchemy though, in one app together with storm
23:27.01niemeyeraa_: Wow.. you actually use *both* in the same project?
23:27.07aa_yeah
23:27.16aa_introspection
23:27.19niemeyerCool
23:27.37aa_sqla is a nice way of not having to use SQL
23:27.45aa_but (imo) its a really horrible ORM
23:28.35aa_in this app where I use both, sqla does automatic schema upgrading for me
23:28.56niemeyerAha, gotcha
23:29.20niemeyerIt's an interesting use case :)
23:30.14aa_for lazy people who don't want to write upgrade scripts (like me)
23:37.29jameshniemeyer: commented on the postgres socket dir support bug
23:37.37niemeyerjamesh: Cool, thank you
23:38.10jameshI still think it is a mistake to mix the socket dir and database name together
23:44.05niemeyerjamesh: Notice that the provided branch doesn't exclude the possibility of using hostnames as usual
23:44.37*** join/#storm pyCube (n=jmayfiel@ip72-208-138-205.ph.ph.cox.net)
23:44.46niemeyerjamesh: In any case, if you really think it's a mistake, I'll remove the proposal
23:46.36niemeyerDone
23:46.50jameshniemeyer: hmm.  I guess it isn't so bad, but it seems like a useless feature.
23:47.17jameshniemeyer: if it was something that users would be typing over and over, I could see it as useful
23:47.26niemeyerjamesh: Cool.. we'll have the branch there if we change our minds in the future
23:48.12niemeyerjamesh: It'd be cool to have you review on the mysql-reconnection branch, btw
23:48.18niemeyeryour
23:48.28jameshbut (a) I don't type database URIs much, and (b) passing a socket dir is only going to be attempted by few people
23:48.39jameshniemeyer: okay.
23:48.41niemeyerjamesh: Agreed
23:49.19jameshniemeyer: re. the reconnect issues in python-mysqldb, I looked at all the patches in the Ubuntu package and they all seem either useless or harmful
23:49.43niemeyerjamesh: Yeah, it's pretty bad :-(
23:49.50niemeyerjamesh: I have a big comment on this branch about that
23:49.58niemeyerjamesh: And have opened a bug against the Ubuntu package as well
23:50.22jameshniemeyer: there is another bug open about backporting 02_reconnect.dpatch to dapper too ...
23:50.30niemeyerjamesh: OUCH
23:50.34niemeyerjamesh: I'll look for it and comment
23:51.14jameshbug 64270
23:51.14ubot3Malone bug 64270 in python-mysqldb "Requesting python-mysqldb 1.2.1-p2-4ubuntu2" [Undecided,New] https://launchpad.net/bugs/64270
23:55.03niemeyerjamesh: Thanks!  I've added a comment there
23:55.32niemeyerjamesh: Btw, the other is bug 163184
23:55.33ubot3Malone bug 163184 in python-mysqldb "MySQLdb reconnect patch is harmful" [Undecided,New] https://launchpad.net/bugs/163184
23:55.38jameshyep

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.