gt; +1 to Zope3 (and note that I have alreay moved there myself). That
> style is already documented; we should not need to expend any
> significant effort maintaining it.
I would second Tres' reasoning, and the Zope3 styleguide is already
second nature to me.
- --
Martijn Pieters
ile "z3.py", line 59, in run
from zope.app.twisted.main import main
ImportError: No module named twisted.main
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
I assumed that a SVN
trunk checkout was no longer the way one is supposed to work on
Zope3..
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
ided against KSS, for various reasons. Some of these
reasons lie in a difference of opinion on how an AJAX architecture
should work.
This is Paul Carduners GSOC project, BTW.
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http
rs that the switch to eggs requires additional
precautions to avoid your python system to be 'polluted' with various
Zope3 packages. Perhaps we should recommend using workingenv for
development work instead?
--
Martijn Pieters
___
Zope3-dev m
iven a
fair chance also. Services should be able to be turned on and off using
application logic - and the app itself should be able to tell you
something about its services and their state.
For which you'd need to expose the root multiservice to start with, of course.
--
Mart
, stop that service,
add this one or drop that other one. This is better in my view - it
would also provide simple infrastructure for integration for applications.
Right, access to the multiservice would give you that, it is an iterator.
--
Mart
directly. Subscribe to the Zope ProcessStarting event to start
your services at Zope startup time, and use the twisted reactor
system event triggers to hook into the shutdown. You could even create
your own multiservice object to manage your own services in one go.
--
Martijn Pieters
__
sta/browser/z3wingdbg/trunk/
It starts additional services, such as a single-threaded HTTP debug
server on a separate port, either at Zope start or later as the user
requests.
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://ma
0]
return storedPassword == self.encodePassword(password, salt)
That'll capture any salt length as the sha.hexdigest output is always
40 characters long.
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/
one. ;)
I found this one also useful:
http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html
That's the correct link! Corrected on the Wiki. :) Thanks!
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope
ellent GSoC
mentoring How-To:
http://plone.org/products/plone/releases/SoC-2007
I added it to the Wiki page. It should be mandatory reading for any
potential mentor!
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.
unt to avoid deleting current files, at least on any UNIX
system I have encountered.
I don't think clueless sysadmins need protecting.. ;)
--
Martijn Pieters
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/option
On 3/5/07, Martijn Pieters <[EMAIL PROTECTED]> wrote:
On 3/5/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
> Great. I've added you to http://wiki.zope.org/zope3/SummerOfCode2007. If
> you happen to have any project suggestions, feel free to add them to the
>
On 3/5/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Great. I've added you to http://wiki.zope.org/zope3/SummerOfCode2007. If
you happen to have any project suggestions, feel free to add them to the
list.
I've added myself to the mentors list as well.
--
ns one at a time (10 pages * 20 spam updates * 2 form
submits per version) wasn't fun either.
Trac's plugin support (components) covers this area well, and will
improve even more in version 0.10.
--
Martijn Pieters
___
Zope3-dev mailing
Gary Poster wrote:
> We think this will allow for a much nicer rich sub-view (i.e., rich
> widget, among others) story. We're eager to get some feedback,
> including ideas for improvements.
+1; I'd rely on this. But the next 5 weeks I have no bandwidth to give
the proposal much attention due to e
ds down (end of this week) I'd love to
set up a few buildbot instances here at Pareto, as we have a few spare
cycles. I can offer:
- Platform: Debian sarge (latest stable)
- Python versions: 2.3 and 2.4
- Zope3 versions: all that need taking.
any of the characters (without the
quotes) in "!#$%&'*+-.^_`|~".
(I misnamed the applicable lines in your bug report, sorry).
As stated in collector item 450, I think Zope3 should log such cookie
errors in the log and otherwise pretend the cookie was never sent.
Martijn Pieters
o references to these string exceptions anywhere in the
Zope3 codebase, nor was the exception described in any interface. So I
felt confident that any breakage I caused was self-inflicted by whomever
was using this undocumented feature. ;)
Martijn Pieters
signature.asc
Description: OpenPGP di
.
All not in favour, please keep mum unless a good reason not to be flogged
for blasphemy is brought henceforth immediatly.
Your loyal priest of the styleguides,
Martijn Pieters
[1] http://mail.python.org/pipermail/python-dev/2005-August/055190.html
[2] http://www.python.org/peps/pep-0008.
Stephan Richter wrote:
I'd like to update the horribly outdated version of docutils in the
Zope3 tree (version 0.3.0) to the latest resease (version 0.3.9).
+1
Okay; it is in (revision #33317). I included the latest version of Mark
Pilgrim's roman.py for good measure (the fast version that p
I'd like to update the horribly outdated version of docutils in the
Zope3 tree (version 0.3.0) to the latest resease (version 0.3.9).
In fact, I have already done so locally including fixing all the
relevant tests and refactoring the zope.app.render.rest module
(simplification and removal of f
I applied a much overdue update to the Zope3 check-in guidelines in the
Z3 wiki at:
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/CheckinGuidelines
Could someone with more actual check-in fu look this over and check my
assumptions?
Martijn Pieters
signature.asc
24 matches
Mail list logo
