Martin Aspeli wrote:
The grok approach is unfamiliar at first, for sure, and could do with
more documentation. But then so could the writing of ZCML directives.
Grok (and martian) do have some really nice abstractions, including good
testing support.
I have not found documentation for
Martin Aspeli wrote:
Well... in any case, this discussion is somewhat moot since only
framework authors should ever need to write directives or grokkers.
In that case, you're disagreeing with my position. Let me state it
differently: if only framework authors write ZCML handlers / grokkers,
Chris McDonough wrote:
I think it would be more approachable (and therefore better on some axis)
if
a) ZCML didn't use schemas (declarative is not a win here, as you still need
to
write imperative code in the handler, and if you *did* want declarative
stuff,
just let the handler call
Chris McDonough wrote:
On 5/7/09 3:44 PM, Shane Hathaway wrote:
Chris McDonough wrote:
c) handlers actually just *returned* something rather than being
called for their side effects.
The thing the handler returns could implement the IConfigurationAction
interface described here:
http
Reed O'Brien wrote:
On May 12, 2009, at 12:17 PM, Chris McDonough wrote:
If we can't afford this (and I sure can't personally), I'm not sure
what we'd
end up calling it. plone.dot.someting? zope.dot.something?
ymmv.zope2
LOL! It would be a commitment to never commit to anything. :-)
Paul Johnston wrote:
By default, passwords are stored in the database without a salt. Usual
practice is to use a salt, to make things harder for an attacker, just
in case your password database is captured. The scheme I favor is
storing hmac_sha1(hmac_sha1(master_salt, user_name), password).
Jens W. Klein wrote:
Am Wed, 24 Jun 2009 09:59:14 -0400 schrieb Tres Seaver:
[..]
Missing is a version fixation like done in ZTK, Grok, Plone, ... I'd
really like to see such a version.cfg for each repoze release. Creation
could be automated.
You shouldn't need to pin the versions if you would
z...@kevinkal.com wrote:
I've become a big fan of pip. The --freeze option is great. It seems
that it lets you pin your versions all the way down. I'm just watching
all of the pain with certain buildout recipes where I could imagine them
easier to create if the person creating the
Thomas G. Willis wrote:
will there be a realtime feed of what's happening for those of us who
are interested, yet too lame to attend?
This is our current project:
http://bitbucket.org/sawdog/bfgcookbook/
We are working on a simple sample app for BFG to be used in documentation.
Shane
Shane Hathaway sh...@hathawaymix.org added the comment:
I ran into the same issue. The following code worked with 1.1.1 but fails with
1.1.2:
from chameleon.zpt.template import PageTemplate
master = PageTemplate('''\
!DOCTYPE html
html metal:define-macro=main
body
div metal:define-slot=content
Malthe Borch wrote:
On 4 March 2010 22:02, Kevin Kalupson b...@bugs.repoze.org wrote:
I wouldn't expect the the xml headers in a macro template to be applied to
the
page template being rendered. It makes no sense to me that an element not
contained within a macro definition would be applied
Kevin J. Kalupson wrote:
On 3/4/10 2:22 PM, Shane Hathaway wrote:
The current syntax is
non-obvious and perhaps problematic, but workable. Some other syntax
might be better, but let's not break the current syntax in the 1.1 branch.
I don't think it's a syntax issue, I think it's
Kevin J. Kalupson wrote:
I just tested in zope2 through the zmi.
I seem to recall that this syntax works in Plone. I don't care whether
it works in plain Zope 2.
Is this really important to you? While it's a special case, I think
it's a case of practicality beats purity. I use it a lot.
Kevin Kalupson wrote:
The importance to me is that there isn't a regression to the duplicate
xml headers when templates render. I like to validate my templates as I
go and not have to hack them to then test my rendered template.
Good point. If you're statically validating all templates, then
On 04/10/2010 07:00 AM, Andreas Jung wrote:
is it save to use the 'multiprocessing' module inside a BFG app?
In particular I need to maintain a multiprocessing.Pool() instance...
this is working at the first glance however the BFG app won't shutdown
in a clean way when stopped through a
On 04/16/2010 10:12 AM, Tres Seaver wrote:
Maybe we should just renew the request to push PILwoTk to PyPI[1] and
update our dependencies.
[1] https://mail.zope.org/pipermail/zope-dev/2007-October/029968.html
+1, I only use PILwoTk and I'd rather get it from PyPI.
Shane
On 04/25/2010 04:40 PM, Chris McDonough wrote:
There's a relationship between the authentication policy and authorization
policy (authorization depends on authentication) that makes writing a good
docstring for this API a bit tortured. For example:
def set_security_policies(self,
On 04/28/2010 01:07 PM, Chris Withers wrote:
In the BFG book their are copious references to the fact that using
imperative configuration (or the decorators, my preferred choice) is
bad if you plan to write apps that might be extended by others.
Am I right in understanding that this is
On 05/06/2010 08:49 AM, Chris McDonough wrote:
I'm also not sure that this can be advertised as an overrides strategy
100% comparable to ZCML unless all the various ZCML directives get
Python declarative equivalents.
So.. yeah, I think there's a cool idea lurking in here, but I'm not sure
we
On 05/13/2010 10:23 AM, Douglas Cerna wrote:
This way used to work when I used ZPT in Grok 1.0. Is it possible to
include the!DOCTYPE ... in a macro using chameleon?
AFAIK, Chameleon now lets you use the whole template as a macro. OTOH,
I've been using the HTML 5 doctype and I've seen no
On 06/25/2010 01:16 PM, Chris McDonough wrote:
We've addressed this in repoze.who by giving r.who's middleware a mode
which injects only a factory into the environ instead of more eagerly
constructing identity information. We can't really do that for
repoze.zodbconn#connector, or at least it
On 11/05/2010 02:11 PM, Casey Duncan wrote:
Congrats! Great to see synergy, particularly amongst Python web frameworks!
+1 :-)
Shane
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
On 11/12/2010 03:17 PM, Iain Duncan wrote:
Reading some of the diaolgue on the pylons/bfg merger has me curious
about the following, wondering if any experts care to share opinions and
war stories:
- what is the best use case for extending through entry points?
- why/when would you use entry
On 11/15/2010 02:48 PM, Martin Aspeli wrote:
On 15 November 2010 21:21, Michael Mulichmr...@psu.edu wrote:
Part of my decision to use entry points was from my experience at pycon.
People hear reference to zope and either cringe or run away. So if
people see zope.* as a dependency they decide
On 11/15/2010 06:29 PM, Uwe Hentzschel wrote:
select multiple id=select1
Your multiple attribute needs a value. One possibility:
select multiple=multiple id=select1
Shane
___
Repoze-dev mailing list
On 03/01/2011 06:48 AM, Malthe Borch wrote:
On 1 March 2011 14:19, Chris Withersch...@simplistix.co.uk wrote:
So, it's quoting the tags but not the entities. Bug, no?
Yes, it certainly seems so.
I hope this isn't a XSS hole. I can't think of a way to add a script
tag to a page using this
On 03/01/2011 07:28 PM, Shane Hathaway wrote:
On 03/01/2011 06:48 AM, Malthe Borch wrote:
On 1 March 2011 14:19, Chris Withersch...@simplistix.co.uk wrote:
So, it's quoting the tags but not the entities. Bug, no?
Yes, it certainly seems so.
I hope this isn't a XSS hole. I can't think
On 03/02/2011 01:12 AM, Malthe Borch wrote:
This could be changed, but it's true that in 2.x (and I realize now
that I haven't written that down anywhere), the pipe character is not
in play with Python-expressions. However, it is implemented and
working for path: in ``z3c.pt``, e.g.:
path:
28 matches
Mail list logo
