Log message for revision 78398:
Death to __of__!
Changed:
U Zope/branches/philikon-aq/lib/python/OFS/Traversable.py
U
Zope/branches/philikon-aq/lib/python/Products/Five/browser/metaconfigure.py
U
Zope/branches/philikon-aq/lib/python/Products/Five/browser/providerexpression.py
Log message for revision 78399:
Rip out test that tested the bogus behaviour of having self.context (where
'self' is a view) have an aq_chain that includes the view again.
Naturally, this branch is all about ripping this out.
Changed:
U
Log message for revision 78401:
Use either obj.__parent__or aq_parent(obj) instead of obj.aq_parent.
Both are the canonical forms of getting to an object's parent now.
Changed:
U Zope/branches/philikon-aq/lib/python/AccessControl/ImplPython.py
U
Log message for revision 78403:
Use the canonical form for getting to an object's innermost wrapper
and an object's parent by usingn the aq_parent and aq_inner *functions*,
not attributes.
Changed:
U Zope/branches/philikon-aq/lib/python/Shared/DC/Scripts/Bindings.py
-=-
Modified:
Log message for revision 78404:
Remove bogus line. There actually *is* a proper options dict coming
from the base class.
Changed:
U
Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py
-=-
Modified:
Log message for revision 78405:
There was a 'not' too much. Thanks Hanno.
Changed:
U Zope/branches/philikon-aq/lib/python/AccessControl/Owned.py
-=-
Modified: Zope/branches/philikon-aq/lib/python/AccessControl/Owned.py
===
Log message for revision 78408:
Add a module-level aq_inContextOf function, along the lines of the
module-level aq_acquire, aq_inner, aq_parent, etc. functions.
Changed:
U Zope/branches/philikon-aq/lib/python/Acquisition/_Acquisition.c
U
Log message for revision 78332:
Get rid of packages that were never in Zope2 (or Zope3, for that matter) and
simply
shouldn't be released. Who put them in here?!?
Bring back packages that were removed, for who knows which reason. Point is,
we can't
just simply remove things from a
Log message for revision 78334:
Make list easier to read
Changed:
U Zope/trunk/setup.py
-=-
Modified: Zope/trunk/setup.py
===
--- Zope/trunk/setup.py 2007-07-25 20:53:58 UTC (rev 78333)
+++ Zope/trunk/setup.py 2007-07-25
Log message for revision 78335:
Bring back ZEO scripts that were removed in r76349.
Changed:
U Zope/trunk/setup.py
-=-
Modified: Zope/trunk/setup.py
===
--- Zope/trunk/setup.py 2007-07-25 20:59:25 UTC (rev 78334)
+++
Log message for revision 78338:
Discourage the use of the upper-case RESPONSE attribute. The lower-case
response attribute works perfectly fine (and has for ages) and it has the
advantage of being supported by Zope 3 as well.
Changed:
U
Log message for revision 78333:
Merged philikon-zope2.11-with-standard-docutils:
- Ship Zope with a standard docutils 0.4 distribution, instead
of a patched one. Both trusted and untrusted code are still
protected against unwanted file inclusion.
Changed:
Log message for revision 78314:
Merged from old philikon-aq-and-__parent__ branch:
Log message for revision 71221:
Step 2: Make aq_acquire aware of __parent__ pointers, even if the object
isn't acquisition wrapped.
Log message for revision 71223:
Add another test that tests
Log message for revision 78318:
Merged from old philikon-aq-and-__parent__ branch:
Log message for revision 71227:
Step 4: Make aq_get aware of __parent__ pointers.
(Also some comment cosmetics in _Acquisition.c)
Log message for revision 71228:
Test aq_parent property as
Log message for revision 78319:
Merged from old philikon-aq-and-__parent__ branch:
Log message for revision 77024:
Read that mail again, we agreed on raising an AttributeError instead of
returning None.
Changed:
U
Log message for revision 77679:
New branch for the Acquisition + __parent__ work, revising changes in the old
branch.
Changed:
A Zope/branches/philikon-aq/
-=-
Copied: Zope/branches/philikon-aq (from rev 77678, Zope/trunk)
___
Zope-Checkins
Log message for revision 77680:
Merge r71220 from old branch:
Warming up: Make acquisition wrappers have __parent__ in addition to
aq_parent
(they point to the same thing).
Changed:
U Zope/branches/philikon-aq/lib/python/Acquisition/_Acquisition.c
U
On 6 Jul 2007, at 09:59 , Andreas Jung wrote:
--On 6. Juli 2007 01:48:11 +0200 Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
Andreas Jung wrote:
now that Zope 3.4.0b1 has been tagged, I plan to release Zope
2.11.0b1
by mid-July. Objections?
Like Chris, I'd rather have one or two
On 6 Jul 2007, at 16:47 , Andreas Jung wrote:
ok, I'll make
- a1 around July 18th (tag against the current trunk)
- b1 around August 8th (new 2.11 branch)
Sounds reasonable?
Sure. The b1 might even happen a week sooner if it were up to me...
___
Andreas Jung wrote:
now that Zope 3.4.0b1 has been tagged, I plan to release Zope 2.11.0b1
by mid-July. Objections?
Like Chris, I'd rather have one or two alphas first. Why not make an
alpha mid-July and perhaps a beta at the end of July?
--
http://worldcookery.com -- Professional Zope
On 28 Jun 2007, at 17:03 , Andreas Zeidler wrote:
On Jun 25, 2007, at 10:05 AM, Philipp von Weitershausen wrote:
On 21 Jun 2007, at 23:47 , Andreas Zeidler wrote:
On Jun 21, 2007, at 9:07 PM, Tres Seaver wrote:
ah, here it is: http://svn.zope.org/?rev=76408view=rev should
fix
the zclasses
On 26 Jun 2007, at 14:56 , Tres Seaver wrote:
Philipp von Weitershausen wrote:
On 25 Jun 2007, at 12:09 , Andreas Jung wrote:
--On 25. Juni 2007 10:13:44 +0200 Andreas Zeidler [EMAIL PROTECTED]
wrote:
On Jun 25, 2007, at 10:05 AM, Philipp von Weitershausen wrote:
true, but i think philipp
Andreas Jung wrote:
Cdoc/CHANGES.txt
Ulib/python/Products/Five/i18n.zcml
Ulib/python/Products/Five/event.zcml
Ulib/python/Products/Five/meta.zcml
Ulib/python/Products/Five/form/tests/forms.txt
Dlib/python/Products/Transience/tests/testCounters.py
U
On 21 Jun 2007, at 23:47 , Andreas Zeidler wrote:
On Jun 21, 2007, at 9:07 PM, Tres Seaver wrote:
ah, here it is: http://svn.zope.org/?rev=76408view=rev should fix
the zclasses problem, if i'm not totally mistaken.
That change needs backporting, I think, to the ZODB 3.6 line (for
2.9)
and
On 25 Jun 2007, at 12:09 , Andreas Jung wrote:
--On 25. Juni 2007 10:13:44 +0200 Andreas Zeidler [EMAIL PROTECTED] wrote:
On Jun 25, 2007, at 10:05 AM, Philipp von Weitershausen wrote:
true, but i think philipp was only asking about 2.11 for the time
being. i agree the fix should
Hanno Schlichting wrote:
as some of you may have noticed I worked a bit more on philikon's branch
which makes Acquisition and in return the Zope2 security machinery aware
of __parent__ pointers.
Yay, thanks Hanno!
As I won't have much time to work on this anymore, I would encourage all
of
Are there any outstanding issues on that Zope211-3.4-integration branch?
If not, I'd like to see it merged, now that ZODB 3.8 has beta'ed.
--
http://worldcookery.com -- Professional Zope documentation and training
___
Zope-Dev maillist -
Stefan H. Holek wrote:
Log message for revision 76597:
Collector #2307: ObjectCopiedEvent not dispatched to sublocations.
...
@@ -130,7 +131,15 @@
if OFS.interfaces.IObjectManager.providedBy(ob):
dispatchToSublocations(ob, event)
[EMAIL PROTECTED](OFS.interfaces.IItem,
On 20 Jun 2007, at 12:20 , Andreas Jung wrote:
--On 20. Juni 2007 12:04:26 +0200 Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
Are there any outstanding issues on that Zope211-3.4-integration
branch?
If not, I'd like to see it merged, now that ZODB 3.8 has beta'ed.
The only
On 20 Jun 2007, at 13:16 , Stefan H. Holek wrote:
I took my cues from how ObjectModifiedEvent is handled. I figured
copied and moved should be treated the same. Also, there is this
comment in OFS/subscribers.py:
# The following subscribers should really be defined in ZCML
# but we don't
Log message for revision 76626:
Harden tests a bit and add a test that actually checks whether the monkey
patch
that turns off docutils' file insertino feature off by default actually works.
Changed:
U
Wichert Akkerman wrote:
I wanted to share a bit of experience I just had with use of eggs in Zope2.
For a project I am working on I want to use the zope.sendmail package in
a Zope2 environment managed using buildout. I added zope.sendmail to the
eggs list in the buildout configuration and ran
On 7 Jun 2007, at 08:45 , Andreas Jung wrote:
--On 6. Juni 2007 18:01:27 +0200 Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
At the PIKTipi sprint this past weekend, Andi Zeidler, Andreas
Jung and I
worked on integrating ZODB 3.8 and Zope 3.4 into the Zope 2 trunk.
Zope
3.4 has
On 7 Jun 2007, at 10:40 , Chris Withers wrote:
Philipp von Weitershausen wrote:
* as newer versions of specific zope.* or ZODB packages are
released, you can individually install those or not. There'll be
no need to wait for another Zope 2 release.
I actually see this as a downside
Log message for revision 76421:
Alternate approach to shipping with a standard docutils distribution and
still preserving security
measurements that Zope installed.
Changed:
A Zope/branches/philikon-zope2.11-with-standard-docutils/
-=-
Copied:
Log message for revision 76433:
Alternate approach to forbidding file inclusion in reStructuredText that's
used from Zope:
* ship with a standard docutils package
* don't monkey patch docutils functions, rather change the default setting
for
file_inclusion_enabled in the docutils
At the PIKTipi sprint this past weekend, Andi Zeidler, Andreas Jung and
I worked on integrating ZODB 3.8 and Zope 3.4 into the Zope 2 trunk.
Zope 3.4 has actually exploded into many eggs that are now
independently managed and released. I therefore looked into a way to
make Zope 2 dependent on
Log message for revision 76328:
Point to the one and only RestrictedPython we now have (the one that has been
set free
as its own project, egg).
Changed:
_U Zope/trunk/lib/python/
D Zope/trunk/lib/python/RestrictedPython/
-=-
Property changes on: Zope/trunk/lib/python
Log message for revision 76337:
Use standard doctest.DocFileSuite, no need for ZopeTestCase...
Changed:
D Zope/trunk/lib/python/Interface/tests/framework.py
U Zope/trunk/lib/python/Interface/tests/test_bridge.py
-=-
Deleted: Zope/trunk/lib/python/Interface/tests/framework.py
Log message for revision 76196:
Remove deprecated stuff that's scheduled for removal in Zope 2.11
Changed:
D Zope/trunk/lib/python/ImageFile.py
D Zope/trunk/lib/python/Zope.py
-=-
Deleted: Zope/trunk/lib/python/ImageFile.py
On 19 Apr 2007, at 08:25 , Christopher Lozinski wrote:
The problem with upgrading ZClasses is that it would break the zope
security models, and the Zope Product Model.
That depends on what you by upgrading ZClasses. To make them
continue to work, simpler changes will probably suffice.
It
Christopher Lozinski wrote:
I need a very simple app. Just 1 ZClass, an invoice object. Not even
subitems on the invoice. I want to create these ZClasses, I want a
table of these ZClasses, I want to be able to say which role gets to
create these objects, which role gets to see which fields,
Philipp von Weitershausen wrote:
Christopher Lozinski wrote:
I need a very simple app. Just 1 ZClass, an invoice object. Not even
subitems on the invoice. I want to create these ZClasses, I want a
table of these ZClasses, I want to be able to say which role gets to
create these objects
whit wrote:
2 items:
1. how does everyone feel about adding the following boilerplate to all
occurences of Products/__init__.py to enable the easy creation of
Product eggs?
try:
__import__('pkg_resources').declare_namespace(__name__)
except ImportError:
from pkgutil import
Wichert Akkerman wrote:
Previously whit wrote:
2 items:
1. how does everyone feel about adding the following boilerplate to all
occurences of Products/__init__.py to enable the easy creation of
Product eggs?
Aren't we asking people to move to using python packages instead?
Well, I
Stefan H. Holek wrote:
Most ObjectEvents are dispatched to sublocations.
Well, the ones that deal with the object hierarchy. This mostly concerns
IObjectMovedEvents and their sub-event types (added, removed). I don't
think it makes a lot of sense to dispatch other object events.
I was
Philipp von Weitershausen wrote:
Stefan H. Holek wrote:
Most ObjectEvents are dispatched to sublocations.
Well, the ones that deal with the object hierarchy. This mostly concerns
IObjectMovedEvents and their sub-event types (added, removed). I don't
think it makes a lot of sense to dispatch
Sascha Welter wrote:
Yesterday evening I installed 2.10.3 for some tests with Zwiki (haven't
tried any of the other 2.10s). I noticed that the wiki logo wasn't
displayed. I think I narrowed it down to the default keyword in
tal:replace being treated like nothing.
My testcase (in a blank
Derek Richardson wrote:
Zope 3.3
I want to add a viewlet to the rotterdam skin. I don't want to create my
own skin. is there an accepted way of doing this? I'm surprised that the
left sidebar in rotterdam doesn't appear to have a viewlet manager. I
have been unable to find any declarations
Martijn Pieters wrote:
On 3/21/07, Martijn Pieters [EMAIL PROTECTED] wrote:
On 3/21/07, Stefan H. Holek [EMAIL PROTECTED] wrote:
Python 2.3 does not support the @decorator syntax.
My bad, I'll fix.
Done. I hadn't even properly run the tests on the 2.8 branch, which
would would also have
The Zope Foundation has been accepted as a mentoring organization in
this year's Google Summer of Code project. That means chosen students
who want to hack on one of the Zope projects (Zope 2, Zope 3, ZODB, CMF,
grok, ...) this coming summer will get paid USD 4,500 if they
successfully
Christian Theune wrote:
a) I want to do the switch to ZODB 3.8 (currently trunk)
b) That needs zope.proxy as of Zope 3.4 (currently trunk)
Is there anything that would block this and if something how I can
contribute unblocking it?
The only way to really find out is to try it. Zope 3.3 and
On 7 Mar 2007, at 12:24 , Lennart Regebro wrote:
On 3/5/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
a) mentors.
It'd be great if some of the Zope core committers would
volunteer to
mentor a student. This doesn't mean you will definitely end up
mentoring one, just show
Christian Theune wrote:
Hi,
[modified slightly from a similar proposal to zope3-dev to match Zope
2's publisher]
I'm writing up a proposal for the ZODB to make even more efficient Blob
handling possible.
This includes not copying the data from an uploaded file, but using a
`link` operation
Stephan Richter wrote:
On Sunday 04 March 2007 20:02, Philipp von Weitershausen wrote:
a) mentors.
It'd be great if some of the Zope core committers would volunteer to
mentor a student. This doesn't mean you will definitely end up
mentoring one, just show your willingness.
I
Basil Shubin wrote:
Basil Shubin wrote:
Hi friends,
I want use zope.testbrowser for testing my sites, but before write it
as DocTest I want execute each statemnt interactively in python shell.
I don't know any way to see where it's works, what value it returns,
what error I can get and how
michael nt milne wrote:
Hi
On trying to make a new zopeinstance from a Plone 2.5 instance created
using the unified installer I am getting the following error when I
attempt to run ./zopectl and start the instance.
Traceback (most recent call last):
...
NameError: name 'set' is not
Tres Seaver wrote:
Tres Seaver wrote:
Roché Compaan wrote:
On Fri, 2007-02-23 at 06:55 -0500, Tres Seaver wrote:
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching ZCatalog
results and if I submitted a patch to do this would it be excepted?
I quickly coded
Stefan H. Holek wrote:
Log message for revision 72754:
Raise SyntaxError when encountering invalid PythonScript headers.
Changed:
U Zope/branches/2.9/lib/python/Products/PythonScripts/PythonScript.py
U
Zope/branches/2.9/lib/python/Products/PythonScripts/tests/testPythonScript.py
Mark, Jonathan (Integic) wrote:
Here is my configure.zcml file, which is identical to the one Paul Everitt says
to write:
configure xmlns=http://namespaces.zope.org/browser;
page
name=hello
template=helloworld.html
Geoff Gerrietts wrote:
[some paragraphs about scaling which I can't really comment on]
As for source control, I figure all of your code (DTML, yuck) is in the
ZODB. This went out of fashion a long time ago, most serious development
happens on the filesystem (in Python packages) which can
On behalf of the Zope Foundation I'm happy to announce the release of
Zope 3.3.1, a bugfix release for the current stable 3.3.x line. Zope
3.3.1 contains a number of bugfixes, though most importantly it fixes
compatibility with Python 2.4.4.
You can find more information as well as a tarball
Geoff Gerrietts wrote:
I have a couple questions about the current game plan for Zope
development that I was unable to answer for myself by searching through
mailing list archives and the zope.org http://zope.org website. I hope
my inability to answer them is not merely a symptom of poor
On 5 Feb 2007, at 12:22 , Martijn Faassen wrote:
Some of the holdup is in the bylaws. The bylaws were, simply put,
rather overengineered, and we've been struggling to cut them down so
we can actually work with them. This is holding up the IP transfer.
Ok. Is there anything us mere mortals can
Jens Vagelpohl wrote:
On 4 Feb 2007, at 12:47, Wichert Akkerman wrote:
I'm not quite sure it has to be part of Zope 2 as you install it. Having
it in svn.zope.org would go a long, way, though, allowing us to use
svn:externals during development and potentially fix issues ourselves as
Dieter Maurer wrote:
Whit (mailto:[EMAIL PROTECTED]) reported that AdvancedQuery
is going to ship with Plone3 and that packaging would be easier for them if
AdvancedQuery were part of the Zope 2 distribution.
I fail to find an explanation *why* that is.
According to Whit, Alexander Limi
Martin Aspeli wrote:
Philipp von Weitershausen wrote:
Dieter Maurer wrote:
Whit (mailto:[EMAIL PROTECTED]) reported that AdvancedQuery
is going to ship with Plone3 and that packaging would be easier for
them if
AdvancedQuery were part of the Zope 2 distribution.
I fail to find
Tres Seaver wrote:
Chris Withers wrote:
Andreas Jung wrote:
0, for keeping zLOG for the time being...
-1, for undeprecating it. Using Python's logging module should remain
the only recommended solution. I don't want to see any new code using
zLOG.
+1 for undeprecating it -- the noise it
Chris McDonough wrote:
How many people would get indignant if I checked in a fix that
undeprecated zLOG? Removing the API seems silly, since its just a
wrapper around the logging module now anyway.
±0
I've become indifferent.
--
http://worldcookery.com -- Professional Zope documentation
Graziella Toutoungis wrote:
Hello,
[...]
This is the wrong list, please write to zope@zope.org with general
problems about *using* Zope.
Please don't respond to this email.
--
http://worldcookery.com -- Professional Zope documentation and training
Next Zope 3 training at Camp5:
Martin Aspeli wrote:
Jim Fulton wrote:
[foo]
recipe=zc.recipe.egg
eggs = egg1 egg2 ...
interpreter = mypy
extra-paths = path-to-your-instance/lib/python
scripts = mypy
This is great :) I used eggs = ${instance:eggs} to make sure it has the
same eggs as our
Ian Bicking wrote:
It would be a concern if, for instance, Plone started depending on
buildout recipes for installation, without plain distutils recipes. Of
course right now there are no distutils recipes for old-style Products.
So actually it's an active issue -- if buildout enables Plone to
Rob Miller wrote:
honestly, it seems to me that buildout tries to do too much.
That's ok. I often don't need the big hammer that buildout is. That's
when I tend to use workingenv (even if it's' just for trying out whether
something's easy_install'able)
it's
trying to handle both
Rocky Burt wrote:
On Thu, 2007-25-01 at 05:07 -0800, Martin Aspeli wrote:
I do wonder what would happen if you had both lib/python/Products/CMFCore
and Products/CMFCore, though. Would there be an explicit preference or would
Zope fail to start up with a conflict? I think I'd prefer the latter,
whit wrote:
Martin Aspeli wrote:
Philipp von Weitershausen wrote:
This is awesome, and by that I don't mean the fact that we have a
plone buildout, but that we actually have Zope 2 recipes for
buildout. I hope they can be moved to svn.zope.org for further
development to benefit the whole
Daniel Nouri wrote:
Philipp von Weitershausen wrote:
For their upcoming versions, Zope 2 consuming platforms such as Plone
are creating standard Zope3-style Python packages while still having
Zope 2 products around. This proposal aims at unifying the deployment
of products and Python packages
This proposal aims at bringing Zope 2 a bit closer to Zope 3 by making
the widely used Acquisition API aware of Zope 3's __parent__ pointers.
This will alleviate the need of using Acquisition base classes in Zope 2
for every security-sensitive object, be it persistent or just a
dynamically
Log message for revision 72027:
Update externals to newly released Zope 3.3.1, and remove a monkey patch that
was fixed in Zope 3.3 proper.
Changed:
U Zope/branches/2.10/doc/CHANGES.txt
_U Zope/branches/2.10/lib/python/
U
Grig Gheorghiu wrote:
I'm trying to check out zope.interface for one of the tests I'm running
for Twisted in the Pybots project. I've been getting an error lately:
[EMAIL PROTECTED] tmp]$ svn co
svn://svn.zope.org/repos/main/zope.interface/trunk zope.interface
A zope.interface/buildout.cfg
A
Chris Withers wrote:
Stephan Richter wrote:
If you are populating the CA before ZCML is fully parsed, then:
Why is the CA predicated on ZCML?!
It's not. And Stephan's Collect all registrations before executing
them! isn't actually necessary either (it's just necessary for conflict
Chris Withers wrote:
Stephan Richter wrote:
If you are populating the CA before ZCML is fully parsed, then:
Why is the CA predicated on ZCML?!
It's not. And Stephan's Collect all registrations before executing
them! isn't actually necessary either (it's just necessary for conflict
Log message for revision 71860:
prepare release
Changed:
U Products.Five/branches/1.5/CHANGES.txt
U Products.Five/branches/1.5/INSTALL.txt
-=-
Modified: Products.Five/branches/1.5/CHANGES.txt
===
---
Dieter Maurer wrote:
I tried to use Zope3 events to get informed when requests start and end.
One of our modules (the interface module to jpype) requires such
a notification for reliable work. Therefore, it tried to register
the corresponding subscriptions on import of this module.
That is an
Dieter Maurer wrote:
I tried to use Zope3 events to get informed when requests start and end.
One of our modules (the interface module to jpype) requires such
a notification for reliable work. Therefore, it tried to register
the corresponding subscriptions on import of this module.
That is an
Log message for revision 71847:
Merge from 2.10 branch:
Log message for revision 71846:
Back out accidental commit from yesterday
Changed:
U Zope/trunk/skel/etc/site.zcml
-=-
Modified: Zope/trunk/skel/etc/site.zcml
Log message for revision 71797:
Give test a better name
Changed:
D
Zope/branches/2.9/lib/python/Products/PageTemplates/tests/input/Attributes.html
A
Zope/branches/2.9/lib/python/Products/PageTemplates/tests/input/BooleanAttributesAndDefault.html
D
Log message for revision 71799:
Fixed Collector #2223: Evaluation of booleans in TALES and the 'default'
variable.
That consisted of forwardporting r70918 and r71797 from the 2.9 branch and
providing
a fix.
Changed:
U Zope/branches/2.10/doc/CHANGES.txt
U
Log message for revision 71801:
get rid of deprecated import
Changed:
U Zope/trunk/lib/python/ZPublisher/tests/testPublish.py
-=-
Modified: Zope/trunk/lib/python/ZPublisher/tests/testPublish.py
===
---
Log message for revision 71815:
Merge from 1.4 branch:
Log message for revision 71811:
Add an ftest that demonstrates zope.security.management.checkPermission()
works in Zope 2.
This is the reproduceability test case for
http://www.zope.org/Collectors/Zope/2190.
Log message
yuppie wrote:
Hi!
Andreas Jung wrote:
I plan to release Zope 2.10.2 in a week or so (don't nail
me to a particular date).
The Zope 2.10 branch still uses Five 1.5.1. There are a few changes on
the Five 1.5 branch (including a security fix) which should become part
of Zope 2.10.2.
I
Andreas Jung wrote:
I added Products/PageTemplates/configure.zcml to register an utility.
That works fine when running Zope however zopectl test won't work
properly anymore because the utility registration does not seem to
happen when running the tests. Bug or feature?
Tests need to do their
On 7 Jan 2007, at 20:44 , Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Andreas Jung wrote:
I added Products/PageTemplates/configure.zcml to register an
utility.
That works fine when running Zope however zopectl test won't work
properly
I'm proud to announce that -- as the first Zope book ever -- my book
titled Web Component Development with Zope 3 has been released as a
second edition and is now available from online and local bookstores.
Like the first edition, the new book is targeted at all web developers
who want to get
Peter Bengtsson wrote:
Something I like about Zope3 is the View classes.
What I like about it especially is that it's a brilliant place for
putting in little extra silly python methods that are specific to your
template rather than the object class. Eg.
class ViewProduct(BrowserPage):
Sidnei da Silva wrote:
I was wondering why there is no easy way to register a view for an
exception in Zope 2 yet (not even in Zope 2.10!).
Because nobody has refactored Zope 2 to support this yet...
There is a product in the z3-base called FiveException:
Chris Withers wrote:
I don't know how easy this is to do, but one thing that would be
_really_ nice would be to use an existing compatible python install
rather than Zope splatting it's own in regardless.
-1
That's what Zope 3 does (it's a standard distutils installer). It makes
it hard to
Edward Pollard wrote:
Hi all,
I've got three subsites that formerly used three different templates. I'd
like for them now to use the same template, but I'd prefer not to have to
touch the thousands of pages of content that currently point in three
different places for their template.
The easy
The Five team is happy to announce the release of three Five stable
releases today! Many thanks to Rocky Burt for making those releases!
What is Five
Five is a Zope 2 product that allows you to integrate Zope 3
technologies into Zope 2, today. Among others, it allows you to use
Log message for revision 71072:
announce new five releases
Changed:
U Products.Five/branches/1.5/doc/main.txt
-=-
Modified: Products.Five/branches/1.5/doc/main.txt
===
--- Products.Five/branches/1.5/doc/main.txt
Log message for revision 71074:
Put a certain changelog entry in the right place
Changed:
U Products.Five/branches/1.3/CHANGES.txt
U Products.Five/branches/1.4/CHANGES.txt
U Products.Five/branches/1.5/CHANGES.txt
U Products.Five/trunk/CHANGES.txt
-=-
Modified:
201 - 300 of 870 matches
Mail list logo
