MoinMoin: MoinMoinChat/Logs/moin-dev/2006-01-16

2006-01-16T00:06:00  <xorAxAx> [PERIODIC ANNOUNCEMENT] Logs can be found on http://moinmoin.wikiwikiweb.de/MoinMoinChat/Logs/moin-dev
2006-01-16T18:27:34  * xorAxAx is pretty sure about the deepcopy bug
2006-01-16T18:27:41  <xorAxAx> havent had time yet to assemble a workaround
2006-01-16T19:13:30  <xorAxAx> ThomasWaldmann: please answer here :)
2006-01-16T19:14:10  <ThomasWaldmann> your code?
2006-01-16T19:14:13  <xorAxAx> ThomasWaldmann: as i said, it looks like my few lines in packages.py trigger this unstability that wasnt seen before. or did you add deepcopy in 1.5?
2006-01-16T19:14:36  <ThomasWaldmann> i don't think so.
2006-01-16T19:15:00  <ThomasWaldmann> but I have never seen that bug anyway, as I upgraded to 2.4.2 quite some time ago.
2006-01-16T19:15:25  <ThomasWaldmann> and didnt use packager before that
2006-01-16T19:15:47  <xorAxAx> yeah, IMHO its packages.py which triggers the dirty-code-bug in wikidicts
2006-01-16T19:16:24  <ThomasWaldmann> what has uncompressing some language pages to do with that?
2006-01-16T19:16:55  <xorAxAx> guess or read the code :)
2006-01-16T19:17:13  <xorAxAx> i do have to account for some caching quirks in that code
2006-01-16T19:17:31  <xorAxAx> i.e. i delete the dicts cache a few hundred times on package installation
2006-01-16T19:18:05  <ThomasWaldmann> http://www.heise.de/newsticker/meldung/68385 ( -> new bugs )
2006-01-16T19:19:02  <xorAxAx> yeah, but they will release a beta. and even then, you have introduced enough IE bugs already for version 6
2006-01-16T19:20:09  <ThomasWaldmann> i didnt introduce bugs for IE
2006-01-16T19:20:43  <xorAxAx> who was it then?
2006-01-16T19:20:57  <ThomasWaldmann> who was what?
2006-01-16T19:21:12  <xorAxAx> i mean, the new css file triggers bugs on IE 6
2006-01-16T19:21:39  <ThomasWaldmann> that's another thing
2006-01-16T19:21:52  <ThomasWaldmann> the bugs are in IE, not in the CSS
2006-01-16T19:22:06  <xorAxAx> yeah, doesnt matter ;-)
2006-01-16T19:35:46  <ThomasWaldmann> maybe we should split off the ie "workarounds" to some ie.css and whoever wants may maintain it then
2006-01-16T19:36:40  <ThomasWaldmann> another possibility is to re-evaluate ie7 hack with current fckeditor code or just for r/o.
2006-01-16T21:05:10  <xorAxAx> ThomasWaldmann: seeing that you mentioned me, i wont really search in-depth for a solution. i will just try to reproduce it and try out a small workaround
2006-01-16T21:42:26  <ThomasWaldmann> try to reproduce it with latest patchlevel