In 2008, the `zope_i18n_allowed_languages` environment setting was
introduced to limit the languages for which a message catalog is
loaded when you register translations using the registerTranslation
ZCML directive, and to be able to negotiate a list from a list of
available languages.
This
I just committed a bugfix against zc.queue which makes it possible to
slice a composite queue:
https://mail.zope.org/pipermail/checkins/2012-June/061348.html
It previously wasn't possible due to a simple programming mistake. Can
we have a release 1.3.1?
\malthe
I had many of these in the instance log; googling around, I found this:
https://mail.zope.org/pipermail/zope/2002-September/122392.html
But it seems the patch attached to a post in that thread never made it
to the repo. It's now almost ten years later, so this sort of incident
must be pretty
On 25 October 2011 17:53, Malthe Borch mbo...@gmail.com wrote:
I'll try and see if I can understand what might be the right thing to
expect and write a test case for that.
Following up here on the list to get some feedback on the patch I
submitted concerning this issue:
https
On 7 November 2011 09:17, Ross Patterson m...@rpatterson.net wrote:
The intention of this package is to see if the implementation of broken
object handling is correct and robust enough to merge into
zope.interface and zope.component themselves. Is this the right
approach? If not why and what
If I set my beforestorage to a reasonably current time, e.g. now, I
expect to get reasonably good performance from a ZEO client cache.
Instead, I find that beforestorage:
1) asks the cache to ``loadBefore``;
2) but that method only looks for noncurrent entries;
3) meanwhile, my cache only
I will merge this branch if there are no objections.
\malthe
On 20 July 2011 17:24, Malthe Borch mbo...@gmail.com wrote:
I've refactored the ``pagetemplate`` module to realistically support
plugging in an alternative implementation of the parser and
interpreter.
http://svn.zope.org
On 21 July 2011 16:19, Leonardo Rochael Almeida leoroch...@gmail.com wrote:
How often is the adaptation called?
Once per template render. No penalty for macros.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
I've refactored the ``pagetemplate`` module to realistically support
plugging in an alternative implementation of the parser and
interpreter.
http://svn.zope.org/zope.pagetemplate/branches/engine-as-component/
Two new interfaces are added which serve as the plugging point see
It makes it possible to use Chameleon with the stock template classes
without monkey-patching the ``TALInterpreter`` class and ``_cook``.
\malthe
On 20 July 2011 17:43, Jim Fulton j...@zope.com wrote:
What problem does this solve?
Jim
On Wed, Jul 20, 2011 at 11:24 AM, Malthe Borch mbo
On 3 December 2010 11:41, Chris Withers ch...@simplistix.co.uk wrote:
I'd much prefer it to just be an order of execution thing, the nyou have
total and flexible control. Combined with some logging about why something
is as it is and you have your solution.
It's not always possible to control
I always found configuration overrides (e.g. ZCML's includeOverrides
directive) to be difficult to manage and hard to get right.
How about an alternative where you can put a priority on a
configuration context like so:
adapter zcml:priority=100 ... /
Default priority would be 0, traditional
On 2 December 2010 13:34, Benji York be...@benjiyork.com wrote:
I appreciate the flexibility inherent in that approach, but personally,
I'd be frightened of such a system. I sometimes have problems figuring
out which directives are active in the current system, if I had to
reason about dozens
On 2 December 2010 14:37, Stephan Richter srich...@cosmos.phy.tufts.edu wrote:
This explanation helped me to understand where you come from. I think I would
be okay with the priority feature, but could we maybe limit it to the
configure element? Since you can use this element anywhere and it
Fabio Tranchitella wrote:
# TODO: Shouldn't meta/?xml? stripping
# be in PageTemplate.__call__()?
body = utils.re_meta.sub(, body)
This snippet was removed from ``chameleon.core`` in r6505.
\malthe
___
Zope-Dev maillist -
Fabio Tranchitella wrote:
I hope this is the right mailing list for such a question. Why does
chameleon.core removes the meta tag http-equiv=content-type from the
output?
I have no idea why; I've asked Sidnei to clarify that particular
changeset in Chameleon (although I suspect it was just
Martin Aspeli wrote:
Is there any documentation on zope.proxy other than the test? I don't
speak C anymore. :)
I find ``zope.location.location.LocationProxy`` to be a good example of
its usage.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
Laurence Rowe wrote:
I would rather we did not hardcode the defaults from SQLAlchemy into the
engine directive (I guess they could change in future). Instead use a
default of None and only supply the parameter if the config option is set.
Sounds right to me. Attached is an update patch.
On MySQL, it's necessary to supply to ``pool_recycle`` parameter on
engine creation, else the connection dies after some timeout and the
pool is unable to hand out a session.
The result of this is that the first request fails whenever the
connection has been dropped.
Attached is a patch
2009/5/23 Adam GROSZER agros...@gmail.com:
The problem that I see here with lxml is that it is used for output
checking. Even worse z3c.form requires at least 2.1.1 of lxml, where KGS
3.4 has lxml nailed at 1.3.6.
It might be possible to shed this testing dependency; ``lxml`` is used
because
2009/5/21 David Glick davidgl...@onenw.org:
Won't this cause problems if a z3c.form uses a template which calls a macro
from a traditional Zope page template? That is, make it impossible to use
z3c.form in a site that isn't using z3c.pt for everything?
That was the reason for z3c.ptcompat; it
2009/5/21 Adam GROSZER agros...@gmail.com:
Well, the strong target is to make z3c.form 2.0 compatible with
KGS 3.4. (z3c.pt is somehow intertwined with z3c.ptcompat too.)
That's the goal am chasing though I'm quite busy right now.
I don't know the implications of requiring zope.i18n = 3.5, but
Hello Adam, ––
The z3c.pt package shouldn't have difficult dependencies; it depends
on zope.i18n = 3.5 but reasons unknown to me (Hanno CC'ed).
Note that the package no longer depends on ``lxml``.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
Chris McDonough chrism at plope.com writes:
This is a pattern that happens over and over again in Zope
development. In my personal opinion, the original error was trying
to make the subframework configurable at all. Instead, the
subframework should be replaceable easily, but it should itself
2009/4/3 Roger Ineichen d...@projekt01.ch:
Can you run the group.txt tests in z3c.form and confirm the
issue. A
div tag get skipped after some nested repeat tags. (line 898, in
group.txt)
I've reproduced this bug in a test case in ``chameleon.zpt`` (r4073).
Will try and solve asap; thanks
2009/4/3 Roger Ineichen d...@projekt01.ch:
Can you fix this or give me some hints which let me do this?
This issue has been fixed and ``chameleon.core`` 1.0b27 released.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
2009/4/3 Roger Ineichen d...@projekt01.ch:
Can you run the group.txt tests in z3c.form and confirm
the issue. A div tag get skipped after some nested repeat
tags. (line 898, in group.txt)
Running with the latest ``chameleon.core``, ``chameleon.zpt`` and
``z3c.pt``, I only get one test failure:
2009/3/18 Christian Theune c...@gocept.com:
Did this get resolved by any means? As it didn't spur any discussion at
all, you might want to at least file a bug tracker issue for that
problem.
It has now been filed as https://bugs.launchpad.net/zope3/+bug/344680.
\malthe
2009/3/18 Christian Theune c...@gocept.com:
I'm not sure how to time the move, though. One option would be to
release a bugfix with the option as non-default and a feature release
with the option as default.
That's a good approach.
What kind of configuration should enable it; an environment
2009/3/18 Roger Ineichen d...@projekt01.ch:
This means to me that an empty value for id or name
doen't start with [A-Za-z] and is invalid because is must start
with [A-Za-z]. or not?
Correct, but should enforce these requirements? I think ZPT should
just have predictable, expected behavior,
Currently, if an attribute expression evaluates to any value that's
boolean False, it's omitted (e.g. 0, , object()). I think that's
unexpected. Instead, attributes should only be omitted when the
expression evaluates to ``None``.
How do folks feel about changing this behavior in
2009/3/10 Fred Drake fdr...@gmail.com:
The change would need to be in zope.tal.
True.
I'm ambivalent; while it makes sense to me in isolation, the affect on
existing templates is undesirable, and compatibility is a huge deal
for this bit of machinery.
I agree, but it would be interesting to
Code snippet:
def open(self, url, data=None):
See zope.testbrowser.interfaces.IBrowser
url = str(url)
This string coercion is unfortunate, because ``mechanize`` accepts a
(mechanize-) request-object in place of a URL string here. Using a
custom request object allows us to do
Just a note that the upcoming release of z3c.ptcompat will have a
module which monkey-patches ``zope.app.pagetemplate``, such that the
view page template classes use z3c.pt for rendering (just committed to
trunk).
This is an optional behavior which may ease transition to Chameleon.
Note that
2008/12/21 Philipp von Weitershausen phil...@weitershausen.de:
I've noticed you're using the U.S. date format here which we discourage due
to its ambiguity (in this case it happens not to be ambiguous, but that's
just coincidence). The preferred format is the ISO 8601 dash notation
I've branched out this package and removed the C-extension. It's not
documented in the package why a C-extension is needed or alternatively,
what it benefits.
If there are no objections, I will merge this into trunk shortly.
\malthe
___
Zope-Dev
Martijn Pieters wrote:
The C extension is required to make messageids immutable. Because they
are immutable, the security machinery can treat them as rocks, e.g.
safe to pass around. Removing the C-extension undoes this, as you
cannot make truely immutable.
I believe it is possible to do this
Malthe Borch wrote:
I believe it is possible to do this in pure Python:
The implementation may reviewed in this branch:
http://svn.zope.org/zope.i18nmessageid/branches/c-extension-less/
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
http
Marius Gedminas wrote:
Careful: id(some_object) will likely be reused when the old object is
garbage collected.
This has been worked around using the weak reference dictionary.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
Martijn Pieters wrote:
I object as well, and have asked for Malthe to provide his reasoning
here at the Plone Performance Sprint in Bristol, but so far his only
motivation is that he wants to see if he can get this to work without
a C-extension. I am sceptical he'll be able to, and am not
Martijn Faassen wrote:
My suspicion from observing the discussions in this thread so far
indicate that a drop in code complexity doesn't seem to be a necessary
consequence of rewriting to Python either.
The proposed implementation has already been implemented (walk up this
thread); it is
2008/12/10 Brian Sutherland [EMAIL PROTECTED]:
Below are the failures, Malthe, would you mind having a look at these?
I'll take a look at them; seems to be __repr__-related all around.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
2008/12/9 Roger Ineichen [EMAIL PROTECTED]:
I agree
A package should never use another package as it's namespace.
Which means a package can not be both a package and namespace for
other packages.
Seems to work fine for e.g. ``repoze.bfg``.
Malthe are you aware of this? Can you change it?
I
2008/12/9 Brian Sutherland [EMAIL PROTECTED]:
Please let me know if there's a step I'm missing?
There are other z3c.* packages which depend on it, namely
z3c.template
z3c.macro
z3c.pagelet
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
2008/12/8 Adam GROSZER [EMAIL PROTECTED]:
Coverage seems to burp on chameleon
I just tried a buildout in newest mode and I did not see the error you
pasted. It's important that the CHAMELEON_CACHE flag be set to '0' in
an automated test setup (this is set in the buildout for the test
runner).
2008/10/14 Binseer N [EMAIL PROTECTED]:
Hi all,
Can anybody tell me how can i add resource by using z3c.pt. i know how to
add it by using zope.pagetemplate, i tried it and it was working well. The
following is the code i am working with and it was not working with z3c.pt
There is a bug in
2008/9/16 Roger Ineichen [EMAIL PROTECTED]:
What is the reason why z3c.* packages should use z3c.pt and fallback
to a new concept rather then stay with PageTemplate if no lxml is
installed and z3c.pt is useless?
There seems to be some confusion here, and I understand why this has
arisen, but
2008/9/16 Stephan Richter [EMAIL PROTECTED]:
Yeah, I like that. This is the right package, since it defines high-level
patterns without any heavy implementations.
Unfortunately, ``zope.contentprovider`` relies on ``zope.tales``
because it implements a TALES expression and somehow, this package
2008/9/16 Roger Ineichen [EMAIL PROTECTED]:
Are you thinking about a basic UI interface package.
where we probably define some interfaces e.g.
IBrowserPage and friends and nothing else?
It really depends on how much we want to play with frameworks like
repoze.bfg that do not want complete
2008/9/16 Roger Ineichen [EMAIL PROTECTED]:
yes, this package must be a zope.* package.
Then we could move the ITerms interface to this
package too rather then add a new one like zope.term.
Could this package be called ``zope.browser`` then?
\malthe
Chris McDonough wrote:
Log message for revision 90974:
Added: z3c.pt/trunk/TODO.txt
===
--- z3c.pt/trunk/TODO.txt (rev 0)
+++ z3c.pt/trunk/TODO.txt 2008-09-09 00:03:08 UTC (rev 90974)
@@ -0,0 +1,4
2008/9/9 Stephan Richter [EMAIL PROTECTED]:
It's not strict. It's a shortcut.
No it's other way around.
tal:block for= / is the short-cut for tal:block tal:for= /.
Previously only the short-cut was allowed; this has been changed in
the most recent release of z3c.pt.
\malthe
2008/8/30 Dieter Maurer [EMAIL PROTECTED]:
This is correct for HTML PageTemplates; XML PageTemplates, too, require
the namespace declarations -- at least this has been the case
for the former Zope 2 version of PageTemplate (I do not yet
know most details about the newer Zope 3 PageTemplate).
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current zope.pagetemplate behavior).
\malthe
___
Zope-Dev maillist -
2008/8/29 Andreas Jung [EMAIL PROTECTED]:
--On 29. August 2008 12:31:21 +0200 Malthe Borch [EMAIL PROTECTED] wrote:
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current
Fred Drake wrote:
This is a controversial change; can we avoid making changes like this
until a policy is agreed upon?
The controversy surrounding this has been discussed on zope-dev
several times; I don't want to rehash it *right now*, since we all
have things we need to get done.
I
Fred Drake wrote:
There's no good way to avoid dependencies like zope.app.testing;
because that's part of the test environment, the tests won't show
whether there are problems when it's removed. If you want to fly what
you test, test dependencies can't be eliminated.
I understand, but this
Martin Aspeli wrote:
I'm trying to build a widget that allows for auto-complete of items in a
vocabulary, but also allows additional (string) values to be added. To
understand how that works, I am digging into z3c.formwidget.query, and
it looks to me like it's making incorrect assumptions
Martijn Faassen wrote:
Thanks for the offer. I think this is up to Laurence to decide, I'd
say. I'm aiming my work at the 0.5 series so I'm fine with requiring
0.5.
Me too, but I'd be careful to *require* an unreleased version.
\malthe
___
Zope-Dev
Lennart Regebro wrote:
2. Using **kw in the argument and looking for noth with and with_,
that way, which will be backwards compatible.
+1
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No
Chris McDonough wrote:
I've been working on a new web framework named (provisionally) repoze.bfg.
This looks very interesting; I'd be curious to see if this could be
useful for Vudo. I'd like it very much if Vudo could sit on top of a
more general framework (not just the Zope 3 libraries).
With an in-memory engine, I seem to lose track of the tables after the
first response.
Turn of events:
1. Request comes in
2. Create some tables
3. Add content and commit transaction
4. Query content
5. Return response
Now...
6. New request comes in
7. Query content
(OperationalError) no
Martijn Faassen wrote:
Could you be more explicit about what exactly in Grok was making too
many assumptions?
First a word on terminology: I mean Grok, the framework, not the
declarative extensions to the component architecture (which I simply
haven't gotten to yet).
We felt that Grok was
Martijn Faassen wrote:
So basically you felt Zope 3 wasn't a good match for Vudo, in the
sense that the normal browser:page wasn't really want you wanted
either, right? Similar to the way you could extend Zope 3 with your
own new ZCML directives to set up the way you'd like views to work
(I'm
Christian Theune wrote:
Develop: '/home/ctheune/Development/zc.buildout/.'
While:
Installing.
Getting section test2.3.
Initializing part test2.3.
Getting section python2.3.
Error: The referenced section, 'python2.3', was not defined.
FWIW, I made the following changes to get things
Currently views are registered as components providing
zope.interface.Interface; this is unfortunate since other kinds of
components may use the same specification, namely (context, request).
An example of this is ``IAbsoluteURL``; it clashes with the resources view*.
In the words of
Martijn Faassen wrote:
There's one major problem that I see. What's the backwards compatibility
story? I'm sure there are a lot of cases in lots of code where people
look up views with a getMultiAdapter, and if we started registering
views differently, wouldn't that code break? How to we get
Christian Theune wrote:
I don't think zope.component wants to know about views. The interface should
be in a package that already knows about views.
I agree it's an inappropriate location, however, zope.component *does*
define an ``IView`` interface as it is (zope.component.bbb.interfaces).
Hanno Schlichting wrote:
Log message for revision 87393:
In debug mode the actual source code for file templates is written
out to a filename.source file, to make it easier to inspect it.
Make debug mode setting explicit in a config.py. Currently it is
bound to Python's __debug__,
Tres Seaver wrote:
I don't think I would this to __debug__: I wouldn't want to pay a price
either at startup time or (worse) at render time for information I don't
need or want.
Is ``devmode`` available on Zope 2? That might be a good flag to control
this.
\malthe
I think a valuable extension to the parameter parsing in buildout's
configuration language would be to allow += and -= operators, which
would append and remove items, respectively.
Example:
[instance]
eggs += Products.PDBDebugMode
Singular or plural arguments would be supported.
\malthe
Philipp von Weitershausen wrote:
This isn't the buildout list :). I think buildout matters are discussed
on the distutils SIG mailinglist.
I guess they're also discussed here now :P
There's also an issue tracker at
https://edge.launchpad.net/zc.buildout.
I'll submit it there, thanks.
This is now:
https://answers.edge.launchpad.net/zc.buildout/+question/35159
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
Malthe Borch wrote:
However, trying to get the absolute url of the resource fails, and it
seems to be an acquisition-wrapping thing.
FWIW, this adapter will do the trick, although it's hardly a solid solution:
class SimpleResourceAbsoluteURL(object):
interface.implements
These three don't mix well; here's the setup:
Using ``zope.traversing.api.traverse``, we're able to traverse from the
site root to the directory resource, and on to the actual resource by
way of OFS.Traversable.
However, trying to get the absolute url of the resource fails, and it
seems to
Jodok Batlogg wrote:
and yes again. unfortunately there is no open source / non-google DB
application implementation so far. we keep this in mind.
There is http://hypertable.org, but of course that's not an application
engine.
\malthe
___
David Pratt wrote:
Hi Jodok. I had looked at storm a while back but the zope integration
seemed to lack any relationship with zope schemas. I guess it is
possible to define a zope schema that is not persisted and create the
tables from it. It did not seem to me a good way of using CA. How are
David Pratt wrote:
Hi Malthe. z3c.dobbin looks quite good and transparent. In my opinion,
this is much closer to what integration ought to look like for CA. BTW,
I noticed that z3c.dobbin is zpl but ore.alchemist that it depends on is
gpl. I think all the other zope flavors of sqlalchemy are
David Pratt wrote:
Hi Malthe. Kapil has confirmed the licensing is ZPL with a version bump
to 0.5.2 with a change in the headers, etc. I am anxious to experiment
with dobbin since it looks so straight forward and nice. I guess I see
traversal and containers as possible issues but will be
Kenneth Miller wrote:
Any and all feedback is appreciated and I will carefully consider
every idea.
For your application: A major drawback is that the underlying
architecture relies on setup file based configuration.
Does it, and is it?
\malthe
Malthe Borch wrote:
For^D^D^DFrom your application...
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope
The ``constraints`` module in zope.app.container seem to be usable
outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not have
to pull in ZODB just to get these frameworky definitions.
Is it package overkill to move
Some motivation:
File .../zope/interface/adapter.py, line 482, in queryMultiAdapter
result = factory(*objects)
TypeError: __init__() takes exactly 2 arguments (3 given)
Perhaps the need for introspection tools would not be so immediate if
the exceptions were more informative; for
On Z2, certain imports need to come from Products.Five, to play nicely
with ZPublisher and friends.
I'd like to ask for the motivation for not patching it onto the existing
classes and/or modules. The effect of having Z2-developers import from
Products.Five is that they must opt out on
Daniel Nouri wrote:
Therefore, I'd argue that we should, in contrary to what you suggest,
make the Zope 2 compatibility layer more explicit in the form of utility
functions, instead of more implicit. Because it makes things more
transparent and easier to debug.
You might be right; but it's a
On 07/04/2008, Chris Withers [EMAIL PROTECTED] wrote:
...and I'll bet that's only to run the tests, so should be removed as a
hard dependency
Actually, only the tests require it –– sorry :-)
Now, does anyone want me to set up a Launchpad project for this?
How do I go about building a Python
On 07/04/2008, Chris Withers [EMAIL PROTECTED] wrote:
I'd certainly be up for championing making RestrictedPython available as a
seperate project. Has anyone done any work towards this or should I go ahead
and get a project / bug tracker / etc set up at Launchpad?
RestrictedPython depends
ranjith kannikara wrote:
I am a student participating in Google Summer of code 2008. My
proposal to the Zope foundation is to port
Zope2 to Python2.5. I am aware of the works done earlier for porting
Zope3 and the issue like
restricted python implementation. Please give some suggestions on this
On 04/04/2008, Chris Withers [EMAIL PROTECTED] wrote:
zope.security uses RestrictedPython, iirc...
For untrusted python, yes –– but is anyone using this (in Zope 3)?
It's integral to most Zope 2 applications of course to allow secure
execution of Python scripts, so we will need to port
Stephan Richter wrote:
I am very happy about my tests in z3c.form. They demonstrate tests with
different audiences in mind.
Rightly so; they're excellent and make transition away from formlib easy.
\malthe
___
Zope-Dev maillist -
Jim Fulton wrote:
Thanks for creating this. I just (finally) commented.
I've elaborated on that paragraph.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related
Martijn Faassen wrote:
I just added a whole range of Grok-related projects to the summer of
code page, and only 1 Zope project, so if you want Zope 2 or 3 to be
represented in the google summer of code, you might want to consider
adding some proposals. :)
I just sent a tentative proposal to
Jim Fulton wrote:
+1. Some more details would need to be worked out. For example, to work
for your use case, it would need to be involved in search, or the
searching rules would need to be made more powerful, so, when looking
for some file name, it is prepared to consider files that have the
Jim Fulton wrote:
+1. Some more details would need to be worked out. For example, to work
for your use case, it would need to be involved in search, or the
searching rules would need to be made more powerful, so, when looking
for some file name, it is prepared to consider files that have the
The z3c.pt-package now provides a template class for plain text files
like .css and .js---using the ${python expression}-syntax.
I'd like to integrate it with browser resources such that
filename.css.some extension for z3c.pt text templates
would be sent through the template engine.
Now,
Christian Zagrodnick wrote:
when will this be merged to the trunk and released? Any plans for that?
I still need to hook up the resource bundle with the publisher. The
implementation hasn't been tested in a browser yet. There might be caveats.
I'll try and bring the branch into a fully
Fred Drake wrote:
On Jan 18, 2008, at 10:35 AM, Malthe Borch wrote:
In the current implementation, z3c.jbot monkeys its way into
zope.pagetemplate to easily allow overriding the template source file.
Whacky.
Sure it's wacky; it's also the only straightforward way to customize
Plone
The z3c.jbot package basically offers an easy way to provide template
overrides much like zope 2 skins. It addresses the common issue with
using a framework that already provides its own skin; you want to be
able to easily customize it.
In the current implementation, z3c.jbot monkeys its way
But I also have a question. Should we not use another
namspace for Zope packages which depend on Five or
other packages then zope.* or z3c.*?
The package makes no assumptions that Five is available, but there are
tests for a scenario where it is.
\malthe
I agree with your analysis. Could you file a bug report in launchpad?
Bug now filed: https://bugs.launchpad.net/zope3/+bug/162166.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
1 - 100 of 101 matches
Mail list logo
