These should be very quickly fixed, it is good that you noted them. Everything done during this week end will be a step forward.<br><br><br><div class="gmail_quote">2009/6/25 Reinout van Rees <span dir="ltr"><<a href="mailto:reinout@vanrees.org">reinout@vanrees.org</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I looked through the `Grok buglist <<a href="https://bugs.launchpad.net/grok" target="_blank">https://bugs.launchpad.net/grok</a>>`_ with<br>
`Jan-Wijbrand <<a href="http://jw.n--tree.net/blog/" target="_blank">http://jw.n--tree.net/blog/</a>>`_ today. Goal:<br>
<br>
- Get a short list of bugs as focus for the `Europython Grok sprint<br>
<<a href="http://reinout.vanrees.org/weblog/2009/06/09/grok-europython-sprint.html" target="_blank">http://reinout.vanrees.org/weblog/2009/06/09/grok-europython-sprint.html</a>>`_.<br>
<br>
- Find the bugs that really move 1.0 forwards.<br>
<br>
- Find bugs that are probably doable in two days.<br>
<br>
I've `tagged all five bugs we selected<br>
<<a href="https://bugs.launchpad.net/grok/+bugs?field.tag=europython2009" target="_blank">https://bugs.launchpad.net/grok/+bugs?field.tag=europython2009</a>>`_ with<br>
"europython2009" so that they're easy to find:<br>
<br>
- Splitting grok.CodeView (*with just a render() method, so something that<br>
programmatically returns output*) out of grok.View (*which only retains its<br>
@template and loses the render() method*) ought to simplify the code a lot<br>
and open up the way for the last couple of fixes that are needed in this<br>
area for 1.0.<br>
<br>
- grok.require() effectively falls back to the zope.Public permission.<br>
zope.Public isn't something you can take away. If we set the default to<br>
zope.View, we can easily close everything to anonymous visitors.<br>
<br>
- Having one ``templates/`` directory for a couple of modules is handy, but<br>
buries you under unnecessary warnings at the moment.<br>
<br>
- XMLRPC in combination with WSGI is broken. Can we (help) fix/debug it?<br>
<br>
- For WSGI when using development mode, something's fishy with logging in.<br>
`Loads of comments on the bug<br>
<<a href="https://bugs.launchpad.net/grok/+bug/332061" target="_blank">https://bugs.launchpad.net/grok/+bug/332061</a>>`_, so with that we ought to<br>
nail it during the sprint.<br>
<br>
For all your grok sprint info, see my previous `Grok sprint at Europython 2009<br>
<<a href="http://reinout.vanrees.org/weblog/2009/06/09/grok-europython-sprint.html" target="_blank">http://reinout.vanrees.org/weblog/2009/06/09/grok-europython-sprint.html</a>>`_<br>
blog entry (which I updated with the sprint location).<br>
<br>
<br>
Reinout<br>
<br>
<br>
--<br>
Reinout van Rees - <a href="mailto:reinout@vanrees.org">reinout@vanrees.org</a> - <a href="http://reinout.vanrees.org" target="_blank">http://reinout.vanrees.org</a><br>
Software developer at <a href="http://www.thehealthagency.com" target="_blank">http://www.thehealthagency.com</a><br>
"Military engineers build missiles. Civil engineers build targets"<br>
<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</blockquote></div><br>