IRC log of #zope3-dev for Wednesday, 2006-09-06

« Tuesday, 2006-09-05 Index Thursday, 2006-09-07 »
*** ignas has joined #zope3-dev00:00
*** jhauser has quit IRC00:03
philiKONTheuni, 'ussage' predates zope x3 3.000:05
Theuniyikes00:09
Theuniso it can/should/must go away? :)00:09
*** ignas has quit IRC00:09
*** jinty has quit IRC00:10
TheuniphiliKON: all tests run when removing that code (and the tests that within the page template package refer to it)00:22
Theuniyou want me to check that in?00:22
philiKONsure00:23
philiKONtrunk only though, to be safe00:23
Theunisure00:23
Theunialso, some other small thing00:23
* philiKON wonders when he has become the checkin authority for zope 3 ;)00:23
Theuniin zope.component.globalregistry, pretty much the last 50 lines, there is a redefinition of the provide*-stuff going on that IMHO contains cruft00:23
TheuniphiliKON: you're aroudn and i wanted a second oppinion :)00:24
philiKONTheuni, oh, yeha00:24
philiKONthe provideUtility = base.registerUtility00:25
philiKON ones should go00:25
Theunii've removed the first assignments in my sandbox and the stuff keeps working (as expected). I didn't know whether any magic was going on there though00:25
Theunithought so00:26
* Theuni checks it in00:26
*** natea has joined #zope3-dev00:26
Theunidone00:27
Theunihm. that's something we can backport00:27
srichterI think there is also a BBB should go away in 3.3 part there00:31
*** gumpa has left #zope3-dev00:32
*** natea_ has quit IRC00:33
Theunisrichter: that's the _IGlobalSiteManager?00:34
Theuniah no00:34
Theunithat's due in february 0700:34
Theuninothing to remove in 3.3 i guess00:34
*** wrobel has quit IRC00:40
Theunidone00:41
*** ktwilight has quit IRC00:56
srichterI can't remember where I saw it, but it was in zope.component00:56
*** ktwilight has joined #zope3-dev00:57
*** J1m has quit IRC01:04
*** ofer has joined #zope3-dev01:04
*** natea_ has joined #zope3-dev01:11
*** benji has quit IRC01:12
*** natea_ is now known as natea|away01:19
*** natea has quit IRC01:19
*** jinty has joined #zope3-dev01:31
*** ktwilight has quit IRC01:54
*** ofer has quit IRC02:01
*** ktwilight has joined #zope3-dev02:16
*** natea|away has quit IRC02:19
*** yota has quit IRC02:22
*** natea has joined #zope3-dev02:23
*** projekt01 has quit IRC02:24
*** natea_ has joined #zope3-dev03:07
*** ktwilight has quit IRC03:14
*** natea has quit IRC03:14
*** markup_ has left #zope3-dev03:18
*** natea has joined #zope3-dev03:32
*** natea_ has quit IRC03:39
*** ktwilight has joined #zope3-dev03:57
*** natea_ has joined #zope3-dev04:01
*** natea_ has quit IRC04:05
*** natea_ has joined #zope3-dev04:05
*** natea has quit IRC04:10
*** ktwilight has quit IRC04:13
*** jinty has quit IRC04:32
*** ktwilight has joined #zope3-dev04:52
*** niemeyer has quit IRC05:09
*** ktwilight has quit IRC05:14
*** ktwilight has joined #zope3-dev05:30
*** alecm has quit IRC05:35
*** ktwilight has quit IRC05:47
*** projekt01 has joined #zope3-dev05:47
*** benji_ has joined #zope3-dev05:47
*** ktwilight has joined #zope3-dev05:57
*** MiUlEr has joined #zope3-dev05:59
*** ktwilight has quit IRC06:14
*** benji_ is now known as benji06:23
*** benji has joined #zope3-dev06:24
*** stub has joined #zope3-dev07:11
*** MiUlEr has quit IRC07:36
*** MiUlEr has joined #zope3-dev07:42
*** alecm has joined #zope3-dev07:59
*** dunny has quit IRC08:05
*** timte has joined #zope3-dev08:05
*** eins has joined #zope3-dev08:14
*** ktwilight has joined #zope3-dev08:21
*** natea_ has quit IRC08:32
*** kobold has joined #zope3-dev08:44
*** MiUlEr has quit IRC08:50
*** d2m has left #zope3-dev09:11
*** zagy has joined #zope3-dev09:13
*** scherand has joined #zope3-dev09:14
*** alecm has quit IRC09:19
*** wrobel has joined #zope3-dev09:20
*** alecm has joined #zope3-dev09:21
*** alecm has quit IRC09:23
*** dobee has joined #zope3-dev09:25
*** romanofski has joined #zope3-dev09:31
romanofskimoin09:34
*** Aiste has joined #zope3-dev09:37
*** d2m has joined #zope3-dev09:41
*** stu1 has joined #zope3-dev09:48
*** stub has quit IRC09:49
*** stu1 is now known as stub09:49
*** MJ has quit IRC09:56
*** philiKON has quit IRC09:59
*** philiKON has joined #zope3-dev10:26
*** jhauser has joined #zope3-dev10:40
*** yota has joined #zope3-dev10:41
*** stainsby has joined #zope3-dev10:49
*** dunny has joined #zope3-dev11:04
*** schwendinger has joined #zope3-dev11:13
*** torkel_ has joined #zope3-dev11:14
*** schwendinger has quit IRC11:15
*** MJ has joined #zope3-dev11:16
*** schwendinger has joined #zope3-dev11:16
*** vlado has joined #zope3-dev11:34
*** faassen has joined #zope3-dev11:51
*** jinty has joined #zope3-dev11:55
*** BjornT has quit IRC11:57
*** BjornT has joined #zope3-dev11:57
*** baijum has joined #zope3-dev12:07
*** xenru|clone has quit IRC12:08
*** russf has quit IRC12:09
*** alga has joined #zope3-dev12:20
*** russf has joined #zope3-dev12:50
*** MJ has quit IRC13:13
*** dobee has quit IRC13:22
*** schwendinger has quit IRC13:26
*** Aiste has quit IRC13:27
*** stainsby has left #zope3-dev13:37
*** alga has quit IRC13:42
*** Aiste has joined #zope3-dev13:46
*** dunny has quit IRC13:47
*** russf has quit IRC13:48
*** dobee has joined #zope3-dev13:52
*** dokai has quit IRC13:58
*** dokai has joined #zope3-dev13:58
*** benji has quit IRC14:25
*** zagy has quit IRC14:25
*** nathany has joined #zope3-dev14:30
*** zagy has joined #zope3-dev14:31
*** srichter has quit IRC14:39
*** timte has quit IRC14:40
*** timte has joined #zope3-dev14:41
*** alga has joined #zope3-dev14:43
*** ignas has joined #zope3-dev14:52
*** timte has quit IRC15:05
*** timte has joined #zope3-dev15:06
*** dobee has quit IRC15:11
*** dobee has joined #zope3-dev15:17
*** niemeyer has joined #zope3-dev15:34
*** timte has quit IRC15:36
*** timte has joined #zope3-dev15:40
*** vlado has quit IRC15:45
*** eins has quit IRC15:50
*** mkerrin has joined #zope3-dev15:58
*** dobee has quit IRC16:00
*** dobee has joined #zope3-dev16:01
*** MiUlEr has joined #zope3-dev16:05
*** benji has joined #zope3-dev16:12
d2mis making pydoc work with zope3 a problem of zope or pydoc ? e.g. looking at zope.component in pydoc yields just a "zope.component = <module 'zope.component' from '/path/to/zope/component/__init__.pyc'" while other packages work just fine16:18
*** natea has joined #zope3-dev16:20
philiKONd2m, i think it's because zope.component is a ModuleProxy16:20
philiKON(for deprecation)16:20
d2mi see, like zope.interface, which makes zope.contentprovider.interfaces show 'zope' as one of its modules ?16:24
*** russf has joined #zope3-dev16:34
philiKONd2m, ?16:35
*** J1m has joined #zope3-dev16:37
*** gumpa has joined #zope3-dev16:41
*** jukart has joined #zope3-dev16:43
*** MiUlEr has quit IRC16:45
*** torkel_ has quit IRC16:45
jukartJ1m: I just checked out zc.recipe.zeoinstance and found that it needs some work, I would do it if that's ok for you16:51
d2mphiliKON: seems pydoc reports 'import zope.proxy' for example just as 'zope' in the Modules section16:51
J1mSure, what do you want to do to it?16:51
jukartactually I do not understand the part in _getdbconfig and would replace it with the code in zc.recipe.zopeinstance16:54
jukartand remove some unused code16:55
J1mI would rather not have you change code you don't understand. :)16:59
J1mEspecially since this recipe has no tests. :(16:59
J1m(I should have checked it into a development branch. I need to get in that habit. Bad me.)17:00
J1mBad bad me17:00
*** baijum has quit IRC17:03
jukartJ1m: right you are, after one more look at it I see what it is doing17:04
jukartI would like to remove the replace for the database name !17:05
J1mYou mean the bit that inserts "1"?17:07
benjiBad, bad Jim.17:07
*** zagy has quit IRC17:08
jukartRight17:09
J1mwhy do you want to remove that?17:09
jukartI want to be able to define my own name there17:10
J1mSo then you're going to add a new option?17:13
jukartyep, or take it directly from the database section17:13
*** timte has quit IRC17:14
*** timte has joined #zope3-dev17:15
J1mk17:23
*** stub has quit IRC17:23
*** torkel_ has joined #zope3-dev17:23
J1mIt sure would be nice to have a test first. :/17:23
jukartwill do it before my checkin17:24
jukartls17:25
*** benji has left #zope3-dev17:26
*** nathany has quit IRC17:30
*** nathany has joined #zope3-dev17:30
*** J1m has quit IRC17:31
*** alecm has joined #zope3-dev17:32
*** J1m has joined #zope3-dev17:33
*** schwendinger has joined #zope3-dev17:34
*** natea_ has joined #zope3-dev17:50
*** natea has quit IRC17:57
*** dobee has quit IRC17:59
*** schwendinger has quit IRC18:01
*** schwendinger has joined #zope3-dev18:05
*** j-w has joined #zope3-dev18:10
j-wi'm trying to set a content-type of 'application/xhtml+xml' on the response.18:18
j-wbut zope.publisher.http then breaks with a ValueError18:18
j-wzope.publisher.http expects a content-type starting with 'text/' for texttual content.18:18
j-wam i doing something wrong here?18:19
j-w(mmm, i hope my explanation is not too vague..)18:19
philiKONit's a known "issue"18:22
romanofskij-w: maybe a the XUL bug in the bugtracker might help you18:22
philiKONwe're not sure yet whether it's a bug or a feature :)18:22
romanofskisearch for XUL18:22
philiKONj-w, basically, the zope.publisher automatically encodes your unicode to text, but only for text/* content types18:23
j-wa, I found it in the collector indeed18:23
j-wit is a bug BTW :)18:23
philiKONwell, is it allowed to say  Content-Type: applciation/xhtml+xml;charset=utf-8  ?18:24
philiKONif it's allowed, then it's a bug18:24
j-wwell, its is allowed to say application/xhtml+xml at least18:24
philiKONright. but the publsiher will encode with some encoding18:25
*** mgedmin has joined #zope3-dev18:25
philiKONand it needs to tell the client18:25
philiKONit is allowed to tell the client via text/*;charset=utf-818:25
philiKONi'm not sure whether the same holds true for application/*18:25
j-w(and I need that for the XForms extension of firefox to work correctly. That's why I found out. XUL could be similar indeed)18:25
j-wI have no idea18:26
j-wbut making it this restrictive is not really a solution, or is it?18:26
*** projekt01 has quit IRC18:27
philiKONdunno18:27
j-wanyway, it is a known issue... uhm, no I wonder how to work arround it...18:27
mgedminare you talking about...18:27
romanofskihmmm don't know who told me about, but I thought the restriction is okey18:28
* mgedmin looks for the issue in the collector18:28
philiKONj-w, encode the unicode manually18:28
romanofskibecause encoding binary data to unicode would be stupid18:28
philiKONyou mean decoding18:28
philiKONbut this isn't about decoding18:28
j-wxhtml+xml isn't binary, is it18:28
philiKONright18:28
philiKONit isn't18:28
mgedminhttp://www.zope.org/Collectors/Zope3-dev/668 ?18:28
mgedminaka http://www.zope.org/Collectors/Zope3-dev/68418:29
philiKONthe point really is about the ;charset=xxx addition18:29
romanofskioh - right...18:29
j-wphiliKON: ah, so, you can't just append the charset part to the mime type part18:29
philiKONi *think* that's what the reason was18:29
philiKONi mean18:29
philiKONapplication/octet-stream;charset=utf-8 makes no sense18:30
j-wno, I see that point18:30
j-wbut for XML it does, I guess18:30
philiKONsorta. xml has <?xml ?> declarations18:30
philiKONso, one could make the point that xml data should always be pre-encoded already to strings18:31
philiKONand carry <?xml ?> declarations accordingly18:31
philiKON(which is an application concern, not one of the publisher)18:31
*** timte_ has joined #zope3-dev18:31
j-whuh, uhm, not sure if I follow that18:31
philiKONlet's say you have you xml unicode data in 'xmldata'18:32
philiKON>>> xmldata = u'...'18:32
philiKON>>> return '<?xml version="1.0" encoding="utf-8" ?>\n' + xmldata.encode('utf-8')18:32
*** timte has quit IRC18:33
philiKON"return" means "return to the zpublisher" here18:33
*** batlogg has quit IRC18:33
j-wyes, I see18:33
philiKONbasically, the encoding information with XML is intrinsic to XML18:33
philiKONno header needed18:33
philiKONheader might even be superfluous18:33
j-wwell, how about the content-type meta element for html then?18:33
philiKONwhat about it?18:34
j-wyou don't need a content-type response header then as well, right?18:34
philiKONi'm not sure i'm following18:34
philiKONwell18:34
j-wwell, I'm not sure either...18:34
philiKONyou would do:18:34
* philiKON sketches out in editor18:34
j-wwhy would the content-type header on the response be superfluous?18:35
*** markup_ has joined #zope3-dev18:35
j-wI mean, it declares what kinf of content you're publishing (apart from the encoding!)18:35
philiKONj-w, http://paste.lisp.org/display/2553618:36
*** scherand has quit IRC18:37
j-wand whether the *encoding* in this case is the concern of the application, not the publisher for non-"text/" cases, well I dunno.18:37
j-wAh, yes I see the point in encoding it before returning. I can certainly do that in my case18:38
j-wit just *feels* a bit weird, because, intuitively, I'm still dealing with some kind of text format.18:39
philiKONi agree18:39
philiKONj-w, i think you should bring this on to the mailinglist18:39
philiKONzope3-dev18:39
philiKONon 1 hand, i can sympthize with you18:39
j-wok18:39
philiKONthe publsiher should take care of encoding issues18:39
philiKONotoh, it's xml data :)_18:39
philiKONxml has an intrinsic encoding info18:40
j-wafter talking to you, I have the same dillema.18:40
philiKON:)18:40
* mgedmin wants to stick his $0.02 here18:41
philiKONlet's see what people smarter than us have to say :)18:41
j-wbut it does make me *understand* the issue much better18:41
philiKONthere we go :)18:41
mgedminHTTP requires a stream of bytes; the publisher knows how to convert unicode to a stream of bytes for text/* and doesn't know how to do that for other content types18:41
mgedminviews can give a stream of bytes to the publisher and avoid the whole issue18:41
philiKONright, we were already that far :)18:42
j-whehe18:42
philiKONthe question is if there's something sensible to do for XML data that's not of text/* content types18:42
mgedminprobably yes18:44
mgedminactual quotes from the relevant RFCs would be welcome in the collector18:44
philiKONright18:44
philiKONi once looked for such quotes18:45
philiKONbut couldn't find any18:45
philiKONthen again, i'm not very proficient with all the HTTP RFCs18:45
BjornTphiliKON, mgedmin: http://www.w3.org/TR/xhtml-media-types/ is a good starting point. there are links to RFCs from there.18:48
*** jukart has quit IRC18:48
j-wif I understand the w3 document right, the charset parameter is STRONGLY recommend for application/xml18:54
j-wand application/xhtml+xml should follow the same rule18:55
j-wso, in that case we can resolve this issue18:55
*** projekt01 has joined #zope3-dev18:55
j-wand treat application/xml and application/xhtml+xml like we treat text/*18:55
j-w(but maybe I just didn't understand the w3 talk - this can happen ;)18:56
*** projekt01 is now known as projekt01_18:57
* philiKON reads18:57
j-wand I think http://www.rfc-editor.org/rfc/rfc3023.txt is about this particular issue18:57
j-w(but I'm not proficient reading RFCs too ;)18:58
BjornTj-w: right. the question is, though, who's responsible for adding the charset parameter? the publisher or the application code?18:58
philiKONthe publisher then18:58
philiKONif there's an RFC that lists all the applicable mime types18:58
j-wwell, why would there be a difference between text/* and applicaiotn/xml18:58
philiKONright18:58
j-weither the publisher does for all18:58
j-wor for none18:58
philiKONfred's suggestion with zope.mimetype sounds interesting18:59
BjornTj-w: the rfc also says that you should includ the encoding in the xml document itself. if you don't encode it yourself, you don't know which encoding the publisher might choose.18:59
philiKONhmm. good point18:59
philiKONargh18:59
philiKONcatch 2218:59
j-wwell I do we knwo for text/* ?18:59
j-wI meant, *how* do we know for the case of text/* ?18:59
j-wcan't they be treated alike?18:59
j-wI guess I miss some detail here...19:00
BjornTj-w: for text/html you don't need to include the encoding in the document, the content-type's charset parameter is used.19:00
philiKON1. most text/* data does not have an intrinsic way of specifying the encoding19:01
philiKON2. even for some text/* types (such as text/html) you don't WANT to use <?xml ?> (quirks mode)19:01
philiKON3. for applciation/xml* the RFC suggests both19:01
philiKONbut the publisher can only set one (the content type info)19:01
mgedminby the way, even if you do include the encoding in the HTML document, the content-type can override it19:01
j-wBjornT: a, right, that's the thing I forgot19:02
rockyisn't the meta tags in an html document that could contain the content type and encoding meant to override whatever the server sends as the Content-Type header?19:02
mgedminrocky: no19:03
rockymgedmin: the other way around?19:03
mgedminthe server is allowed to do recoding on the fly19:03
rockyah19:03
mgedminso the <meta> element may have the wrong encoding, while the content-type is correct19:03
*** timte_ has quit IRC19:04
j-whmmmm, i need to catch a train now :| i'll read the logs later. thanks for helping me getting this issue clear...19:04
*** philiKON has quit IRC19:04
*** timte has joined #zope3-dev19:06
*** j-w has quit IRC19:06
*** jinty has quit IRC19:07
*** schwendinger has quit IRC19:08
*** torkel_ has quit IRC19:08
*** alecm has quit IRC19:10
*** torkel_ has joined #zope3-dev19:17
*** romanofski has quit IRC19:18
*** jukart has joined #zope3-dev19:34
*** gumpa is now known as gumpa-afk19:42
*** timte has quit IRC19:45
*** zagy has joined #zope3-dev19:53
*** RaFromBRC has joined #zope3-dev19:54
*** timte has joined #zope3-dev19:59
*** schwendinger has joined #zope3-dev20:03
*** Aiste has quit IRC20:04
*** ignas has quit IRC20:11
*** kobold has left #zope3-dev20:23
*** xenru has joined #zope3-dev20:25
*** alecm has joined #zope3-dev20:37
*** batlogg has joined #zope3-dev20:41
*** jinty has joined #zope3-dev20:46
*** Aiste has joined #zope3-dev20:46
*** dobee has joined #zope3-dev20:48
*** faassen has quit IRC21:01
*** philiKON has joined #zope3-dev21:06
*** dobee has quit IRC21:16
*** romanofski has joined #zope3-dev21:21
*** rocky has quit IRC21:25
*** MJ has joined #zope3-dev21:27
*** jukart has quit IRC21:30
*** dobee has joined #zope3-dev21:34
*** RaFromBRC has quit IRC21:35
*** dunny has joined #zope3-dev21:46
*** jinty has quit IRC21:46
*** benji has joined #zope3-dev21:54
*** rocky has joined #zope3-dev22:11
*** J1m has quit IRC22:14
*** J1m has joined #zope3-dev22:16
*** zagy has quit IRC22:18
*** J1m has quit IRC22:24
*** nathany has quit IRC22:25
*** philiKON has quit IRC22:34
*** alecm has quit IRC22:37
*** philiKON has joined #zope3-dev22:37
*** J1m has joined #zope3-dev22:39
*** schwendinger has quit IRC22:45
*** alecm has joined #zope3-dev22:46
*** stub has joined #zope3-dev22:46
*** volvox has joined #zope3-dev22:48
*** dokai has quit IRC22:56
*** dokai has joined #zope3-dev22:59
*** timte has quit IRC23:02
*** timte has joined #zope3-dev23:02
*** srichter has joined #zope3-dev23:03
*** ChanServ sets mode: +o srichter23:03
*** philiKON has quit IRC23:04
*** philiKON has joined #zope3-dev23:05
*** alga has quit IRC23:13
*** dobee has quit IRC23:19
*** mgedmin has quit IRC23:25
*** stub has quit IRC23:31
*** MJ has quit IRC23:41
*** mkerrin has quit IRC23:45
*** timte has quit IRC23:55
« Tuesday, 2006-09-05 Index Thursday, 2006-09-07 »

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!