*** projekt01 has quit IRC | 00:18 | |
*** tvon has quit IRC | 00:20 | |
*** bskahan has joined #zope3-dev | 00:50 | |
*** SureshZ has left #zope3-dev | 00:50 | |
*** philiKON has quit IRC | 00:51 | |
srichter | J1m: what is the latest way to make a release? | 00:57 |
---|---|---|
srichter | I cannot build a package with my old script anymore | 00:57 |
srichter | did you remove the X? | 00:57 |
J1m | Yes | 00:58 |
J1m | Look at what I checked in in releases | 00:58 |
J1m | I checkd in a "test" script | 00:58 |
srichter | ok, this is the same I had as a shell script ;-) | 00:58 |
J1m | Note that it assumes that that zpkgtools checkout is a sibling to the zope checkout | 00:59 |
srichter | like my setup :-) | 00:59 |
J1m | cool | 00:59 |
J1m | and it uses a local zope map that has relative path references in it. | 01:00 |
J1m | This wasn't possible until a couple of weeks ago | 01:00 |
srichter | ok | 01:01 |
srichter | J1m: I get an error: | 01:06 |
srichter | tar xozf Zope-0.0.0.tgz | 01:06 |
srichter | ./configure --prefix `pwd`/z | 01:06 |
srichter | ./configure: line 24: syntax error near unexpected token `<<<' | 01:06 |
srichter | ./configure: line 24: `<<<<<<< .mine' | 01:06 |
srichter | someone did not clean up something (this is a new pure checkout | 01:06 |
srichter | oh ok, it might be zpckgtools, which I modified before | 01:07 |
srichter | my bad | 01:07 |
*** rk_ has joined #zope3-dev | 01:22 | |
*** tvon has joined #zope3-dev | 01:30 | |
*** xerophyte has left #zope3-dev | 01:48 | |
*** rk_ has quit IRC | 01:54 | |
*** bskahan has quit IRC | 02:01 | |
J1m | srichter, how's it going? | 02:20 |
*** J1m has quit IRC | 02:21 | |
*** bskahan has joined #zope3-dev | 02:34 | |
*** projekt01 has joined #zope3-dev | 03:02 | |
*** yota has quit IRC | 03:04 | |
*** dagnachew has joined #zope3-dev | 03:13 | |
*** bskahan has quit IRC | 03:30 | |
*** tarek has quit IRC | 03:42 | |
*** projekt01 has quit IRC | 03:45 | |
*** stub has joined #zope3-dev | 03:50 | |
* dagnachew is away: supper ! | 03:50 | |
*** dagnachew has quit IRC | 05:49 | |
*** stub has quit IRC | 06:30 | |
*** bradb is now known as bradb-afk | 07:02 | |
*** strichter has joined #zope3-dev | 09:03 | |
*** srichter has quit IRC | 09:03 | |
*** SureshZ has joined #zope3-dev | 09:24 | |
*** SureshZ has left #zope3-dev | 09:37 | |
*** timte has joined #zope3-dev | 09:54 | |
*** philiKON has joined #zope3-dev | 10:42 | |
*** philiKON has joined #zope3-dev | 10:51 | |
*** jhauser has quit IRC | 11:04 | |
*** philiKON has quit IRC | 11:10 | |
*** timte has quit IRC | 12:16 | |
*** yota has joined #zope3-dev | 13:13 | |
*** projekt01 has joined #zope3-dev | 13:23 | |
*** debugger has joined #zope3-dev | 13:28 | |
*** andrew_m has joined #zope3-dev | 13:36 | |
*** philiKON has joined #zope3-dev | 14:10 | |
andrew_m | i'm having some problems with logging out of zope3. does anyone know if that's a zope, browser or configuration issue? | 14:22 |
VladDrac | could be a browser issue - some browsers have difficulty clearing the http authentitacion | 14:23 |
VladDrac | ..cation | 14:23 |
* VladDrac uses ff webdev extensions to be sure | 14:23 | |
andrew_m | thanks - is that something that fixes the problem e.g. on firefox? | 14:25 |
VladDrac | yeah (ff = firefox) | 14:25 |
VladDrac | it has a 'clear http authentication' option | 14:25 |
andrew_m | i see.. i'll have a look at that, thanks | 14:27 |
*** philiKON has quit IRC | 14:31 | |
andrew_m | VladDrac: hmm.. before i spend my whole weekend searching for that extension ;), any hints where to find that? | 14:36 |
VladDrac | let's see | 14:36 |
*** J1m has joined #zope3-dev | 14:37 | |
VladDrac | very annoying, firefox extensions urls now force you to a mozilla firefox upgrade page | 14:38 |
VladDrac | http://chrispederick.com/work/firefox/webdeveloper/ | 14:38 |
andrew_m | oke, thanks.. was looking on the official firefox extensions page | 14:39 |
andrew_m | VladDrac: do you make your users install that when they use firefox? | 14:40 |
VladDrac | no | 14:43 |
VladDrac | I use it as a developer | 14:43 |
*** bskahan has joined #zope3-dev | 14:47 | |
andrew_m | ic.. i guess for the user the only way to log out then is to close the browser for now | 14:47 |
VladDrac | yup | 14:47 |
VladDrac | or switch to some sort of cookie based authentication | 14:47 |
andrew_m | hmyeah.. | 14:48 |
J1m | like session auth which is provided by zope.app.authentication | 14:48 |
andrew_m | J1m: ok, that sounds like an option to try for me | 14:48 |
*** strichter is now known as srichter | 14:53 | |
*** ChanServ sets mode: +o srichter | 14:53 | |
projekt01 | Jim, do you have time to answer a short question? | 14:54 |
srichter | andrew_m: HTTP Authentication does not have the concept of logout | 14:54 |
J1m | projekt01, sure | 14:55 |
projekt01 | What's the best way to fire a event in the method directlyProvide() | 14:55 |
srichter | andrew_m: you can only rechallenge, but the browser keeps the old settings, unless the new ones are accepted | 14:55 |
projekt01 | ;-) | 14:55 |
projekt01 | Replace the interface module? | 14:55 |
J1m | uh, yes | 14:56 |
J1m | srichter, how goes the release? | 14:56 |
SteveA | projekt01: provide your own API that fires the event you want, and calls the zope.interface.diectlyProvides() | 14:56 |
andrew_m | srichter: ok, that's good to know | 14:56 |
srichter | I have started last evening and the functional test seems mysterios to me. I do have a plan for the import thingy though | 14:57 |
srichter | projekt01: I agree with SteveA | 14:57 |
projekt01 | But if I use a method hook, all other packages don't use this and I can't exactly control this part | 14:58 |
srichter | projekt01: right, but it is very unlikely that you are in general interested in knowing who got a directlyProvided interface | 15:00 |
projekt01 | Other packages = 3rd party packages | 15:00 |
srichter | for example, I doubt that you are interested in the skin the request has (which is a directlyProvides() call) | 15:00 |
projekt01 | I'm interested to control the "directly provided" interface order | 15:01 |
SteveA | that's like saying "i want to hook into all method calls" | 15:01 |
J1m | you definately don't want to change the order implicitly | 15:01 |
SteveA | it's hooking into a low-level interface that is used for very many things | 15:01 |
srichter | but you are only interested in doing this in a particular context, such as your specific content types or so | 15:02 |
projekt01 | But nobody can say which order this "directly provided" interface really have, two objects of the same type can have different orders | 15:02 |
J1m | directlyProvides completely specifies the order by the order of its arguments. | 15:03 |
J1m | That is explicit. | 15:03 |
J1m | It would be evil to change that. | 15:03 |
J1m | If I say: directlyProvides(o, I1, I2) | 15:04 |
J1m | It would be bad if something switched the order of I1 and I2 behind the scenes. | 15:04 |
projekt01 | Yes, but if I directlyProvide(IA, [Iother]) and directlyProvide(IB, [Iothers]) or directlyProvide(IB, [Iothers]) and then directlyProvide(IA, [Iother]) I get a different order | 15:04 |
projekt01 | First I get (IA, IB) and second I get (IB, IA) | 15:05 |
projekt01 | Sorry, forgot the Iothers | 15:05 |
J1m | I find that a bit hard to believe, since directlyProvides replaces the directly provided interfaces. | 15:06 |
projekt01 | If I directlyProvide a Interface I append it to the directlyProvided interface (each time) and this will produce different orders | 15:07 |
projekt01 | If we directlyProvide different Interfaces | 15:07 |
projekt01 | The interface order depends on the order you call the different directlyProvide at all and not how you call the method, | 15:09 |
projekt01 | Because if you call directlyProvide you don't take care on other interfaces orders (normaly) where the object allready provides | 15:10 |
J1m | no, directlyProvides does not append | 15:10 |
J1m | >>> o = C() | 15:10 |
J1m | >>> directlyProvides(o, I1, I3) | 15:10 |
J1m | >>> list(providedBy(o)) | 15:10 |
J1m | [<InterfaceClass __main__.I1>, <InterfaceClass __main__.I3>] | 15:10 |
J1m | >>> directlyProvides(o, I2, I3) | 15:10 |
J1m | >>> list(providedBy(o)) | 15:10 |
J1m | [<InterfaceClass __main__.I2>, <InterfaceClass __main__.I3>] | 15:10 |
J1m | >>> o = C() | 15:10 |
J1m | >>> directlyProvides(o, I2, I3) | 15:10 |
J1m | >>> directlyProvides(o, I1, I3) | 15:11 |
J1m | >>> list(providedBy(o)) | 15:11 |
J1m | [<InterfaceClass __main__.I1>, <InterfaceClass __main__.I3>] | 15:11 |
J1m | >>> | 15:11 |
projekt01 | The method does not append but if we use the directlyProvide we put the additional interface in front or at the end (normaly) | 15:13 |
projekt01 | We don't take care on orders | 15:13 |
projekt01 | And this is like append, it depends what you do first | 15:13 |
projekt01 | And what next and last | 15:13 |
J1m | The directly provided interfaces get combined with the class implemented interfaces. | 15:14 |
J1m | This happens in a fixed way | 15:14 |
J1m | it has no dependence on ordr of directlyProvides calls. | 15:14 |
srichter | that's because all these pieces of the framework do not care about the order, since the directly provided interfaces are usually unrelated to each other | 15:14 |
J1m | srichter, that's often not true. | 15:15 |
J1m | Often you do care about the order. | 15:15 |
J1m | Sometimes, one would like to directlyProvide an interface and have it take a lower precedence than existing interfaces. | 15:15 |
srichter | but I meant that the various packages that might directly provide an interface on the request, for example, do not care about the order | 15:16 |
J1m | There are similar issues with the interface combinations that happen with decorators. | 15:16 |
J1m | srichter, usually that is true, yes. | 15:16 |
srichter | for example, the skin code does not care about the order of the other interfaces; it only cares about finding the skin interface | 15:16 |
* J1m expects SteveA to say he wishes nothing depended on interface order. | 15:16 | |
projekt01 | srichter, if the don't force using different adapters yes, otherwise no | 15:17 |
projekt01 | SteveA, hm, yes and no, it could be a interesting pattern if we can take really care on that part. | 15:18 |
J1m | projekt01, I could see having a flavor of directlyProvides that put some directly-provided interfaces after the implemented ones. | 15:18 |
J1m | I certainly wouldn't do anything about this using events. | 15:18 |
SteveA | i wonder about having an option to say "adapt, provided it isn't ambiguous" | 15:19 |
SteveA | i've needed this for some use of getting adapters to determine authorization | 15:19 |
SteveA | where having ambiguity may mean the programmer has not realized something, and made a mistake | 15:19 |
J1m | It's never ambiguous :) | 15:19 |
SteveA | for the whole system, yes | 15:20 |
SteveA | from the partial knowledge of one developer, it often is | 15:20 |
SteveA | or rather, it is easy to get the wrong idea | 15:20 |
SteveA | which is not good, where security is concerned | 15:20 |
SteveA | now, you could say "don't use adapters for security then" ;-) | 15:20 |
J1m | :) | 15:20 |
SteveA | but, in this case, my infrastructure raises an exception when there is such ambiguity | 15:21 |
J1m | How do you define ambiguity? | 15:21 |
SteveA | in this particular case, when one name is in more than one interfaces provided by an object, where one of those interfaces does not extend the other | 15:22 |
SteveA | i'm looking up an adapter that is going to say who is authorized to do 'permission' on that name | 15:22 |
SteveA | oh, one thing i've come across a few times that seems to be missing from zope.interface | 15:23 |
J1m | That seems like a valid strategy | 15:23 |
J1m | That seems like a intresting strategy | 15:23 |
J1m | That seems like a interesting strategy | 15:23 |
projekt01 | SteveA, I don't understand, what have a name of a interface to do with that? You mean attribute name? | 15:24 |
SteveA | is to be able to say not IFoo(object) or getAdapter(IFoo, object), but getAdapterSpecificallyFor(IFoo, object, specific_iterface=IThingObjectHas) | 15:24 |
SteveA | or otherwise, getAdapterFactory(IThing, IFoo) | 15:24 |
SteveA | although, i'd also have to say how many dependents i have, and the name | 15:24 |
SteveA | projekt01: by 'a name in an interface', i'm talking about an attribute name | 15:25 |
SteveA | that is, an attribute that is described by that interface | 15:25 |
J1m | SteveA, you want adapter super IOW. | 15:25 |
SteveA | or, described within the interface, if you prefer | 15:25 |
* SteveA tries to remember exactly what super does | 15:26 | |
J1m | I plan a redesign of the adapter registry that would allow super operations. | 15:26 |
projekt01 | SteveA, Ok, I see, it sounds interesing | 15:26 |
J1m | It is useful in inheritence for looking up a method that a method overrides. | 15:26 |
SteveA | i'm not sure i want adapter super | 15:26 |
J1m | In the adapter case, it would be used by an adapter to call the adapter it overrised. | 15:27 |
SteveA | but i'm not sure i don't | 15:27 |
SteveA | when you say getAdapter(IFoo, obj), then all interfaces provided by obj are considered, in a particular order | 15:27 |
J1m | I wanted to do this for 3.1, but had too much customer work. | 15:27 |
SteveA | what I want to do is to look up IFoo for a particular interface that I choose | 15:27 |
SteveA | right now, i get around it by making an object that provides the one interface i'm interested in | 15:28 |
J1m | You can do that now in 2 steps. | 15:28 |
SteveA | and say IFoo(object_that_provides_IBar_only) | 15:28 |
SteveA | darn customers, always getting in the way of writing software... | 15:28 |
J1m | You can get the adapter registry and call lookup on it. | 15:28 |
J1m | Yeah, they're a real pain sometimes | 15:29 |
J1m | The lookup fuction takes interface specifications | 15:29 |
J1m | It returns a factory, which you can then call. | 15:29 |
J1m | So, it should be straightforward to implement an api like you want. | 15:29 |
SteveA | okay, i'll take a look. i'll need to see how names fit it too. | 15:29 |
SteveA | thanks | 15:30 |
SteveA | hmm | 15:30 |
SteveA | super opertaions + events sounds a bit like partial adapters | 15:30 |
J1m | uh | 15:31 |
J1m | I supose super could be used to implement partial adapters. | 15:31 |
J1m | Not sure how events fit in. | 15:31 |
projekt01 | SteveA, J1m, srichter, thanks for the hints, I have to leave now, nice weekend and see you next time | 15:32 |
srichter | bye | 15:32 |
*** J1m has quit IRC | 15:36 | |
*** projekt01 has quit IRC | 15:52 | |
*** mikka__ has joined #zope3-dev | 16:05 | |
*** timte has joined #zope3-dev | 16:10 | |
*** MiUlEr has quit IRC | 16:18 | |
*** bskahan has quit IRC | 16:43 | |
*** nederhoed has joined #zope3-dev | 16:50 | |
*** anguenot has joined #zope3-dev | 16:51 | |
*** mikka__ has quit IRC | 17:17 | |
*** Aiste has quit IRC | 17:18 | |
*** ignas has joined #zope3-dev | 17:35 | |
*** garrett-smith has joined #zope3-dev | 18:51 | |
*** garrett-smith has left #zope3-dev | 18:51 | |
*** ignas has quit IRC | 18:51 | |
nederhoed | how can I access the standardmacros from a page template that I add using the management interface? | 19:01 |
nederhoed | <html | 19:02 |
nederhoed | metal:use-macro="views/standard_macros/view"> | 19:02 |
nederhoed | results in the following error | 19:02 |
nederhoed | Module zope.pagetemplate.pagetemplate, line 118, in pt_render | 19:03 |
nederhoed | Warning: Macro expansion failed | 19:03 |
nederhoed | Warning: exceptions.KeyError: 'views' | 19:03 |
nederhoed | anyone? | 19:03 |
*** projekt01 has joined #zope3-dev | 19:15 | |
srichter | use context/@@standard_macros | 19:33 |
srichter | and also, this only works for filesystem-based development | 19:33 |
srichter | no TTW supported | 19:33 |
*** SureshZ has joined #zope3-dev | 19:56 | |
*** anguenot has left #zope3-dev | 20:22 | |
nederhoed | aha | 20:23 |
nederhoed | merci | 20:23 |
nederhoed | yes! that worked, thank you | 20:26 |
*** bskahan has joined #zope3-dev | 21:15 | |
*** J1m has joined #zope3-dev | 21:49 | |
J1m | srichter, ayt? | 21:50 |
srichter | J1m: yep | 21:50 |
J1m | I just sent you a note. | 21:51 |
srichter | I am sending the release notes right now | 21:51 |
J1m | There is now a separate release for windows. | 21:51 |
srichter | ok, that's what I thought | 21:51 |
srichter | so this will be the Windows source release that Tim will use | 21:51 |
J1m | yes | 21:52 |
J1m | It includes some extra files to support running as a service. | 21:52 |
srichter | btw, we really need to share the *.cfg files between Zope-Win and Zope, so that I will not forget to updat them | 21:52 |
srichter | does SVN support links? | 21:52 |
J1m | svn has externals, but I'm told that you can't use them with files. | 21:53 |
srichter | ok | 21:53 |
J1m | Most config files are shared. | 21:53 |
J1m | Zope-win is very small and builds on Zope | 21:53 |
srichter | ok, so I guess I have to live with that for now | 21:53 |
srichter | but PUBLICATION.cfg, for example, is duplicated | 21:53 |
J1m | There's not much to live with | 21:53 |
J1m | That is the only one. | 21:53 |
srichter | ah, since you are here; I think we can remove ReleaseSupport now, right? | 21:54 |
srichter | ok, good to know | 21:54 |
J1m | what's that? | 21:54 |
srichter | it is a directory in the Zope repository that we used for maps to create releases | 21:54 |
J1m | No, I don't think we are ready to get rid of it. | 21:55 |
srichter | really? | 21:55 |
srichter | I built the release totally without it | 21:55 |
srichter | you basically copied everything interesting into releases | 21:55 |
J1m | Yes, but there are ather releases supported there, | 21:55 |
J1m | Yes, for Zope 3. | 21:56 |
J1m | Maybe we should get rid of the zope3.map from there. | 21:56 |
srichter | (except for a couple of map files I created to package zwiki, bugtracker, psycopgda and mysqlda) | 21:56 |
srichter | oh, maybe I can create similar releases directories for those packages | 21:56 |
srichter | and for zwiki and bugtracker I simply add them to Zope's | 21:57 |
J1m | But I suspect that other releases use the zope3.map | 21:57 |
srichter | mmh, maybe | 21:57 |
srichter | We leave it there, until I release those products for 3.1 | 21:57 |
J1m | I think fred uses it for zope.interface. | 21:58 |
srichter | I see | 21:58 |
srichter | that could move to Zope3/releases as well | 21:58 |
J1m | well, I guess the zope,interface release could use the map that's already there. | 21:59 |
srichter | yep | 21:59 |
J1m | Congrats on the release! | 22:02 |
J1m | Thanks! | 22:02 |
srichter | thank you | 22:03 |
srichter | I know you did a lot of work there too | 22:03 |
srichter | btw, I decided not to create a branch yet and keep the feature freeze for while longer | 22:03 |
J1m | why? | 22:03 |
srichter | this way Julien, Dimitry and other bug fixers have an easier time | 22:03 |
J1m | Now that you mention it, I was going to complain about that. | 22:04 |
srichter | LOL | 22:04 |
srichter | we have the tag | 22:04 |
J1m | have you announced a feature freeze? | 22:04 |
srichter | yeah, we did that a long time back | 22:04 |
srichter | I will send another message in a moment | 22:04 |
J1m | well, you should announce one now. | 22:04 |
J1m | Especially since we don't have a branch. | 22:04 |
srichter | done | 22:10 |
bskahan | srichter, J1m: very nice | 22:10 |
srichter | J1m: does a news item take a while to appear on the front page after it is published? | 22:14 |
J1m | I have no idea. | 22:14 |
srichter | ok, I'll just wait a few mins then | 22:14 |
srichter | J1m: will Zope-win also run on Linux? | 22:18 |
J1m | yes | 22:19 |
srichter | ok, then I can test it | 22:19 |
J1m | yes | 22:19 |
srichter | J1m: I saw that you decided not to include versioncontrol | 22:20 |
J1m | yes, or wfmc | 22:21 |
srichter | right, I figured you wanted to wait with wfmc | 22:21 |
J1m | I don't know that anyone but us is interested in using versioncontrol. | 22:21 |
srichter | right | 22:22 |
srichter | I think people are interested, but they don't like the approach | 22:22 |
srichter | Florent said that CPS does it another way which he likes better | 22:22 |
srichter | and wants to use for Z3 ECM | 22:23 |
J1m | I like it better too, if I understand it correctly. | 22:23 |
srichter | I did not follow the discussion | 22:24 |
J1m | Was there a discussion? | 22:25 |
srichter | on the z3labs list there was a brief one | 22:26 |
*** bskahan has quit IRC | 22:33 | |
srichter | arggggggggghhhhhhhhhh, I hate zope.org | 22:52 |
srichter | it never does what I want | 22:52 |
srichter | J1m: even though I have published everyhting in my new Software release Products/Zope3 is broken | 22:53 |
srichter | do you know why? | 22:53 |
srichter | especially since this works: http://www.zope.org/Products/Zope3/swpackage_view | 22:55 |
*** tvon has quit IRC | 22:59 | |
srichter | d2m: are you around? | 23:03 |
srichter | d2m_: ping | 23:03 |
d2m | srichter: hi | 23:04 |
srichter | d2m: are you on the Web team? | 23:04 |
d2m | yes | 23:04 |
srichter | d2m: Because you are the only one in the #zope-web channel | 23:04 |
srichter | I really need your help | 23:05 |
d2m | ;) | 23:05 |
srichter | for some reason http://www.zope.org/Products/Zope3/ does not work | 23:05 |
srichter | and I just sent an announcement providing this URL | 23:05 |
srichter | some priv issue | 23:05 |
srichter | on the other hand this works: http://www.zope.org/Products/Zope3/swpackage_view | 23:05 |
srichter | should I just create an index_html that forwards to this view? | 23:06 |
d2m | ok, must be a 'private' object somewhere -- i'll check the folder | 23:06 |
srichter | I thought I published everything | 23:06 |
srichter | it stopped working after I added the beta 1 Windows file | 23:06 |
srichter | also, my news item did not make it to the news list | 23:07 |
*** dagnachew has joined #zope3-dev | 23:09 | |
d2m | srichter: checking.... | 23:10 |
srichter | d2m: thanks a lot! | 23:10 |
srichter | d2m: quick in dirty is better than slow and correct, right now :-) | 23:10 |
d2m | srichter: http://www.zope.org/Products/Zope3/ works for me now, http://www.zope.org/News/ and http://www.zope.org/news.rss too | 23:13 |
srichter | ok, what did you do? | 23:14 |
srichter | does it just work? | 23:14 |
srichter | yipee, for me too :-) | 23:14 |
srichter | d2m: so you gotta tell me what was wrong | 23:15 |
srichter | because it is release season I have to play this game a couple of times in the next weeks | 23:15 |
d2m | srichter: no idea, i just hit it a bit :) | 23:15 |
srichter | ooooohhhhhhhh, no! | 23:15 |
srichter | its the zope.org ghost again :-) | 23:16 |
d2m | srichter: well, the NewsItem had no EffectiveDate set | 23:16 |
srichter | ahh, I see, good to know that you need this | 23:16 |
srichter | same for the other objects? | 23:16 |
d2m | the NewsItem should show up on frontpage within the next minutes | 23:16 |
srichter | cool | 23:17 |
srichter | thanks a whole lot! | 23:18 |
d2m | srichter: what is the difference between the 2 release files ? | 23:33 |
*** gsbain has joined #zope3-dev | 23:41 | |
srichter | the windows one installs a fix, so that the release will work with Windows services | 23:41 |
d2m | i see, ok -- great news btw ! | 23:42 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!