| *** andrew_m has quit IRC | 00:04 | |
| *** jvts has quit IRC | 00:06 | |
| *** andrew_m has joined #zope3-dev | 00:07 | |
| *** niemeyer_ is now known as niemeyer | 00:08 | |
| *** J1m has quit IRC | 00:13 | |
| *** _projekt01 is now known as projekt01 | 00:15 | |
| *** GaryPoster has joined #zope3-dev | 00:26 | |
| GaryPoster | srichter: hey. I didn't get your email but Benji mentioned you sent one. Do you see why you need the _clear call now? | 00:27 |
|---|---|---|
| srichter | yes | 00:27 |
| GaryPoster | ok, cool | 00:27 |
| srichter | I just sent another one to you :-) | 00:27 |
| GaryPoster | OK, cool, hopefully I get that one ;-) | 00:27 |
| srichter | so why do you need clear after BasicTypes are set? | 00:28 |
| srichter | that makes no sense | 00:29 |
| srichter | clear_ does not mess with BasicTypes | 00:29 |
| GaryPoster | No, BasicTypes are not the important data structure. _default_checkers, and _checkers, are the important data structure. | 00:29 |
| GaryPoster | They are only updated when _clear is called, which is done when the checkers module is imported, and when tests are run. | 00:30 |
| *** baldtrol has joined #zope3-dev | 00:31 | |
| srichter | so, what you really want to do is: | 00:31 |
| GaryPoster | Therefore, without the call to _clear, you were putting the checker setting in for future test runs, but it was not registered for the app itself to run | 00:31 |
| srichter | _checkers.update(BasicTypes) | 00:31 |
| GaryPoster | Yes, except that again elevates an _* name (_checkers) to API. | 00:32 |
| srichter | so create an alias to _clear called update(), and we are fine, right? :-) | 00:32 |
| GaryPoster | But yes, that would accomplish the same thing practically. Well, I'm OK with that if it is marked as # TODO not API; expect change. | 00:33 |
| srichter | so I guess the right solution would be to make BasicTypes a special dictionary that, when updated, also adds the checker entry | 00:34 |
| *** whit has quit IRC | 00:34 | |
| srichter | that would be a wuick implementation of an API without adding aPI | 00:34 |
| GaryPoster | Given that you want a fix (very understandable) and we don't have time to figure out how to do it right (as it had been discussed on the list before, I think) then I'm ok with a to-be-deprecated solution for now. | 00:34 |
| GaryPoster | Except that BasicTypes itself is new, yes? | 00:34 |
| srichter | is it? | 00:35 |
| srichter | I dunno | 00:35 |
| *** MJ has quit IRC | 00:35 | |
| GaryPoster | Heh, I thought so | 00:35 |
| srichter | something like it has existed for a while, if I remember correctly | 00:35 |
| GaryPoster | It wasn't there last time I walked through this code. _default_checkers and _checkers were the only data structures like this back then. Really don't think it is in 3.1, which I guess is the core question. | 00:36 |
| GaryPoster | Lemme look; I think I have a copy of the branch hanging around | 00:36 |
| srichter | ok, thanks | 00:37 |
| GaryPoster | Yeah, you're right. It's in 3.1. Ah well; I don't love it, but yeah, it's there, and you could make that do some of the magic | 00:38 |
| GaryPoster | I'm OK with that or a "TODO" | 00:38 |
| srichter | ok, I have it do some magic :-) | 00:39 |
| GaryPoster | ok :-) | 00:39 |
| benji | tarek, the tests are still failing :( | 00:42 |
| GaryPoster | bye | 00:42 |
| *** GaryPoster has quit IRC | 00:42 | |
| *** Alef has quit IRC | 00:45 | |
| baldtrol | hi all... using apache in front of zope3.1 for the first time, and none of my css, js, etc come through. pages display, but with no formatting or javascript... i have the virtual host directives line by line from the zope3 dev book... zope error logs keep saying "ForbiddenAttribute: ('publishTraverse', ..." | 00:46 |
| baldtrol | googled around for it, but other than some other, similar examples quoting stephan or philipp's books, nothing seemed to shine any light | 00:46 |
| *** zbir has quit IRC | 00:48 | |
| *** benji has quit IRC | 00:49 | |
| *** fdrake has quit IRC | 00:54 | |
| *** baldtrol has quit IRC | 01:00 | |
| *** BjornT_ has joined #zope3-dev | 01:07 | |
| *** nisq has joined #zope3-dev | 01:16 | |
| *** nisq has left #zope3-dev | 01:17 | |
| *** BjornT has quit IRC | 01:21 | |
| *** tarek has quit IRC | 01:36 | |
| *** xenru has joined #zope3-dev | 01:36 | |
| *** natea|busy is now known as natea | 02:16 | |
| *** andres has joined #zope3-dev | 02:19 | |
| andres | I have a question regarding persistence. | 02:20 |
| andres | Views dont have persistence, or? | 02:21 |
| srichter | no | 02:21 |
| srichter | they are created every time they are used | 02:21 |
| andres | Because I create an object in a view and this one keeps values. | 02:22 |
| andres | Which is quite strange i think. | 02:22 |
| srichter | huh | 02:22 |
| andres | And that object is just an layer uppon zope.formlib, so nothing special is involved. | 02:23 |
| projekt01 | what do you mean with "create an object in a view"? | 02:24 |
| projekt01 | srichter, do we need the update method in the viewlet? | 02:25 |
| andres | projekt01, a = Objectname(context,request, some=other,paremeters=exist, also=...) | 02:25 |
| srichter | projekt01: yes, at least a dummy implementation | 02:25 |
| srichter | projekt01: it is part of the content provider API now | 02:25 |
| srichter | projekt01: that was the agreement I made with Gary | 02:26 |
| projekt01 | I guess it's needed for subviews? right? | 02:26 |
| projekt01 | Ok, I see | 02:26 |
| srichter | yes | 02:26 |
| srichter | I think this is a good agreement actually | 02:26 |
| srichter | because it makes content providers two-stage views, which gives them a better meaning | 02:26 |
| srichter | and it adresses a very important use case | 02:27 |
| projekt01 | Yes, I can live with that ,-) | 02:27 |
| projekt01 | I think two interfaces where better then all in one, but that's ok. | 02:28 |
| srichter | I thought so first too, but while talking to Gary I convinced myself otherwise | 02:29 |
| projekt01 | andreas, that can you do in the view. | 02:29 |
| andres | projekt01, do you mean me? | 02:29 |
| srichter | I really want to make the two-phase process a core content provider implementation | 02:29 |
| projekt01 | srichter, if you say that's Ok, I'm fine, then I know you have allways good arguments ;-) | 02:30 |
| projekt01 | andreas, yes | 02:30 |
| srichter | btw, I agree with Jim and ZC now, that the two-phase process is very JSR-168 friendly | 02:30 |
| projekt01 | srichter, sounds interesting this two-phase process | 02:30 |
| andres | projekt01, i just are called andres ;-) | 02:30 |
| projekt01 | andres, Ok | 02:31 |
| projekt01 | andres, after you created this object, where do you store them? | 02:31 |
| projekt01 | andres, I guess you call this view on a "content type instance", then you create a object, ad now you have to store the object somewhere | 02:33 |
| andres | projekt01, no, i dont want to store something somewhere (actually, i do, but thats not the point). | 02:34 |
| projekt01 | what do you do with object "a" | 02:35 |
| andres | projekt01, i let it generate some text for me, nothing more. | 02:35 |
| andres | but, a has an array as one of its attributes, and that still contains values from the last request. | 02:36 |
| andres | s/a/'a'/ | 02:36 |
| projekt01 | use sessions for share request data | 02:36 |
| projekt01 | over more then one view | 02:36 |
| andres | projekt01, i dont want that, it is so at the moment, thats my problem. | 02:37 |
| andres | and the strange thing. | 02:37 |
| projekt01 | can you explain the problem a little more. I think I didn't understand it right. | 02:38 |
| andres | I will try so. | 02:38 |
| andres | I have a View in which i create an instance of my class Form. Then i do some things like Form.add(x). Which saves x in an array. On the first request, the array contains only one item (which is normal). On the second request, it contains _two_ elements. | 02:42 |
| andres | The one from the request before (and thats the strange thing) and the newly added (which is normal) | 02:42 |
| andres | Which i dont understand. | 02:43 |
| projekt01 | do you use a "input field" for show the value of the first request in the form? | 02:44 |
| andres | No, just text. | 02:44 |
| *** zbir has joined #zope3-dev | 02:46 | |
| projekt01 | can you trace the request? | 02:46 |
| projekt01 | I mean do you have a tool for see the request variables? | 02:46 |
| andres | yes, i have that, and its not in there. | 02:47 |
| andres | ARG. My Python unawareness shoot me in my foot. The array was declared outside of __init__() (but still in the class). | 02:48 |
| andres | after moving that into __init__ it works. | 02:48 |
| projekt01 | cool | 02:49 |
| andres | But is that normal? | 02:49 |
| projekt01 | I guess you defined a class variable and set a value there, so all classes provide this attribute as default | 02:50 |
| andres | Yes | 02:50 |
| projekt01 | so they first value get stored there | 02:51 |
| andres | But, that those are persistent over multiple request seems strange to me. | 02:51 |
| andres | Anyway, its soled and working... | 02:52 |
| projekt01 | that isn't persistent, after a server restart all class variable will have the initial values | 02:53 |
| andres | Yes, stupid naming from my side. | 02:54 |
| projekt01 | but in the runtime you can change class variables and thy get shared on all class instances, except a class overrides this value in a self.xy | 02:54 |
| andres | Even if i only access them via self.xy they are shared? So, i should never declare variables outside of __init__? | 02:55 |
| andres | if i did classname.attribute = 'xyz' i would have expected this... | 02:55 |
| projekt01 | It depends how the attribute "attribute" is declared in the class | 02:57 |
| andres | class xyz: | 02:57 |
| andres | ....attributename = [] | 02:57 |
| projekt01 | but if you call self.attribute you call "as a kind of fallback" the class variable if no private variable is defined. | 02:58 |
| projekt01 | self.attribute is private | 02:58 |
| andres | Ok. Strange that didnt hit me earlier. | 02:59 |
| projekt01 | your attributename list is a class variable. You have to define "self.attributename" in the __init__ or in a method in your case | 03:00 |
| andres | projekt01, yes, thats what i do now. | 03:02 |
| projekt01 | Ok | 03:02 |
| projekt01 | srichter, there is no viewlet base class for use/inherit in custom viewlets. Or I have to say the metaconfigure mixin the class ViewletBase if I whould use one. | 03:03 |
| projekt01 | srichter, the problem is, the custom viewlets have to call the super class constructor an they are only based on "object" | 03:06 |
| projekt01 | I don't like this, because we have to write mixin classes | 03:07 |
| andres | btw, the combination zope3 + postgres + sqlos is quite neat. | 03:10 |
| *** xenru has joined #zope3-dev | 03:37 | |
| *** stub has joined #zope3-dev | 03:52 | |
| *** srichter has quit IRC | 04:18 | |
| *** srichter has joined #zope3-dev | 04:18 | |
| *** ChanServ sets mode: +o srichter | 04:18 | |
| *** sashav has joined #zope3-dev | 04:45 | |
| *** projekt01 has quit IRC | 04:46 | |
| *** benji has joined #zope3-dev | 05:00 | |
| benji | srichter, ayt? | 05:02 |
| srichter | benji: yeah | 05:04 |
| benji | have you checked out buildbot.zope.org lately? :) | 05:04 |
| srichter | no, but I just did as soon as you pinged me | 05:05 |
| srichter | eek | 05:06 |
| *** niemeyer has quit IRC | 05:10 | |
| *** gdsgdsgvdd has joined #zope3-dev | 05:19 | |
| gdsgdsgvdd | i have zope 3.0.0 installed and was tring to use ISession | 05:20 |
| gdsgdsgvdd | zope.app.session.interfaces | 05:20 |
| gdsgdsgvdd | import ISession | 05:21 |
| gdsgdsgvdd | but there is no session.interfaces, in what version can i find this session interface | 05:22 |
| srichter | I think we did not ship the session package in 3.0 | 05:25 |
| gdsgdsgvdd | is it there in 3.1 | 05:26 |
| srichter | yeah, it is in 3.1 | 05:31 |
| srichter | benji: are you still there? | 05:32 |
| benji | yep | 05:32 |
| srichter | benji: we really need to get the urllib2 404 error problem addressed | 05:33 |
| srichter | have you looked into that already? | 05:33 |
| srichter | also, I really would like to have a testbrowser method that can return all links in a page | 05:33 |
| srichter | this way I can check for broken links | 05:34 |
| benji | I think something can already check for broken links, but can't remember | 05:34 |
| benji | is there a helper function to do that in the functional testing stuff? | 05:34 |
| srichter | yeah, but the mechanize browser class has a very efficient link retriever | 05:35 |
| benji | I'd be in favor of reworking that function to use mechanize | 05:36 |
| srichter | yeah | 05:36 |
| srichter | btw, I built today the static apidoc maker using mechanize and your publisher handler and it is a really nice interface | 05:37 |
| srichter | except that it is not tested at all | 05:37 |
| srichter | btw, if I check in fixes to the Zope 3 version of mechanize, will you guys send those fixes upstream? | 05:38 |
| benji | we can, it'd probably be best if you do though (in case he has any questions it'd be easier for you to answer directly) | 05:43 |
| srichter | ok, though I really don;t want to join yet another mailing list | 05:49 |
| srichter | darn contributing must be easier ;-\ | 05:49 |
| *** gdsgdsgvdd has quit IRC | 06:01 | |
| *** lucia12345 has quit IRC | 06:06 | |
| *** strichter has joined #zope3-dev | 06:14 | |
| *** srichter has quit IRC | 06:23 | |
| *** deo has quit IRC | 07:19 | |
| *** d2m_ has joined #zope3-dev | 07:29 | |
| *** d2m has quit IRC | 07:29 | |
| *** jhauser has quit IRC | 07:29 | |
| *** d2m_ is now known as d2m | 07:29 | |
| *** benji has quit IRC | 07:30 | |
| *** natea has quit IRC | 07:30 | |
| *** bradb has quit IRC | 07:30 | |
| *** gnosis has quit IRC | 07:30 | |
| *** mp has quit IRC | 07:30 | |
| *** tiredbones has quit IRC | 07:30 | |
| *** vinsci has quit IRC | 07:30 | |
| *** benji has joined #zope3-dev | 07:31 | |
| *** bradb has joined #zope3-dev | 07:31 | |
| *** natea has joined #zope3-dev | 07:31 | |
| *** gnosis has joined #zope3-dev | 07:31 | |
| *** mp has joined #zope3-dev | 07:31 | |
| *** tiredbones has joined #zope3-dev | 07:31 | |
| *** vinsci has joined #zope3-dev | 07:31 | |
| *** xenru has quit IRC | 07:38 | |
| *** gnosis has quit IRC | 07:45 | |
| *** tiredbones has quit IRC | 07:45 | |
| *** benji has quit IRC | 07:45 | |
| *** vinsci has quit IRC | 07:45 | |
| *** mp has quit IRC | 07:45 | |
| *** bradb has quit IRC | 07:45 | |
| *** natea has quit IRC | 07:45 | |
| *** benji has joined #zope3-dev | 07:45 | |
| *** bradb has joined #zope3-dev | 07:45 | |
| *** natea has joined #zope3-dev | 07:45 | |
| *** gnosis has joined #zope3-dev | 07:45 | |
| *** mp has joined #zope3-dev | 07:45 | |
| *** tiredbones has joined #zope3-dev | 07:45 | |
| *** vinsci has joined #zope3-dev | 07:45 | |
| *** dobee has joined #zope3-dev | 08:02 | |
| *** lucia12345 has joined #zope3-dev | 08:04 | |
| *** BjornT_ is now known as BjornT | 08:08 | |
| *** strichter has quit IRC | 08:23 | |
| *** dlk has joined #zope3-dev | 08:41 | |
| *** sashav has quit IRC | 08:44 | |
| *** dobee has quit IRC | 08:47 | |
| *** MJ has joined #zope3-dev | 09:08 | |
| *** dobee has joined #zope3-dev | 09:09 | |
| *** hdima has joined #zope3-dev | 09:33 | |
| *** mp has quit IRC | 09:39 | |
| d2m | how do i POST to a URL using a python module like httplib ? are there functional tests for POST ? | 09:44 |
| *** MJ has quit IRC | 09:46 | |
| *** jvts has joined #zope3-dev | 10:15 | |
| *** sashav has joined #zope3-dev | 10:22 | |
| *** alienoid has joined #zope3-dev | 10:27 | |
| *** faassen has joined #zope3-dev | 10:32 | |
| *** vlado has joined #zope3-dev | 10:35 | |
| *** j-w has joined #zope3-dev | 10:59 | |
| *** Aiste has joined #zope3-dev | 11:01 | |
| *** andres has quit IRC | 11:15 | |
| *** andres_ is now known as andres | 11:15 | |
| *** povbot` has joined #zope3-dev | 11:24 | |
| *** ignas has joined #zope3-dev | 11:26 | |
| *** povbot has quit IRC | 11:40 | |
| *** MJ has joined #zope3-dev | 11:40 | |
| *** projekt01 has joined #zope3-dev | 11:48 | |
| *** mkerrin has joined #zope3-dev | 12:16 | |
| *** mgedmin has joined #zope3-dev | 12:22 | |
| *** regebro has joined #zope3-dev | 12:40 | |
| *** j-w has quit IRC | 12:42 | |
| *** tarek has joined #zope3-dev | 12:45 | |
| *** j-w has joined #zope3-dev | 13:21 | |
| *** jvts has quit IRC | 13:43 | |
| *** philiKON has joined #zope3-dev | 13:50 | |
| *** strichter has joined #zope3-dev | 13:54 | |
| *** efge has joined #zope3-dev | 13:57 | |
| *** niemeyer has joined #zope3-dev | 14:03 | |
| *** philiKON has quit IRC | 14:04 | |
| projekt01 | srichter, ayt? | 14:05 |
| *** benji has quit IRC | 14:22 | |
| *** strichter has quit IRC | 14:23 | |
| *** jinty has joined #zope3-dev | 14:48 | |
| *** dlk has quit IRC | 14:48 | |
| *** MrTopf has joined #zope3-dev | 15:05 | |
| *** srichter has joined #zope3-dev | 15:10 | |
| *** jvts has joined #zope3-dev | 15:12 | |
| *** srichter has quit IRC | 15:12 | |
| *** jvts has left #zope3-dev | 15:13 | |
| *** srichter has joined #zope3-dev | 15:15 | |
| *** srichter has quit IRC | 15:19 | |
| *** srichter has joined #zope3-dev | 15:19 | |
| *** jvts has joined #zope3-dev | 15:22 | |
| efge | has anyone profiled zcml loading to find out what's so slow ? adding the load of 4 little zcml files in a unit test makes things slower by at least 1.5 s per test... :( | 15:27 |
| *** ChanServ sets mode: +o srichter | 15:28 | |
| srichter | efge: never add ZCML files to unit test setup; it's a recipe for disaster | 15:28 |
| srichter | in ZCML, the schema field conversion is what's taking the time | 15:29 |
| efge | srichter: well I need to load some Five stuff before anything can be tested | 15:29 |
| srichter | it loads a lot of Python too of course | 15:29 |
| srichter | so if your FS is slow, then you have your bottle neck | 15:29 |
| srichter | then create a FiveSetupBase class or helper function | 15:29 |
| srichter | the new test runner will encourage this | 15:30 |
| efge | for some tests, every test will need the setup | 15:30 |
| *** povbot has joined #zope3-dev | 15:38 | |
| *** andres has quit IRC | 15:38 | |
| *** benji has joined #zope3-dev | 15:40 | |
| srichter | efge: right, that's the reason you should write a base class or helper function | 15:40 |
| srichter | using the new test runner, all those tests would be in the same layer | 15:40 |
| *** MrTopf_ has joined #zope3-dev | 15:40 | |
| *** MrTopf has quit IRC | 15:41 | |
| *** povbot` has quit IRC | 15:41 | |
| *** hdima has quit IRC | 15:41 | |
| *** dobee has quit IRC | 15:41 | |
| *** hdima has joined #zope3-dev | 15:44 | |
| *** dobee has joined #zope3-dev | 15:44 | |
| *** philiKON has joined #zope3-dev | 15:44 | |
| *** Aiste has quit IRC | 15:45 | |
| *** zbir has quit IRC | 15:47 | |
| *** Faelin has joined #zope3-dev | 15:50 | |
| efge | srichter: you mean the zcml would be loaded once for all the tests ? that's what layers are ? | 15:57 |
| efge | if that's the case, cool | 15:57 |
| srichter | yeah, I think this is the idea | 15:59 |
| srichter | you load some common setup once | 15:59 |
| srichter | (I am not sure how well cleanup will be | 15:59 |
| srichter | because using the placelesssetup.tearDown() is very simple and powerful, and that would certainly not work anymore | 15:59 |
| benji | srichter, currently tearing down is not done, and a new clean subprocess is spawned that loads the new ZCML | 16:00 |
| efge | ah yes | 16:00 |
| srichter | I'll wait for Jim to make the switch | 16:00 |
| srichter | benji: I see | 16:00 |
| * philiKON is waiting for Jim, too... his testrunner change on the zope 2 trunk made running tests in instance products impossible | 16:01 | |
| srichter | benji: oh, so the setup is loaded and then a process is spawned | 16:01 |
| srichter | benji: this way you keep your setup base line and you always have a clear tear down | 16:01 |
| srichter | benji: that's clever | 16:01 |
| benji | srichter, it'd be more clever if we could undo ZCML :) | 16:02 |
| efge | better have fast process spawn though, I wonder how windows fares :) | 16:02 |
| *** zbir has joined #zope3-dev | 16:02 | |
| jvts | hi, I'm integrating Zope 3's zope.component in Gaphor (http://gaphor.sf.net). The problem I'm having is that I just want zope.interface, zope.component and zope.exceptions. But the packages somehow also depend on zope.testing, zope.proxy and zope.deprecation. | 16:02 |
| srichter | benji: undoing ZCML is very tough, simply because you would need to define anti-actions for each action to make it work | 16:03 |
| alienoid | benji: hi, you dislike zcml? | 16:03 |
| srichter | benji: I have thought about this many times :-) | 16:03 |
| benji | alienoid, nope. I think ZCML is great for the things it's good at | 16:04 |
| alienoid | oh, ok :) | 16:04 |
| srichter | jvts: it should not depend on zope.proxy | 16:04 |
| srichter | jvts: zope.testing and zope.deprecation sound right though | 16:04 |
| jvts | testins is indeed listed in the dependencies | 16:05 |
| srichter | jvts: zope.testing is only required, if you want to run the tests of course | 16:05 |
| benji | alienoid, I also think it really, really bad for other things, let's not do those :) | 16:05 |
| philiKON | zcml is great for turning things on and off. that's it :) | 16:05 |
| srichter | jvts: zope.deprecation is a simply package to make deprecation warnings much easier. It allows us to evolve the code | 16:06 |
| *** alga has joined #zope3-dev | 16:07 | |
| jvts | srichter: ok | 16:07 |
| benji | efge, it works well enough on Windows; you generally only spawn a new process fairly rairly, not for every test or anything | 16:08 |
| philiKON | zope.depecration is quite useful. the only thing that i'm missing from it is the functionality to deprecate a whole module and still play nice during certain imports | 16:09 |
| benji | philiKON, I wish we had a dedicated evangelist to promote individual packages (like zope.deprecation, zope.wfmc, etc.) to non Zope 3 users | 16:12 |
| benji | maybe I need to figure out ZPackage and do it myself | 16:12 |
| philiKON | we'd need an inside man ;) | 16:13 |
| philiKON | like, someone who's actually respected in the pythonc ommunity | 16:13 |
| philiKON | the twisted guys seem like a good group of evangelists | 16:13 |
| philiKON | we already got them to use zope.interface | 16:13 |
| philiKON | zope.component should be next :) | 16:13 |
| benji | :) | 16:13 |
| *** SteveA has joined #zope3-dev | 16:16 | |
| *** sashav has quit IRC | 16:18 | |
| srichter | note that for 3.3 we will be individual packages for 3.3 | 16:20 |
| srichter | Fred and I will work on that | 16:20 |
| philiKON | s/packages/eggs/ ? | 16:21 |
| srichter | I don't know what eggs are | 16:21 |
| srichter | we will distribute many small zpkgtools-created packages | 16:21 |
| philiKON | eggs are zipfiles containing python modulees | 16:21 |
| philiKON | err, packages | 16:21 |
| philiKON | they are like JAR files | 16:22 |
| faassen | srichter: you should learn what eggs are, and easy_install, and setuptools. :) | 16:22 |
| philiKON | a whole package inside a zip file | 16:22 |
| srichter | yeah, when I need it | 16:22 |
| faassen | srichter: I think Zope 3 should be packaged as an egg as soon as possible. | 16:22 |
| philiKON | the beauty of eggs is that in addition to putting everything in a zip file (which python already supports) is the dependency management | 16:22 |
| faassen | srichter: it's an essential requirement for Zope 3 marketing in my opinion. part of the reason TurboGears is hyped to death is that you can install it in a few minutes. | 16:22 |
| philiKON | faassen, i agree! | 16:22 |
| faassen | srichter: even though it's a humongous package with many dependencies. | 16:22 |
| philiKON | not only from a marketing perspective | 16:23 |
| philiKON | it has so many other advantages | 16:23 |
| faassen | of course. :) | 16:23 |
| faassen | anyway, I think it's going to be the Python standard way to do packaging, and Zope 3 should do it the Python standard way. | 16:23 |
| srichter | if eggs fulfill our use cases then sure | 16:23 |
| *** J1m has joined #zope3-dev | 16:23 | |
| srichter | I'll defer to Jima nd Fred to make the decision | 16:23 |
| philiKON | morning J1m | 16:23 |
| faassen | srichter: the tutorial even has zope 3 examples! | 16:23 |
| philiKON | faassen, it does? | 16:23 |
| * philiKON doesn't remember | 16:23 | |
| faassen | srichter: I just wanted to make sure eggs settled in your mind as something potentially Important. :) | 16:24 |
| faassen | philiKON: yes, it does, one of the tutorials talks about namespace packages, for instance 'zope' | 16:24 |
| srichter | faassen: ok :-) | 16:24 |
| faassen | philiKON: and now we install a sub package into it, etc. | 16:24 |
| philiKON | J1m, your changing of test.py on the Zope 2 trunk made it impossible to execute something like "bin/zopectl test --dir Products/MyProduct" in an instance (to run the tests of MyProduct | 16:24 |
| faassen | it's the combo setuptools/eggs/easy_install that's the important bit. | 16:24 |
| philiKON | faassen, ah, cool | 16:24 |
| J1m | philiKON, ise -s instead og --dir | 16:25 |
| J1m | philiKON, use -s instead og --dir | 16:25 |
| J1m | philiKON, use -s instead of --dir | 16:25 |
| J1m | grrrr | 16:25 |
| philiKON | :) | 16:25 |
| * philiKON tries, but doesn't think that that changes anything | 16:25 | |
| *** fdrake has joined #zope3-dev | 16:25 | |
| J1m | I think the goldegg people are leading the way on eggs in zope | 16:26 |
| srichter | note that I am totally indifferent about the packaging solution; I am just following what I am told and zpkgtools is very powerful; it handles ZCML, which is a big feature for us | 16:26 |
| srichter | the thing is that we do not just install simple packages | 16:26 |
| J1m | fdrake, will be participating in a packaging sprint next month. | 16:26 |
| srichter | ok | 16:26 |
| fdrake | woohoo, San Jose, here I come! | 16:26 |
| srichter | (as I said I just do what Fred will tell me I have to do to make a release) | 16:26 |
| J1m | philiKON, hm, --dir should work too. | 16:27 |
| philiKON | J1m, http://paste.plone.org/710 | 16:27 |
| philiKON | J1m, when i comment out the automatic generation of the --libdir flag that's causing the trouble, i get different errors | 16:27 |
| philiKON | J1m, really, i don't think that the new test runner behaves like the old at all when it comes to bootstrapping zope (setting up Products, for intsance) | 16:28 |
| J1m | philiKON, that's odd wrt --libdir. | 16:28 |
| J1m | I changed the code that generates that. | 16:28 |
| philiKON | oh, wait, maybe i didn't update that | 16:28 |
| * philiKON has a weird sandbox | 16:28 | |
| philiKON | (because of the zope 3.2 integration) | 16:29 |
| * philiKON svn ups | 16:29 | |
| J1m | brb | 16:29 |
| philiKON | J1m, works now | 16:30 |
| philiKON | J1m, sorry about that. was my bad | 16:30 |
| philiKON | ooooooh. i get lots of dots now... | 16:30 |
| * philiKON loves the new testrunner's interpretation of doctests | 16:30 | |
| srichter | btw, I made some really good headway with static apidoc | 16:31 |
| philiKON | srichter, saw that, nice | 16:31 |
| philiKON | for zope 3.3 i'll look at generating docbook | 16:32 |
| srichter | there are some issues left with images | 16:32 |
| philiKON | images? what do we need images for? | 16:32 |
| srichter | and recently it fails to find some links using pullparser, which I have to investigate | 16:32 |
| srichter | philiKON: opening and closing sections in the interface details | 16:32 |
| philiKON | ic | 16:32 |
| srichter | the URLs of those images are not referenced in the usual way and the URL is hard coded | 16:33 |
| srichter | but by making the JS a bit nicer, we should be able to get it working | 16:33 |
| srichter | but the missing links really kill me right now, because I know they worked before, but pullparser seems not to be able to find them | 16:34 |
| srichter | and of course, we have massive amounts of ReST complaints | 16:34 |
| srichter | we need to attack fixing those problems | 16:34 |
| philiKON | yup | 16:36 |
| philiKON | basically making docstrings rest compliant | 16:36 |
| srichter | yes | 16:36 |
| *** anguenot has joined #zope3-dev | 16:36 | |
| *** jinty_ has joined #zope3-dev | 16:38 | |
| *** dlk has joined #zope3-dev | 16:39 | |
| *** jvts has left #zope3-dev | 16:41 | |
| *** SteveA has quit IRC | 16:43 | |
| *** JoaoJoao has joined #zope3-dev | 16:43 | |
| JoaoJoao | good morning | 16:43 |
| *** jinty_ has quit IRC | 16:45 | |
| JoaoJoao | Is there a way to make a Zope3 server always do HTTP Basic Auth | 16:46 |
| srichter | what do you mean? This question does not make sense. | 16:47 |
| JoaoJoao | srichter: I have a PDA app that do POST requests to a Zope3 server and I'd like to make it use HTTP Basic Auth | 16:54 |
| *** jinty has quit IRC | 16:54 | |
| philiKON | JoaoJoao, protect it with a permission that the anonymous principal doesn't have | 16:54 |
| philiKON | that will make zope automatically request login information | 16:55 |
| philiKON | through whichever method you prefer | 16:55 |
| philiKON | http basic auth is just one | 16:55 |
| srichter | yeah, and the default in Basic Auth | 16:55 |
| *** baldtrol has joined #zope3-dev | 16:55 | |
| JoaoJoao | okay, thanks a lot | 17:01 |
| *** andres has joined #zope3-dev | 17:08 | |
| *** hdima has quit IRC | 17:12 | |
| baldtrol | hey all... i tossed this out to the zope3-users list (and in here way toward the end of the day yesterday), but if no one minds i'd like to ask again, just because i'm stumped... | 17:15 |
| baldtrol | running zope3.1 behind apache, i keep getting "ForbiddenAttribute: publishTraverse in traverseName" whenever a request looks for anything configured as a resource in browser:resource... | 17:17 |
| VladDrac | not if you access it directly? | 17:18 |
| baldtrol | nosir... on 8080 i get everything fine | 17:18 |
| *** SteveA has joined #zope3-dev | 17:19 | |
| VladDrac | check your zope's accesslog and see if apache somehow mangles the requests | 17:19 |
| baldtrol | yessir... i have, and i'm pretty sure it has to do with that, but i'm confused about what to do about it. everything i want to redirect is under a site named "agency_application", so my RewriteRule is "^/agency_application(/?.*)" | 17:22 |
| benji | baldtrol, that's the match part of the rewrite, what is the redirect part say? | 17:23 |
| baldtrol | but then all the traversals are looking for things at agency_application/@@/zope3.css (as an example) as opposed to /@@/zope3.css... but still, if I change the rewrite rule to /.* i still have the same issue... | 17:24 |
| baldtrol | the rest of the rewrite is: | 17:24 |
| baldtrol | http://localhost:8080/agency_application/++vh++http:localhost:80/agency_application/++$1 \ | 17:24 |
| baldtrol | [P,L] | 17:24 |
| baldtrol | which, per the zope3dev book and what i can find online, i think that's right (assuming, as i am, that i'm running zope and apache on the same box) | 17:25 |
| benji | and what does the URL look like when Zope sees it? | 17:25 |
| baldtrol | request url that is coupled with the error are like the following: http://localhost/agency_application/@@/zope3.js | 17:26 |
| baldtrol | thanks for helping me out (or at least chattin' with me about it... sometimes talking it over helps me understand it better) | 17:27 |
| benji | and if you put that URL in your browser it works? | 17:28 |
| *** dobee has quit IRC | 17:28 | |
| *** dlk has quit IRC | 17:28 | |
| baldtrol | nosir, that's the frustrating bit. I have a url that works... http://localhost/agency_application/1130357904.01075245452/agency_applicant/index.html (numbers are tmp while the object is created and worked through, before archiving), which returns the html based on the object views. | 17:29 |
| benji | what is the working form of the zope3.js URL you gave above? | 17:29 |
| baldtrol | but the url for @@/whatever.css or whatever.js, or .png... none of them work. | 17:29 |
| baldtrol | working form is: src="http://localhost:8080/@@/zope3.js" | 17:30 |
| benji | is "agency_application" a site? | 17:30 |
| baldtrol | it is... weird thing though (i had assumed this was a tangential issue, but it's a subclass of Folder, which lets me turn it into a site, but not manage it...) | 17:32 |
| *** alga has quit IRC | 17:32 | |
| benji | I think the problem is that when agency_application is asked for the zope3.js resource, it can't find it | 17:33 |
| benji | this is only a work-around, but add another rewrite so JS, CSS, and images are rewritten without the "agency_application" part and see what happens | 17:34 |
| baldtrol | i agree... the error and the way it's not returning my images, zope images, my css, and zope css, makes me think it's a traversal issue. and ok... i'll get on that. (brb, workplace issues calling my name) | 17:34 |
| baldtrol | thanks | 17:35 |
| benji | glad to help; what little I did :) | 17:35 |
| srichter | what do you guys think: Should the static apidoc generator use a config file or command line options for configurability? | 17:46 |
| andres | srichter, the best would be both, with commandline overwriting the configfile, or? | 17:47 |
| srichter | yeah, but it takes twice the work right now | 17:47 |
| J1m | srichter, look at the approach I took for the new test runner. | 17:49 |
| J1m | Basic idea: | 17:49 |
| J1m | - most of logic is in a module. The module defines default defaults | 17:49 |
| J1m | - A small script uses the module. This small script overrides the default defaults with defaults. Basically the script is the config file. | 17:50 |
| J1m | - User-supplied options override the defaults. | 17:50 |
| J1m | Low rent and flexibly enough imo. | 17:50 |
| srichter | ok, I have a look | 17:51 |
| J1m | It could be easily extended to load defaults from a config file. | 17:51 |
| J1m | but I doubt that is necessary, | 17:51 |
| srichter | right | 17:51 |
| srichter | me too | 17:51 |
| SteveA | it is nice if that happens in the snall script | 17:51 |
| SteveA | not in the library | 17:51 |
| srichter | I do not want to overdesign but remove some of the spghetti code | 17:51 |
| J1m | agreed | 17:51 |
| SteveA | because having the config file policy in the library makes problems if you don't want that | 17:52 |
| J1m | yup | 17:52 |
| srichter | btw, how is the Authentcation token for HTTP Auth calculated? | 17:52 |
| srichter | a md5 hash of user:pw? | 17:52 |
| SteveA | base64 digest | 17:52 |
| SteveA | of user:pw | 17:53 |
| SteveA | i think | 17:53 |
| srichter | thanks, I'll try | 17:53 |
| SteveA | it is in the spec for Basic auth | 17:53 |
| SteveA | digest auth is of course better ;-) | 17:53 |
| srichter | oh, I just need it for the static apidoc generator, so I don't care | 17:53 |
| baldtrol | benji: that worked. made my first rewrite rule: | 18:04 |
| baldtrol | RewriteRule ^/agency_application/(.*css|.*png|.*js) \ | 18:04 |
| baldtrol | http://localhost:8080/++vh++http:localhost:80/++/$1 \ | 18:04 |
| baldtrol | [P,L] | 18:04 |
| benji | baldtrol, well at least that's somethign :/ | 18:05 |
| baldtrol | heheheh | 18:05 |
| baldtrol | i mean, i can run it that way in production. it wouldn't be the most tangled apache config i've ever decided was "eh, good enough" | 18:05 |
| baldtrol | ;) | 18:05 |
| benji | yeah, me too :) | 18:05 |
| baldtrol | i just wasn't sure if there was something on the zope side that i'm doing wrong... | 18:06 |
| benji | I don't think so, I think it's in the rewrite, but I'd have to think about it harder | 18:06 |
| baldtrol | cool. thanks much man. | 18:07 |
| benji | NP | 18:07 |
| baldtrol | i'll post a reply to my own zope3-users question just so your sol'n is archived in these logs and those | 18:07 |
| *** j-w has quit IRC | 18:08 | |
| SteveA | resources should be rooted based on virtual hosting stuff | 18:11 |
| SteveA | not based on sites | 18:11 |
| *** xenru has joined #zope3-dev | 18:15 | |
| baldtrol | my pagetemplate usage of resources is always context/++resource++<resourcename> ...is that not right? | 18:17 |
| *** mohsen has joined #zope3-dev | 18:22 | |
| philiKON | that's correct | 18:26 |
| philiKON | the point is how that is rendered | 18:26 |
| *** mohsen has quit IRC | 18:27 | |
| *** stub has quit IRC | 18:33 | |
| *** alga has joined #zope3-dev | 18:33 | |
| d2m | i posted to zope-users mailing list about the problems to POST data to a zope3 server using httplib -- problems seem to be httplib related; it turned out that POSTs through urllib work just fine | 18:36 |
| d2m | what remains is the question if posting to /@@edit.html is necessary -- or better: how a default view for the POST method can be created/configured | 18:36 |
| philiKON | srichter, is it me or is the SiteManager.next attribute nowhere documented in an interface??? | 18:39 |
| philiKON | site managers are just assumed to have this attribute, or what? | 18:40 |
| JoaoJoao | how do I create a new zope role in my package's configure.zcml? | 18:40 |
| philiKON | JoaoJoao, <role /> | 18:41 |
| philiKON | JoaoJoao, look at etc/securitypolciy.zcml for examples | 18:41 |
| philiKON | srichter, never mind about the documentation of next | 18:48 |
| philiKON | see it now | 18:48 |
| *** sashav has joined #zope3-dev | 18:51 | |
| *** fdrake has quit IRC | 18:59 | |
| srichter | okay, I did my third closed run of the API doc generation and it seems to stabilize around 260 MB | 19:04 |
| srichter | on my laptop it takes 1 hour 20 mins to generate | 19:05 |
| philiKON | ouch | 19:06 |
| srichter | that's not bad | 19:06 |
| srichter | I hope you were not hoping for something smaller | 19:06 |
| philiKON | dn't care so much about size | 19:07 |
| philiKON | the time it takes to generate is just enormous | 19:07 |
| *** faassen has quit IRC | 19:07 | |
| philiKON | i wonder how big a tar.bz2 tarball of the whole thing would be | 19:07 |
| srichter | it is probably very very compressible, because a lot of information is duplicated | 19:08 |
| srichter | It tries to load up about 22000 links btw | 19:09 |
| srichter | some fail, which you could consider a ftest failure of course ;-) | 19:09 |
| srichter | parsing an HTML file takes also a long time | 19:12 |
| philiKON | ah, you're parsing each file? | 19:13 |
| srichter | of course, you need to get all the links | 19:14 |
| philiKON | hmm | 19:15 |
| tarek | srichter, i was wondering something about the tests we made yesterday | 19:31 |
| tarek | for instance: this was'nt failing on my box: http://buildbot.zope.org/Zope3%20trunk%202.4%20Linux%20tlotze/builds/99/ftest/0 | 19:32 |
| tarek | in this code | 19:33 |
| tarek | http://pastebin.com/407923 | 19:33 |
| tarek | there's a missing bracket (</param>) | 19:33 |
| tarek | it's not catched on my box | 19:33 |
| srichter | strange | 19:33 |
| srichter | no clue why that would be | 19:34 |
| *** alga has quit IRC | 19:34 | |
| *** deo has joined #zope3-dev | 19:37 | |
| *** tarek has quit IRC | 19:40 | |
| *** natea is now known as natea|out | 19:43 | |
| *** vlado has quit IRC | 19:49 | |
| *** benji has quit IRC | 19:53 | |
| *** MrTopf_ has quit IRC | 20:06 | |
| *** natea|out is now known as natea | 20:08 | |
| *** philiKON has quit IRC | 20:17 | |
| *** benji has joined #zope3-dev | 20:18 | |
| *** regebro has quit IRC | 20:26 | |
| *** alga has joined #zope3-dev | 20:27 | |
| *** Alef has joined #zope3-dev | 20:56 | |
| JoaoJoao | How do I grant permissions to users authenticated with a specific principal source | 21:01 |
| *** zbir has quit IRC | 21:10 | |
| *** andres has quit IRC | 21:13 | |
| benji | srichter, ayt? | 21:32 |
| *** natea has quit IRC | 21:52 | |
| JoaoJoao | I'm a little confused with PAU | 21:59 |
| JoaoJoao | I have built a principal source, and I want to grant all users authenticated from this principal source a special role | 22:00 |
| *** efge has quit IRC | 22:14 | |
| *** alienoid has quit IRC | 22:20 | |
| baldtrol | JoaoJoao, i've run into that same issue... i've tried it myself, and hadn't found a way to do it. | 22:21 |
| JoaoJoao | that's bad news =( | 22:28 |
| JoaoJoao | I can grant permissions for roles and principals | 22:29 |
| JoaoJoao | PAU is damn complex | 22:31 |
| J1m | JoaoJoao, you don't want to use a role for that. | 22:32 |
| J1m | Use a group. | 22:32 |
| J1m | It should be easy to arrange that all users from a principal source are in a group. | 22:32 |
| J1m | Then you can grant a permission to the group or assign a role to the group. | 22:33 |
| JoaoJoao | oh that's cool, thanks | 22:38 |
| J1m | BTW, I agree that pau is complex. Many situations are well served by that. | 22:39 |
| J1m | But maybe it would be word while to have a really simple ZODB based auth service that let you manage users and groups. | 22:39 |
| J1m | Might be nice for people getting started and for simpler sites. | 22:39 |
| JoaoJoao | J1m: Maybe a doc explaining such simple use cases would be enough | 22:40 |
| J1m | You mean a recipe for how to set it up. I agree. | 22:41 |
| J1m | Of course, pau could probably benefit a log from some UI work. | 22:41 |
| J1m | Volunteerrs would be much appreciates. | 22:41 |
| J1m | Garrett Smith done a ton of great work a few months ago. | 22:41 |
| J1m | Garrett Smith did a ton of great work a few months ago. | 22:42 |
| srichter | benji: what's up? (I am about to go though) | 22:47 |
| *** srichter has quit IRC | 22:53 | |
| *** mgedmin has quit IRC | 22:53 | |
| JoaoJoao | J1m: So, I only need to know how to put all users from a principal source in a group ;) | 22:57 |
| J1m | Yes, and you can do that with a subscriber on the principal creation events. | 23:00 |
| *** MJ has joined #zope3-dev | 23:00 | |
| *** JoaoJoao has quit IRC | 23:09 | |
| *** alga has quit IRC | 23:11 | |
| *** ignas has quit IRC | 23:13 | |
| *** anguenot has quit IRC | 23:23 | |
| *** benji has quit IRC | 23:31 | |
| *** baldtrol has left #zope3-dev | 23:48 | |
| *** fdrake has joined #zope3-dev | 23:51 | |
| fdrake | would anyone have a problem if I change zope.schema.interfaces.IIterableSource to extend zope.schema.interfaces.ISource? | 23:54 |
| fdrake | making the change does not cause any tests to break, and this only affects the trunk (3.2) | 23:55 |
| fdrake | the issue w/ the current arrangement is that a source that implements both depends on the order they're specified to select widgets registered for IIterableSource | 23:56 |
| fdrake | I don't think that's acceptable. | 23:56 |
| fdrake | (especially since I'm adding such a widget for 3.2) | 23:56 |
| fdrake | ok, silence indicates consent! :-) | 23:59 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!