| *** m8 has quit IRC | 00:03 | |
| *** supton has quit IRC | 00:03 | |
| *** Wu has joined #zope | 00:10 | |
| *** supton has joined #zope | 00:17 | |
| *** Wu has quit IRC | 00:17 | |
| *** Wu has joined #zope | 00:19 | |
| *** TresEquis has joined #zope | 00:21 | |
| *** MrTango has quit IRC | 00:33 | |
| *** TresEquis has quit IRC | 01:04 | |
| *** sp0cksbeard has quit IRC | 01:27 | |
| *** Wu has quit IRC | 01:38 | |
| *** alga has quit IRC | 01:44 | |
| *** mr_jolly has quit IRC | 01:46 | |
| *** John[a] has quit IRC | 02:44 | |
| *** srichter has quit IRC | 02:45 | |
| *** srichter has joined #zope | 02:46 | |
| *** mcdonc has quit IRC | 03:04 | |
| *** mcdonc has joined #zope | 03:13 | |
| *** tiwula has quit IRC | 03:23 | |
| *** webmaven has quit IRC | 03:30 | |
| *** John[a] has joined #zope | 03:42 | |
| *** Arfrever has quit IRC | 03:46 | |
| *** davisagli has quit IRC | 04:18 | |
| *** davisagli has joined #zope | 04:19 | |
| *** davisagli has quit IRC | 04:22 | |
| *** davisagli has joined #zope | 04:23 | |
| *** tiwula has joined #zope | 04:41 | |
| *** daMaestro has quit IRC | 05:00 | |
| *** John[a] has quit IRC | 05:05 | |
| *** davetoo has joined #zope | 05:52 | |
| *** dayne has joined #zope | 06:26 | |
| *** tiwula has quit IRC | 07:09 | |
| *** davetoo has quit IRC | 07:15 | |
| *** povbot has joined #zope | 07:22 | |
| *** davisagli has quit IRC | 07:25 | |
| *** srichter has quit IRC | 07:26 | |
| *** davisagli has joined #zope | 07:26 | |
| *** dayne has quit IRC | 07:53 | |
| *** hever has joined #zope | 08:02 | |
| *** menesis has joined #zope | 08:31 | |
| *** tisto has joined #zope | 08:35 | |
| *** sm has quit IRC | 08:43 | |
| *** hever has quit IRC | 08:51 | |
| *** hever has joined #zope | 08:57 | |
| *** zagy has joined #zope | 08:59 | |
| *** __mac__ has joined #zope | 08:59 | |
| *** zagy has quit IRC | 09:00 | |
| *** wosc has joined #zope | 09:00 | |
| *** slackrunner has quit IRC | 09:09 | |
| *** JT has quit IRC | 09:29 | |
| *** JT has joined #zope | 09:32 | |
| *** JT has quit IRC | 09:36 | |
| *** JT has joined #zope | 09:42 | |
| *** MrTango has joined #zope | 09:45 | |
| *** agroszer has joined #zope | 09:50 | |
| *** agroszer has quit IRC | 10:02 | |
| *** avoinea1 has joined #zope | 10:03 | |
| *** ccomb1 has quit IRC | 10:03 | |
| *** kleist has joined #zope | 10:04 | |
| *** avoinea1 has quit IRC | 10:05 | |
| *** planetzopebot has quit IRC | 10:08 | |
| *** avoinea1 has joined #zope | 10:08 | |
| *** planetzopebot has joined #zope | 10:09 | |
| *** avoinea1 has left #zope | 10:11 | |
| *** agroszer has joined #zope | 10:11 | |
| *** shastry has quit IRC | 10:11 | |
| *** shastry has joined #zope | 10:14 | |
| *** alga has joined #zope | 10:23 | |
| *** humanfromearth has joined #zope | 10:23 | |
| *** humanfromearth has left #zope | 10:23 | |
| *** alexpilz has joined #zope | 10:30 | |
| *** Wu has joined #zope | 10:41 | |
| *** hever has quit IRC | 10:44 | |
| *** alga has quit IRC | 10:45 | |
| *** hever has joined #zope | 10:55 | |
| *** goschtl has joined #zope | 10:58 | |
| *** kosh has quit IRC | 11:11 | |
| *** kosh has joined #zope | 11:17 | |
| *** kosh has quit IRC | 11:23 | |
| *** kosh has joined #zope | 11:24 | |
| *** menesis has quit IRC | 11:28 | |
| *** menesis has joined #zope | 11:29 | |
| *** Gogo|gui has joined #zope | 11:32 | |
| *** menesis has quit IRC | 11:35 | |
| *** John[a] has joined #zope | 11:38 | |
| *** John[a] has quit IRC | 11:43 | |
| *** alga has joined #zope | 11:45 | |
| *** sylvain has joined #zope | 11:47 | |
| *** Ariel_Calzada has joined #zope | 11:55 | |
| *** TomBlockley has joined #zope | 11:57 | |
| *** thevishy has joined #zope | 12:15 | |
| thevishy | How does Zope doeal with HTTRequest ? | 12:15 |
|---|---|---|
| thevishy | I presume its using HTTPRequest.py module ? | 12:15 |
| *** mitchell`off is now known as mitchell` | 12:15 | |
| *** tisto is now known as tisto|lunch | 12:16 | |
| kosh | not sure waht you are asking | 12:23 |
| thevishy | I mean whats the basic controller in Zope | 12:26 |
| thevishy | to handle user requests | 12:26 |
| *** Gogo|gui has quit IRC | 12:26 | |
| thevishy | the initiial page is a index.html | 12:26 |
| thevishy | Correct ? | 12:27 |
| kosh | index_html for zope 2.x by default in the root of the zodb | 12:27 |
| kosh | REQUEST/RESPONSE are part of ZPublisher | 12:27 |
| thevishy | Yes ZPublisher | 12:27 |
| kosh | I still don't get what you are actually really asking about though | 12:28 |
| thevishy | ZPublisher/HTTRequest.py is there right ? What is its function | 12:28 |
| kosh | it has the REQUEST and RESPONSE objects used in fulfilling a request | 12:28 |
| kosh | what specficially are you actually trying to solve? | 12:28 |
| kosh | also what version of zope are you using? | 12:29 |
| thevishy | Okay so any HTTP request I send to a Zope server goes to REQUEST / RESPONSE right ? | 12:29 |
| thevishy | I am trying to implement a JSON handler for Zope 2 | 12:29 |
| kosh | it ends up in them one way or another but JSON is normally sent over http so I don't see what makes JSON special for that | 12:30 |
| kosh | when I did sending and receiving of JSON I just did that instead of html, nothing special | 12:30 |
| kosh | REQUEST/RESPONSE don't change it | 12:30 |
| thevishy | kosh : our idea is simple , we have added a TinyMCE editor object into Zope | 12:31 |
| thevishy | Now the TinyMCE editor has a button that sends JSON requests | 12:31 |
| thevishy | but Zope2 doesnt know to handle the data and its getting trimmed | 12:32 |
| thevishy | so our idea is to get this data at the server side | 12:32 |
| thevishy | I am new into web development so figuring out lot of things | 12:32 |
| kosh | zope should not be trimming any data | 12:32 |
| kosh | all you have is GET and POST and considering the length of data you probably have from TinyMCE it should be doing a POST to a url on the server, so the data will be in a form var in REQUEST.form['somevarname'] and that data would be in JSON format | 12:33 |
| thevishy | in the TinyMce.py , we started a debugger and we dont see the JSON data though we can see Cookies | 12:33 |
| kosh | use a network analyzer like wireshark | 12:33 |
| thevishy | ok let me check that method | 12:34 |
| kosh | see how the data is actually sent from the browser to the server | 12:34 |
| kosh | make sure that it actually sends the right data to the right url in some sane manner | 12:34 |
| kosh | once you know that for certain then it is time to figure out what is going on in the zope end | 12:34 |
| thevishy | It does and the proof of that is , in HTTPRequest.py , we can intercept the full data | 12:34 |
| kosh | what doy ou mean by intercept it? | 12:34 |
| *** teix has joined #zope | 12:34 | |
| kosh | what var is it stored under? why do you think it is being truncated? | 12:35 |
| thevishy | Wait | 12:35 |
| thevishy | I will just check with a debugger and tell you | 12:36 |
| kosh | so you see the whole thing in the debugger but then later you see only part of it? | 12:36 |
| *** Wu has quit IRC | 12:37 | |
| *** eperez has joined #zope | 12:40 | |
| *** evilbungle has joined #zope | 12:53 | |
| *** Gogo|gui has joined #zope | 12:56 | |
| *** alexpilz has quit IRC | 12:59 | |
| thevishy | Actually I am not able to reproduce what my colleague did before | 13:00 |
| thevishy | I need to see the self object for the JSON request coming to the server | 13:00 |
| kosh | self object for JSON request? that does not realy make sense | 13:01 |
| thevishy | kosh : thats right , we see the whole thing in the HTTRequest.py Module and then at TinyMCE we see that JSON data is not arriving | 13:01 |
| kosh | you have POST and GET for how you work with the server | 13:01 |
| thevishy | I mean I need to see the request object | 13:01 |
| thevishy | when I click on a JSON POST | 13:01 |
| kosh | tinemce would have to POST the data to zope and it would arrive as a string | 13:01 |
| thevishy | does that make sense ? | 13:01 |
| kosh | so you will have a string on REQUEST.form['somevarname'] depending on what you sent it as | 13:02 |
| thevishy | Yes it does a HTTP POST with content as application/json | 13:02 |
| kosh | there is no self for that, it is just a string | 13:02 |
| thevishy | right let me check REQUEST | 13:02 |
| kosh | on the page you are posting this data to print out REQUEST | 13:02 |
| kosh | the data you are trying to use should be in REQUEST.form | 13:02 |
| *** Gogo|gui has quit IRC | 13:03 | |
| thevishy | let me check that one | 13:03 |
| *** Gogo|gui has joined #zope | 13:04 | |
| *** digitalmortician has joined #zope | 13:04 | |
| *** Gogo|gui has quit IRC | 13:08 | |
| *** Gogo|gui has joined #zope | 13:10 | |
| thevishy | Zope receives HTTPReuquest objects and how does it decide where to give it ? | 13:11 |
| thevishy | When I make a request , it creates a HTTPRequest object and then forwards it to another object for doing the ncessary stuff | 13:12 |
| thevishy | right ? | 13:12 |
| CIA-89 | tlotze 2 * r121682 zc.buildout/src/zc/buildout/bootstrap.txt: fixed whitespace in test expectation | 13:18 |
| CIA-89 | tlotze 2 * r121683 zc.buildout/src/zc/buildout/tests.py: fixed a test for all Python versions supported by consistently relying on a newly introduced normalizer for pyc files in directory listings | 13:18 |
| kosh | the url you are working with | 13:18 |
| kosh | so if you do a POST to /foo/bar/baz then baz is the code that will be run and the code has access to the REQUEST object | 13:19 |
| kosh | basically you don't worry about HTTPReques objects | 13:21 |
| kosh | you just grab what you need from REQUEST when your code runs | 13:21 |
| *** Gogo|gui has left #zope | 13:36 | |
| *** alexpilz has joined #zope | 13:43 | |
| *** alexpilz has quit IRC | 13:43 | |
| *** alexpilz has joined #zope | 13:44 | |
| thevishy | Thanks I need to ponder | 13:45 |
| kosh | what version of zope are you using? what kind of object are you posting to? | 13:49 |
| thevishy | Zope 2 | 13:50 |
| thevishy | I am current posting the object to /tinymce/spell_checker | 13:50 |
| kosh | what kind of object is spell_checker? | 13:51 |
| thevishy | there is a file called inymce.py | 13:53 |
| thevishy | tinymce.py and spellchecker is an object there | 13:53 |
| thevishy | def spell_checker | 13:53 |
| kosh | ah | 13:53 |
| thevishy | so the problem is that the JSON object doesn't reach here | 13:53 |
| kosh | so it is just a method then | 13:53 |
| thevishy | Yeah | 13:53 |
| thevishy | basically we are adding a tiny_mce functionality locally | 13:54 |
| kosh | was this a product originally built to use zope? | 13:54 |
| thevishy | Tiny_MCE , no it is a 3rd party product written in JS | 13:54 |
| thevishy | it does most of its stuff at client side | 13:55 |
| thevishy | but we need to implement the spell check locally | 13:55 |
| kosh | well in your spell_checker method look at the value of self.REQUEST.form.items() | 13:55 |
| kosh | your json data should be in there | 13:55 |
| thevishy | thats what we did all the time let me check it up now again | 13:56 |
| kosh | did whoever that wrote your python code write it to work with zope? | 13:56 |
| thevishy | We are trying to integrate with Python | 13:57 |
| thevishy | Few functions of TinyMCE needs to be done at server side | 13:57 |
| thevishy | its basically a js based thing | 13:57 |
| thevishy | There was a ZTinyMCE egg but its old and depreciated | 13:58 |
| *** menesis has joined #zope | 13:58 | |
| thevishy | (Pdb) self.REQUEST.form.items() | 13:58 |
| thevishy | [] | 13:58 |
| thevishy | IN firebug I can see it posts the full data | 13:59 |
| thevishy | Do you get me ? | 13:59 |
| kosh | what var does it POST it under though? | 13:59 |
| thevishy | JSON format | 13:59 |
| thevishy | id method params format | 14:00 |
| thevishy | like 100 params | 14:00 |
| kosh | JSON is just a string | 14:01 |
| thevishy | Oh... | 14:01 |
| kosh | POST should be key:value pairs where you would have somename and then the value would be the JSONDATA | 14:01 |
| thevishy | So how do I figure out the variable? | 14:01 |
| thevishy | Wait | 14:01 |
| kosh | I have no idea about that for firebug | 14:01 |
| kosh | it is not something I Have played with | 14:02 |
| thevishy | CConteleght=946 | 14:02 |
| kosh | I have always used wireshark so that I know exactly what is being sent from the browser to the server | 14:02 |
| thevishy | Contenlength=946. | 14:02 |
| thevishy | Right let me install that , would be a great tool | 14:02 |
| thevishy | is it available default in Linux OS'es ? | 14:02 |
| thevishy | any idea there | 14:03 |
| kosh | sudo apt-get install wireshark should normally do it for debian based os at least | 14:03 |
| kosh | the problem is that if you have never used it before it is not easy to use | 14:03 |
| thevishy | right | 14:03 |
| thevishy | will try it out now | 14:03 |
| wosc | thevishy: open firebug. Do your post. Go to "net" tab in Firebug | 14:06 |
| wosc | there you should see "POST /tinymce/spell_checker" with a [+] beside | 14:07 |
| wosc | click that; you should see new tabs appear below; one of them is labeled "post" | 14:07 |
| thevishy | I see post tab | 14:07 |
| wosc | that lists all the parameters it POSTed to the server | 14:07 |
| *** menesis has quit IRC | 14:08 | |
| wosc | kosh can take it from there ;) | 14:08 |
| thevishy | In POST tab | 14:09 |
| thevishy | I see JSON | 14:09 |
| thevishy | and the format JSON uses like id , method and params | 14:09 |
| kosh | what is in the JSON format does not matter | 14:09 |
| kosh | it is just a string | 14:09 |
| wosc | no, what we need to know is what the name of the HTTP variable is that *contains* all that JSON | 14:10 |
| wosc | it should be written in bold to the left of that "post" tab | 14:10 |
| kosh | I wonder if the idiots just sent the data directly to the server with no var names at all | 14:10 |
| kosh | I saw someone do that once with files, no delimeters or anything | 14:10 |
| kosh | I wanted to take them out back and feed them through a woodchipper | 14:10 |
| thevishy | lol | 14:10 |
| wosc | kosh: not idiots. those REST-ful approaches call for exactly that IIRC | 14:11 |
| kosh | still idiots | 14:11 |
| kosh | because it makes it very hard to work with the data | 14:11 |
| thevishy | its like this | 14:11 |
| thevishy | http://ideone.com/M4TF2 | 14:11 |
| wosc | that's still just the JSON | 14:11 |
| wosc | we still don't know whether that is the *whole* POST body | 14:11 |
| wosc | in my firebug there's a section called "Source" | 14:12 |
| kosh | wosc: the whole POST body being json, csv or just some binary file is hard to work with and upload to in a lot of systems | 14:12 |
| kosh | REQUEST.form is pretty much the standard for getting data from a form from java apps to .net to just about everything else, if you just shove something in with no name at all working with it is a bitch | 14:13 |
| kosh | or generating it for that matter | 14:13 |
| wosc | kosh: I'm not so sure about that | 14:13 |
| wosc | I don't have all the request APIs memorized, but it should be possible to get the raw body | 14:13 |
| thevishy | let me check | 14:13 |
| wosc | without any parsing | 14:13 |
| kosh | wosc: that seems like a massively bad idea | 14:14 |
| wosc | kosh: I happen to disagree ;) | 14:14 |
| wosc | but it doesn't really concern me all that much right now | 14:15 |
| kosh | putting it under a name makes it trivial to work with in pretty much every tool developed | 14:15 |
| kosh | wosc: why do you disagree that direct access to the raw data is a bad idea? that looks like it would be a massive security problem to me | 14:15 |
| wosc | sorry, that doesn't seem like a very coherent argument to me | 14:16 |
| kosh | raw data means it has not been parsed yet | 14:16 |
| kosh | so you have to do all the careful checking instead of the app server | 14:16 |
| wosc | what's there to parse, if everything there is is a JSON document (as in our example) | 14:16 |
| kosh | what if it isn't though | 14:17 |
| kosh | what if someone POSTs something else to that url | 14:17 |
| kosh | you can't assume that all data sent to a url will be data that originated from the correct source | 14:17 |
| kosh | so if you start putting in stuff like CSRF protection then you are back to needing the data sent normally | 14:17 |
| wosc | putting a "myparam=bad stuff" in front of it doesn't change anything in that situation, or does it? | 14:18 |
| kosh | by doing POSTs using normal methods then all normal tools work so that you can easily do things like sanitize the data, block certain requests | 14:19 |
| thevishy | we will check a few things here and get back | 14:19 |
| thevishy | thanks for your inputs | 14:20 |
| kosh | using some other format for the POST is just not a good idea | 14:20 |
| kosh | there is no reason that JSON data should not be POST as a key:value pair to the server | 14:20 |
| kosh | the jQuery stuff I have worked with has all done exactly that, none of them went some weird route of sending that data as the only payload | 14:21 |
| thevishy | I will check ont this point | 14:21 |
| kosh | thevishy: I looked at the tinymce docks and they are pretty limited but I did not see how to setup spellchecking for it | 14:21 |
| kosh | I did not even see spellchecking listed in the docs | 14:21 |
| thevishy | spell checking is a plugin feature | 14:22 |
| thevishy | what we are planning to do is to use the plugin template and then do the processing at server end | 14:22 |
| thevishy | we plan to use a Python based spell checker locally and reply using JSON thats the main idea | 14:22 |
| kosh | I don't see docs for that | 14:22 |
| *** menesis has joined #zope | 14:24 | |
| thevishy | http://stackoverflow.com/questions/1920162/tinymce-spellchecker-in-pylons | 14:25 |
| thevishy | seems to have a similar issue | 14:25 |
| thevishy | I will be back in few mins | 14:25 |
| thevishy | documentation seems poor as per him too | 14:26 |
| kosh | thevishy: try look at self.REQUEST.get('BODY') or self.REQUEST.get('BODYFILE') and see if your data is in there | 14:26 |
| kosh | if it is find the people that wrote that and take them out back and shoot them | 14:26 |
| wosc | thevishy: the stackoverflow confirms it | 14:27 |
| wosc | tinymce does not use a POST variable | 14:27 |
| wosc | but the whole POST body is the JSON | 14:27 |
| * wosc doesn't know enough about the Zope2 request | 14:27 | |
| kosh | god I hate apps that do that kind of crap | 14:28 |
| kosh | that question should not even exist | 14:28 |
| kosh | is this was done the standard way then there would have been no issues at all | 14:28 |
| wosc | kosh: I don't think you know enough about what the standard actually is here | 14:28 |
| kosh | wosc: if you post it as a key:value pair then it would have come up correctly in any of the standard tools | 14:29 |
| wosc | reminds me of "if all lemmings jump off a cliff"... | 14:29 |
| kosh | wosc: the question on stackoverflow even says that he looks in his request object and did not find it | 14:29 |
| kosh | wosc: there is a reason for standards, when you follow the standards systems work together better | 14:29 |
| kosh | wosc: a huge ammount of time is wasted for NO gain by doing it this other way | 14:29 |
| wosc | kosh: the standard we're talking about is HTTP | 14:30 |
| wosc | but I think that's all I'm gonna say about it | 14:30 |
| kosh | can you tell me any actual advantage of posting the data as the body of the request instead of a key:value pair like normally done? | 14:30 |
| kosh | I know what the HTTP standard is, I know it allows this, that does not make it a normal approach by a long shot | 14:30 |
| wosc | thevishy: as kosh said, try self.REQUEST.get('BODY') or self.REQUEST.get('BODYFILE') | 14:31 |
| kosh | by going this other approach it makes it harder to test, harder for many common tools to work, harder for normal people to figure out what is going on | 14:31 |
| kosh | there is no realistic gain by posting raw json as the entire body and not going key value and a huge ammount of loss | 14:32 |
| kosh | it is not going to transmit any faster, it won't run any faster | 14:32 |
| *** Ariel_Calzada has quit IRC | 14:37 | |
| *** ccomb has joined #zope | 14:39 | |
| teix | kosh wosc http://tinymce.moxiecode.com/wiki.php/Plugin:spellchecker they call it as "rpc service document" | 14:40 |
| teix | [spellchecker_rpc_url] URL to back end for example the PHP rpc service document or some custom spellchecker service. | 14:40 |
| *** Ariel_Calzada has joined #zope | 14:41 | |
| teix | whatever that means :P | 14:41 |
| wosc | thevishy: did you look self.REQUEST.get('BODY') or self.REQUEST.get('BODYFILE') yet? | 14:41 |
| *** srichter has joined #zope | 14:45 | |
| kosh | for some reason the javascript web people decided that JSON should be done differently then other stuff the whole JSONRequest objects which exist now do POST and GET differently from how it has normally been done | 14:47 |
| kosh | so a lot of normal tools also screw those things up | 14:47 |
| kosh | sometimes I wish I could force the people that write that crap to maintain it long term | 14:47 |
| kosh | and not just jump from project to project and never have to deal with the long term consequences of what they do | 14:48 |
| *** eperez has quit IRC | 14:48 | |
| *** Ariel_Calzada has quit IRC | 15:04 | |
| *** tisto|lunch is now known as tisto | 15:08 | |
| *** yvl has quit IRC | 15:11 | |
| thevishy | kosh: JSON seems to be available at self.REQUEST['BODY'] | 15:17 |
| thevishy | we tried many places but missed out this param called BODY , it has data in JSON format nearly ! | 15:18 |
| *** avoinea has quit IRC | 15:29 | |
| *** dayne has joined #zope | 15:37 | |
| *** ccomb has quit IRC | 15:59 | |
| *** digitalmortician has quit IRC | 16:02 | |
| *** digitalmortician has joined #zope | 16:03 | |
| *** TomBlockley_ has joined #zope | 16:04 | |
| *** TomBlockley has quit IRC | 16:05 | |
| *** TomBlockley_ is now known as TomBlockley | 16:05 | |
| *** dayne has quit IRC | 16:08 | |
| *** sp0cksbeard has joined #zope | 16:14 | |
| *** ccomb has joined #zope | 16:15 | |
| CIA-89 | lentinj * r121684 plone.z3cform/plone/z3cform/traversal.py: Don't assume widget has prefix we are expecting | 16:22 |
| CIA-89 | hannosch * r121685 Products.ZCatalog/src/Products/PluginIndexes/common/UnIndex.py: Remove outdated comment and avoid creating Length() which is done again in the clear method | 16:22 |
| CIA-89 | hannosch * r121686 Products.ZCatalog/ (3 files in 2 dirs): | 16:22 |
| CIA-89 | Extend BooleanIndex by making the indexed value variable instead of hardcoding | 16:22 |
| CIA-89 | it to `True`. The indexed value will determine the smaller set automatically and | 16:22 |
| CIA-89 | choose its best value. An inline switch is done once the indexed value set grows | 16:22 |
| CIA-89 | larger than 60% of the total length. 60% was chosen to avoid constant switching | 16:22 |
| CIA-89 | for indexes that have an almost equal distribution of `True/False`. | 16:22 |
| *** __mac__ has quit IRC | 16:42 | |
| *** thevishy has quit IRC | 16:42 | |
| *** wosc has quit IRC | 16:42 | |
| *** thevishy has joined #zope | 16:43 | |
| *** TomBlockley has quit IRC | 16:50 | |
| *** TomBlockley has joined #zope | 16:50 | |
| *** eperez has joined #zope | 17:08 | |
| *** TomBlockley_ has joined #zope | 17:08 | |
| *** TomBlockley has quit IRC | 17:10 | |
| *** TomBlockley has joined #zope | 17:15 | |
| *** alga has quit IRC | 17:15 | |
| *** pjfd4 has joined #zope | 17:17 | |
| *** pjfd2 has quit IRC | 17:20 | |
| *** cwarner_ has joined #zope | 17:43 | |
| *** thevishy has left #zope | 17:45 | |
| *** fredvd has joined #zope | 17:49 | |
| *** Arfrever has joined #zope | 17:53 | |
| *** J1m has joined #zope | 18:02 | |
| *** sm has joined #zope | 18:04 | |
| CIA-89 | satchit achapman-exc-info * r121687 zope.server/src/zope/server/http/ (wsgihttpserver.py tests/test_wsgiserver.py): | 18:06 |
| CIA-89 | further compliance with WSGI PEP. | 18:06 |
| CIA-89 | and tests. | 18:06 |
| CIA-89 | satchit achapman-exc-info * r121688 zope.server/src/zope/server/http/tests/test_wsgiserver.py: fix typo. | 18:06 |
| CIA-89 | tseaver * r121689 zope.interface/CHANGES.txt: Garden changelog. | 18:06 |
| CIA-89 | tseaver * r121690 zope.interface/ (CHANGES.txt setup.py README.txt): | 18:06 |
| CIA-89 | Detailed documentation moved out-of-line from PyPI page | 18:06 |
| CIA-89 | - Now links to http://docs.zope.org/zope.interface | 18:06 |
| CIA-89 | - Garden ReST of README.txt, CHANGES.txt | 18:06 |
| CIA-89 | tseaver * r121691 zope.interface/README.txt: ReST fix. | 18:06 |
| CIA-89 | tseaver * r121692 zope.interface/CHANGES.txt: Better phrasing. | 18:06 |
| CIA-89 | tseaver * r121693 /zope.interface/tags/3.6.2: Tag 3.6.2 release. | 18:06 |
| CIA-89 | tseaver * r121694 /zope.interface/tags/3.6.2: Missed version bump | 18:06 |
| CIA-89 | tseaver * r121695 zope.interface/setup.py: Prep 3.6.2 release. | 18:06 |
| *** sm has quit IRC | 18:17 | |
| *** alvaro_o has joined #zope | 18:19 | |
| *** alvaro_o has quit IRC | 18:20 | |
| *** fredvd has quit IRC | 18:24 | |
| *** __mac__ has joined #zope | 18:34 | |
| *** agroszer has quit IRC | 18:42 | |
| *** tisto has quit IRC | 19:05 | |
| *** pjfd4 has quit IRC | 19:12 | |
| *** alexpilz has quit IRC | 19:28 | |
| *** Spanktar has joined #zope | 19:31 | |
| *** sylvain has quit IRC | 19:54 | |
| *** davisagli has quit IRC | 19:54 | |
| *** davisagli has joined #zope | 19:54 | |
| *** alexpilz has joined #zope | 20:22 | |
| *** TomBlockley has quit IRC | 20:27 | |
| *** srichter has quit IRC | 20:30 | |
| *** evilbungle has quit IRC | 20:34 | |
| *** giampaolo has joined #zope | 20:38 | |
| *** zagy has joined #zope | 20:42 | |
| *** sm has joined #zope | 20:48 | |
| *** TresEquis has joined #zope | 20:54 | |
| *** kleist has quit IRC | 20:56 | |
| *** ccomb1 has joined #zope | 21:06 | |
| *** TresEquis has quit IRC | 21:06 | |
| *** ccomb has quit IRC | 21:07 | |
| *** TresEquis has joined #zope | 21:10 | |
| *** hever has quit IRC | 21:12 | |
| *** digitalmortici-1 has joined #zope | 21:21 | |
| *** digitalmortician has quit IRC | 21:21 | |
| *** menesis has quit IRC | 21:31 | |
| *** tiwula has joined #zope | 21:31 | |
| *** teix has quit IRC | 21:35 | |
| *** allisterb has quit IRC | 21:50 | |
| *** __mac__ has quit IRC | 21:52 | |
| *** __mac__ has joined #zope | 21:53 | |
| *** teix has joined #zope | 21:55 | |
| *** srichter has joined #zope | 22:08 | |
| *** TomBlockley has joined #zope | 22:13 | |
| *** m8 has joined #zope | 22:14 | |
| *** teix has left #zope | 22:14 | |
| *** TomBlockley has quit IRC | 22:15 | |
| *** giampaolo has quit IRC | 22:17 | |
| *** TomBlockley has joined #zope | 22:21 | |
| *** cwarner_ has quit IRC | 22:23 | |
| *** benji has quit IRC | 22:33 | |
| *** ccomb has joined #zope | 22:35 | |
| *** ccomb1 has quit IRC | 22:37 | |
| *** RichardBarrell has joined #zope | 22:43 | |
| *** John[a] has joined #zope | 23:03 | |
| *** tiwula has quit IRC | 23:10 | |
| *** __mac__ has quit IRC | 23:14 | |
| CIA-89 | ldr * r121698 plone.z3cform/docs/HISTORY.txt: Prepare plone.z3cform 0.7.6. | 23:17 |
| CIA-89 | ldr * r121699 /plone.z3cform/tags/0.7.6: Tagged plone.z3cform 0.7.6. | 23:17 |
| CIA-89 | ldr * r121700 plone.z3cform/ (docs/HISTORY.txt setup.py): bump version | 23:17 |
| CIA-89 | satchit achapman-exc-info * r121701 zope.server/src/zope/server/http/wsgihttpserver.py: whitespace fix. | 23:17 |
| CIA-89 | satchit achapman-exc-info * r121702 zope.server/src/zope/server/http/wsgihttpserver.py: comment to explain what happens next. | 23:17 |
| *** alga has joined #zope | 23:19 | |
| *** ccomb has quit IRC | 23:22 | |
| *** zagy has quit IRC | 23:23 | |
| *** m8 has quit IRC | 23:50 | |
| *** TomBlockley has joined #zope | 23:55 | |
| *** evilbungle has joined #zope | 23:59 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!