2006-07-14T09:03:37  <richardb> ThomasWaldmann?
2006-07-14T09:04:43  <Kepplar> moin
2006-07-14T09:04:59  <richardb> Hi.
2006-07-14T09:05:09  <richardb> Seen ThomasWaldmann around today?
2006-07-14T09:06:36  <ThomasWaldmann> i am here
2006-07-14T09:07:01  <richardb> aha!
2006-07-14T10:20:37  <ThomasWaldmann> http://moinmoin.wikiwikiweb.de/GoogleSoc2006/BetterProgress SOC students and mentors please READ this.
2006-07-14T10:20:40  <ThomasWaldmann> bbl
2006-07-14T10:39:15  <Kepplar> i would if the server wasnt down
2006-07-14T10:45:10  <Kepplar> ThomasWaldmann: i strongly disagree with your mentality regarding the page
2006-07-14T10:45:48  <Kepplar> I dont know about Germany but in the UK if an employer wanted me to work 7 days a week they would either have to be paying me ALOT of money
2006-07-14T10:45:58  <Kepplar> Everyone needs a break
2006-07-14T10:46:30  <Kepplar> I think I can sufficiantly say that I speak for everyone when I say that 5 days a week as a requirement is fine, but 7 is plain unreasonable
2006-07-14T10:47:19  <Kepplar> oh hold on
2006-07-14T10:47:20  <Kepplar> sorry
2006-07-14T10:47:23  <Kepplar> i misread the page entirely
2006-07-14T10:47:36  <Kepplar> (dyxlexia is bad :( )
2006-07-14T10:48:57  <Kepplar> ThomasWaldmann: if you want my honest opinion i think you're coming across a tad paranoid =)
2006-07-14T10:58:12  <mvirkkil> ThomasWaldmann: You might want to change the wording on "we get the impression that SOC was not your main summer full-time activity (meaning you work on it like you would for another paid fulltime job), this will get a problem for you." since now it says "if you just work on this as another paid fulltime job, you will be in trouble".
2006-07-14T10:58:56  <ThomasWaldmann> Kepplar: nobody speaks about 7 days a week
2006-07-14T10:59:05  <Kepplar> ThomasWaldmann: yes yes, i misread, sorry =)
2006-07-14T10:59:40  <Kepplar> tbh i do spent alot of my time reading existing code
2006-07-14T10:59:59  <Kepplar> im now preping for integration and the likes
2006-07-14T11:00:04  <ThomasWaldmann> well, document that in CHANGES.*, this is expected in your case an no problem
2006-07-14T11:00:22  <Kepplar> will do
2006-07-14T11:21:22  * Kepplar quashes all storage bugs
2006-07-14T11:45:47  <Kepplar> hey ThomasWaldmann for imports i have to put the directory in too right?
2006-07-14T11:46:01  <Kepplar> for MoinMoin import storage.storage storage.flatfile ?
2006-07-14T11:46:04  <Kepplar> from*
2006-07-14T12:53:30  <Kepplar> Ok
2006-07-14T12:53:54  <Kepplar> SEM now has retrieve_exisiting_item() and create_new_item()
2006-07-14T12:54:22  <Kepplar> mainly because having it in one operation with it auto-creating directories and the likes is a bit crap
2006-07-14T12:54:34  <Kepplar> eliminates potential misuse
2006-07-14T12:54:55  <Kepplar> howevr the actual CREATION of a new item on the storage layer
2006-07-14T12:55:07  <Kepplar> will now only occour onces commit/add a revision for that item
2006-07-14T12:59:44  <Kepplar> hmm
2006-07-14T12:59:48  <Kepplar> unless we dont bother
2006-07-14T12:59:48  <Kepplar> hmm
2006-07-14T12:59:53  <Kepplar> ill think it over
2006-07-14T13:10:54  <Kepplar> ok
2006-07-14T13:11:11  <Kepplar> everything hinges on getting this exeption from access_storage sorted
2006-07-14T13:11:35  <Kepplar> with it implemtned, changes will cascade back and i can handle the creation of new revisiona and new wikinames (almost)
2006-07-14T13:14:05  <Kepplar> ThomasWaldmann: for im going to be reading more detail about exceptions this afternoon
2006-07-14T13:14:17  <Kepplar> ThomasWaldmann: ive also made some changes to the test cases
2006-07-14T13:14:29  <Kepplar> but they are stuck until i get this exception ironed out
2006-07-14T16:16:20  <Kepplar> Hmm
2006-07-14T16:16:21  <Kepplar> ok
2006-07-14T16:16:31  <Kepplar> i got a good iea for an exception architecture
2006-07-14T16:16:35  <Kepplar> i just need to map everything out
2006-07-14T16:19:23  <ThomasWaldmann> Kepplar: it is "from MoinMoin.storage import storage, flatfile"
2006-07-14T16:21:01  <ThomasWaldmann> btw, if storage.py is general stuff, it maybe could also be in storage/__init__.py
2006-07-14T16:23:05  <Kepplar> __init__.py is for?
2006-07-14T16:24:08  <Kepplar> Question. Should flatfile (read: any storage implementation) handle IOError from write/read/nonexistantfiles/etc by itself, or let the abstract engines calls handle it?
2006-07-14T16:24:15  <Kepplar> or
2006-07-14T16:24:20  <Kepplar> we write out own exception object
2006-07-14T16:24:23  <Kepplar> which makes more sense
2006-07-14T16:24:31  <Kepplar> as sql and stuff probably wont throw IOError
2006-07-14T16:24:42  <Kepplar> and the guy implementing the stroage engine will need to raise it manaually
2006-07-14T16:25:08  <Kepplar> I need to get the exception handled (either directly or recieving a false back from it handled further up the line)
2006-07-14T16:25:22  <Kepplar> from the storage implementation retrival
2006-07-14T16:25:39  <Kepplar> well
2006-07-14T16:25:40  <Kepplar> add
2006-07-14T16:25:42  <Kepplar> basically
2006-07-14T16:25:46  <Kepplar> when you add a revision
2006-07-14T16:25:50  <Kepplar> it needs to check if something exisits
2006-07-14T16:32:23  <ThomasWaldmann> Kepplar: it is the package initialization. You just do "from MoinMoin import storage" and then everything in __init__ will be accessable by storage.whatever
2006-07-14T18:22:32  <Kepplar> ah ok
2006-07-14T18:22:33  <Kepplar> ill do that
2006-07-14T18:22:34  <Kepplar> then

MoinMoin: MoinMoinChat/Logs/moin-dev/2006-07-14 (last edited 2007-10-29 19:08:34 by localhost)