Log message for revision 66230:
Convert some uses of ISiteManager to IComponentLookup.
Get rid of some deprecated stuff that is to go away for Five 1.5.
Changed:
U Products.Five/branches/philikon-local-components/site/interfaces.py
U
Log message for revision 66231:
Remove unnecessary rebind magic.
Tighten the screws on a test whether 'view' is None or not.
Changed:
U
Products.Five/branches/philikon-local-components/browser/pagetemplatefile.py
-=-
Modified:
Log message for revision 66232:
template - zpt
Changed:
U Products.Five/branches/philikon-local-components/component/configure.zcml
D
Products.Five/branches/philikon-local-components/component/customizetemplate.pt
A
Andreas Jung wrote:
Zope 2.8 ships/shipped with Five 1.0 which is very old and no longer
actively maintained. Most ppl doing currently development with Zope
2.8 are using Five 1.2. Should we upgrade the Five version in Zope
2.8 to Five 1.2 to make their lives a bit easier? There is possibly
Chris McDonough wrote:
-1... Five 1.2 has quite a few differences from Five 1.0 that would stop
products written for Five 1.0 from working properly. I've not gone to
2.9 on a few projects for this reason (sticking with 2.8). 2.9 is where
the new version belongs, IMO.
Out of curiosity, what
Log message for revision 66177:
1. Let's not be too ambitious and try to solve WebDAV issues that we don't
know
are actually there.
2. ZPublisher now makes sure that the request has the default skin
Changed:
U Products.Five/branches/philikon-fix-lookup-priorities/traversable.py
Log message for revision 66185:
update to latest revision of ZODB 3.6 for upcoming release
Changed:
_U Zope/branches/2.9/lib/python/
-=-
Property changes on: Zope/branches/2.9/lib/python
___
Name: svn:externals
- ZConfig
Log message for revision 66187:
report changes for this branch
Changed:
U Products.Five/branches/philikon-fix-lookup-priorities/CHANGES.txt
-=-
Modified: Products.Five/branches/philikon-fix-lookup-priorities/CHANGES.txt
===
Log message for revision 66188:
Move to Zope 3.2.1, which also means we have to include copies of pullparser
and ClientForm (zope.testbrowser dependencies) now.
Changed:
_U Zope/branches/2.9/lib/python/
A Zope/branches/2.9/lib/python/ClientForm.py
A
Log message for revision 66191:
Merge philikon-fix-lookup-priorities and fix up doc files for upcoming
release.
Changed:
U Products.Five/branches/1.3/CHANGES.txt
U Products.Five/branches/1.3/INSTALL.txt
U Products.Five/branches/1.3/browser/tests/test_traversable.py
U
Log message for revision 66195:
better Zope trunk compatibility
Changed:
U Products.Five/branches/1.4/browser/tests/test_traversable.py
-=-
Modified: Products.Five/branches/1.4/browser/tests/test_traversable.py
===
---
Log message for revision 66196:
better Zope trunk compatibility
Changed:
U Products.Five/branches/1.3/browser/tests/test_traversable.py
-=-
Modified: Products.Five/branches/1.3/browser/tests/test_traversable.py
===
---
Log message for revision 66199:
Grrr... was still not right with the trunk
Changed:
U Products.Five/branches/1.3/browser/tests/test_traversable.py
-=-
Modified: Products.Five/branches/1.3/browser/tests/test_traversable.py
Log message for revision 66201:
Tag Five 1.3.3 yet again
Changed:
A Products.Five/tags/1.3.3/
-=-
Copied: Products.Five/tags/1.3.3 (from rev 66200, Products.Five/branches/1.3)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
Log message for revision 66212:
Merge philikon-fix-lookup-priorities branch and prepare for release.
Changed:
U Products.Five/branches/1.0/CHANGES.txt
U Products.Five/branches/1.0/fiveconfigure.py
U Products.Five/branches/1.0/tests/test_five.py
U
Log message for revision 66213:
Tag release
Changed:
A Products.Five/tags/1.2.2/
-=-
Copied: Products.Five/tags/1.2.2 (from rev 66212, Products.Five/branches/1.2)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
Log message for revision 66214:
fix indentation to bring this version closer to the one in Zope 2.8 branch
Changed:
U Products.Five/branches/1.0/tests/test_five.py
-=-
Modified: Products.Five/branches/1.0/tests/test_five.py
Log message for revision 66215:
Last and final release of Five 1.0.x.
Changed:
A Products.Five/tags/1.0.3/
-=-
Copied: Products.Five/tags/1.0.3 (from rev 66214, Products.Five/branches/1.0)
___
Zope-Checkins maillist - Zope-Checkins@zope.org
Tres Seaver wrote:
Philipp von Weitershausen wrote:
Log message for revision 66185:
update to latest revision of ZODB 3.6 for upcoming release
Should'nt we be tagging a ZODB release for this? I *really* don't like
the practice of releasing a product which has non-tagged dependencies
Log message for revision 66158:
try and improve the UI of the view listing a bit by mangling file names
a bit and displaying a table.
Changed:
U Products.Five/branches/philikon-local-components/component/browser.py
U
Log message for revision 66159:
Remove lots zope.app.zapi and some zope.app.i18n usage.
Note: some resource code seems not to have been tested because they
were still using getView and not getMultiAdapter
Note 2: formlib was using 'zope' i18n domain but zope.formlib code
uses
Andreas Jung wrote:
As announced earlier I plan to release Zope 2.8.7 and 2.9.2 by
next Monday...so as always: any pending fixes should be commited
until Monday.
Can we have a Zope 3.2.1 along with Zope 2.9.2? There are a few bugfixes
on the Zope 3.2 branch (e.g. involving widgets, formlib,
Chris Withers wrote:
I've started seeing warnings like this with an instance I'm moving from
Zope 2.7 to 2.9:
C:\Zope\2.9.1\lib\python\OFS\subscribers.py:74: DeprecationWarning:
Products.CookieCrumbler.CookieCrumbler.CookieCrumbler.manage_afterAdd is
deprecated and will be removed in Zope
Hi there,
Zope 3 has the concept of a default layer. This is a request interface
that most skins derive from. It is also the default request interface
that browser views are registered for if they don't specify another one
using the 'layer' argument.
Zope 3 also has the concept of a default
Lennart Regebro wrote:
I would propose to remove the Five hack and properly set the default
skin right after the request has been created. This would be in
ZPublisher.Publish.publish_module_standard.
That's probably a good idea.
Althoug, wasn't somebody going to try replacing the whole
Dieter Maurer wrote:
Chris McDonough wrote at 2006-3-13 10:21 -0500:
... silly id restrictions ...
Here's my current monkeypatch to Zope to unrestrict a good number of
characters:
def patch_objectmanager_badid():
Causes Zope to be less restrictive in the set of characters it
Log message for revision 65918:
update install docs
Changed:
U Products.Five/trunk/INSTALL.txt
-=-
Modified: Products.Five/trunk/INSTALL.txt
===
--- Products.Five/trunk/INSTALL.txt 2006-03-12 10:54:38 UTC (rev 65917)
Log message for revision 65924:
Backport jinty's r41392:
Have test.py remove iself from the pythonpath.
Changed:
U Zope/branches/2.9/test.py
-=-
Modified: Zope/branches/2.9/test.py
===
--- Zope/branches/2.9/test.py
yuppie wrote:
In Zope 3 the NameChooser makes sure you can't use content IDs starting
with '+' or '@'.
Zope 2 doesn't allow '+' in content IDs (actually the error message says
the ID contains characters illegal in URLs), but you can use content IDs
like '@@edit.html'. If the lookup order is
Chris McDonough wrote:
and should be fixed in Zope 2.8, 2.9 and trunk.
We'd be changing Zope 2's behaviour (not fixing a Five bug), I would
therefore vote for making this change on the Zope 2 trunk only.
I'd be apt to not further restrict the set of identifiers an OFS content
object can
Log message for revision 65856:
Branch for some minor modifications to Zope 2 regarding the work on local
component registration. They're minor, but break Five tests, hence the
branch.
Changed:
A Zope/branches/philikon-local-components/
-=-
Copied:
Log message for revision 65857:
Switch some essential zope.* packages to Jim's adapter branch
Changed:
_U Zope/branches/philikon-local-components/lib/python/zope/
-=-
Property changes on: Zope/branches/philikon-local-components/lib/python/zope
Log message for revision 65858:
Switch included Five to local component branch so people can check it out
more easily.
Changed:
_U Zope/branches/philikon-local-components/lib/python/Products/
-=-
Property changes on: Zope/branches/philikon-local-components/lib/python/Products
Log message for revision 65859:
Make ObjectManager an IPossibleSite.
Changed:
U Zope/branches/philikon-local-components/lib/python/OFS/ObjectManager.py
U Zope/branches/philikon-local-components/lib/python/OFS/interfaces.py
-=-
Modified:
Log message for revision 65824:
Make the marking of five methods nicer by using a descriptor.
Also, make some relative imports absolute ones. Death to absolute imports! (at
least the way they currently exist in Python)
Changed:
U
Log message for revision 65825:
Make template source listing look a little bit like CMF one for filesystem
based pagetemplates
Changed:
U
Products.Five/branches/philikon-local-components/component/customizetemplate.pt
-=-
Modified:
Log message for revision 65804:
Missing imoprts
Changed:
U Products.Five/branches/philikon-local-components/site/localsite.py
-=-
Modified: Products.Five/branches/philikon-local-components/site/localsite.py
===
---
Log message for revision 65805:
Fix tests by making dummy site implement nothing from its baseclasses.
That way the five:localsite directive won't be confused about it already
being an IPossibleSite (which ObjectManager will be).
Changed:
U
Log message for revision 65807:
small cleanup
Changed:
U Products.Five/branches/philikon-local-components/component/component.txt
-=-
Modified:
Products.Five/branches/philikon-local-components/component/component.txt
===
Log message for revision 65808:
Rename doctest file. It's not really a general local component test but
specific to customizing zpt views.
Changed:
D Products.Five/branches/philikon-local-components/component/component.txt
U
Log message for revision 65809:
Move test for the siteManagerAdapter out to Five.component (now a doctest in
component.txt).
Also clean up the test fixtures in test_localsite, based on the fact that
ObjectManager
is an IPossibleSite now.
Changed:
A
Log message for revision 65810:
Make tests pass by loading some necessary configuration that was moved to
Five.component.
Changed:
U
Products.Five/branches/philikon-local-components/site/tests/test_localsite.py
U
Log message for revision 65812:
set Id expansion keyword
Changed:
_U Products.Five/branches/philikon-local-components/component/interfaces.py
-=-
Property changes on:
Products.Five/branches/philikon-local-components/component/interfaces.py
Log message for revision 65813:
Refactoring: Make browser.py smaller:
Move local-ZPT logic out to zpt.py (we still could do more)
Move findSite out to __init__.py and make the siteManagerAdapter use it.
Changed:
U Products.Five/branches/philikon-local-components/component/__init__.py
Log message for revision 65815:
fux big (SyntaxError)
Changed:
U Products.Five/branches/philikon-local-components/component/tests.py
-=-
Modified: Products.Five/branches/philikon-local-components/component/tests.py
===
---
Log message for revision 65741:
Move site manager adapter and subscriber configuration (IOW, the useful stuff
in Five.site) to Five.component.
Changed:
U Products.Five/branches/philikon-local-components/component/__init__.py
U
Log message for revision 65742:
Oh, and yeah, include Five.component config
Changed:
U Products.Five/branches/philikon-local-components/configure.zcml
-=-
Modified: Products.Five/branches/philikon-local-components/configure.zcml
Log message for revision 65744:
update imports
use @adapter, @implementer instead of specifying interfaces in ZCML
Changed:
UU Products.Five/branches/philikon-local-components/component/__init__.py
U Products.Five/branches/philikon-local-components/component/configure.zcml
-=-
Stefane Fermigier wrote:
I think that the idea of giving Zed its own, distinct identity is great.
I think it is stupid.
We (Zope Corp + the Zope Community) have spent 8 years building the Zope
brand, and you want to restart from scratch ?
Good point. There's the question: Does this zed
Stefane Fermigier wrote:
Strange how (most of) the Plone people seem to be so quick in willing to
sacrifice the Zope brand :(
It's not about sacrificing the Zope-the-app-server brand. It's actually
about growing it in the sense that it becomes much clearer WHAT THE HELL
Zope actually is. Or can
Benji York wrote:
Good point. There's the question: Does this zed thing need a different
name at all? If we want other people to pick it up, then it seems like a
good idea to distinguish it from Zope-the-app-server. Paul seems to
suggest that in his response.
How about zopelib?
If we want
Log message for revision 65675:
i renamed the view name last night
Changed:
U Products.Five/branches/philikon-local-components/component/component.txt
-=-
Modified:
Products.Five/branches/philikon-local-components/component/component.txt
Log message for revision 65676:
More catching up with the renaming
Changed:
U Products.Five/branches/philikon-local-components/component/component.txt
U
Products.Five/branches/philikon-local-components/component/customizetemplate.pt
-=-
Modified:
Log message for revision 65677:
rename variable obj - site
don't reacquire the zpt object
Changed:
U Products.Five/branches/philikon-local-components/component/browser.py
-=-
Modified: Products.Five/branches/philikon-local-components/component/browser.py
Log message for revision 65682:
Use Products.PageTemplates.ZopePageTemplate instead of
zope.app.zptpage.ZPTPage
because the things we put in an ObjectManager really need to be SimpleItems
(grrr).
Slightly refactored the view factory (local function instead of class).
Also introduced a
Log message for revision 65688:
get the template top-level variable namespace right and test it.
improve some of the explanations in the doctest.
Changed:
UU Products.Five/branches/philikon-local-components/component/browser.py
U
Log message for revision 65689:
expand the id keyword
Changed:
_U Products.Five/branches/philikon-local-components/component/tests.py
-=-
Property changes on:
Products.Five/branches/philikon-local-components/component/tests.py
Log message for revision 65693:
Take the original view class for the 'view' object. In order to find it, we
look for it at the global level (which might not be enough in the future). For
this to work we also need to remember its view name.
Changed:
U
Log message for revision 65694:
Remind myself that we're not doing everything we might have to yet.
Changed:
U Products.Five/branches/philikon-local-components/component/browser.py
-=-
Modified: Products.Five/branches/philikon-local-components/component/browser.py
Log message for revision 65701:
One action is enough.
Changed:
U
Products.Five/branches/philikon-local-components/component/customizetemplate.pt
-=-
Modified:
Products.Five/branches/philikon-local-components/component/customizetemplate.pt
Log message for revision 65703:
ugh, wrong base classes
Changed:
U Products.Five/branches/philikon-local-components/component/browser.py
-=-
Modified: Products.Five/branches/philikon-local-components/component/browser.py
Log message for revision 65715:
Use the Zope2 TALES engine to support Zope2-compatible TALES traversal.
If that is going to go away, then this will have to be done differently,
but at least this fixes several issues where the z3-style PageTemplate
implementation didn't do everything that
Log message for revision 65584:
Branch off Five 1.4. We're not releasing Five 1.4b yet, but we need a Five
branch that is geared towards Zope trunk (=Zope 2.10).
Rocky should merge his work only to the Five 1.4 branch. Five 1.4 is geared
towards Zope 2.9.
Changed:
A
Log message for revision 65631:
New approach to local components in Zope 2, based on Jim's new component
registration
in the jim-adapter branch of Zope 3.
Five.component.browser actually features a CustomizationView which lets you
walk up
to an object, view a list of template-based
Log message for revision 65656:
Use _setObject which actually adds the object to the items list of the
container.
We probably still need to fix up the ZPT class so that it provides the correct
manage_* junk (which essentially means creating a subclass with a bunch of
mix-ins).
Log message for revision 65659:
correct ZCML info object API
Changed:
U
Products.Five/branches/philikon-local-components/component/templateviews.pt
-=-
Modified:
Products.Five/branches/philikon-local-components/component/templateviews.pt
Stephan Richter wrote:
1) Our current vision (AFAIK) is that Zope 3 will eventually
replace Zope 2
2) In an alternate vision, Zope 2 evolves to Zope 5.
As you probably know already, I am -1 on the second proposal, since it will
disallow us to finally get rid of the old Zope 2 code.
Martijn Faassen wrote:
I will also note that just because Zope 2 won't die, it doesn't mean we
shouldn't clean it up. Eventually, Zope should mostly be reusing things
from Zed.
+sys.maxint
I think this will be the way we get a real forward migration path for an
awful lot of us who are
Martijn Faassen wrote:
I see Zope 5 being a combination of Zope 2 and Zope 3, keeping
the best of both.
I think we already have Zope 5, and it's called Zope 2.9.
I'd rather say it's called Zope 2.15 or something :).
Philipp
___
Zope-Dev maillist
Lennart Regebro wrote:
-if name[0] == '_':
+if name.startswith('_'):
Just a question: Is this only a matter of stylistic changes, or is
there some, like, speedup involved?
In general, using str.startswith and str.endswith is a failsafe because
Martijn Faassen wrote:
I think focusing on one app server and a dedicated set of libraries
would be a good alternative to two concurring app servers.
...if the single app server is based on acquisition,
__bobo_traverse__ and friends, objectValues and friends, ZCatalog,
and so on, I'd
Jim Fulton wrote:
2) In an alternate vision, Zope 2 evolves to Zope 5.
+1 as already discussed at PyCON.
- Zope 5 will be the application server generally known as Zope. It
will be backward compatible (to the same degree that Zope 2
releases are currently backward compatible
Log message for revision 65500:
New repository lcoation
Changed:
U Products.Five/trunk/doc/main.txt
-=-
Modified: Products.Five/trunk/doc/main.txt
===
--- Products.Five/trunk/doc/main.txt2006-02-26 20:45:08 UTC (rev
Hi all,
thanks to Jens we successfully moved the Five source code and all of its
history to svn.zope.org. It now lives at svn.zope.org/Products.Five/.
Zope 2.9 and the trunk use svn:externals to stitch in Five from the
1.3.2 tag. I didn't bother to update the 2.8 branch.
Note that we now use the
Philipp von Weitershausen wrote:
Hi all,
thanks to Jens we successfully moved the Five source code and all of its
history to svn.zope.org. It now lives at svn.zope.org/Products.Five/.
Zope 2.9 and the trunk use svn:externals to stitch in Five from the
1.3.2 tag. I didn't bother to update
The Five team is happy to announce two bugfixes releases of Five
today, Five 1.2.1 and 1.3.2!
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
Zope 3 interfaces, ZCML-based configuration,
Log message for revision 65452:
Codespeak conventions - svn.zope.org conventions.
Changed:
D Products.Five/branch/
A Products.Five/branches/
-=-
Copied: Products.Five/branches (from rev 65451, Products.Five/branch)
___
Zope-Checkins
Log message for revision 65453:
Codespeak conventions - svn.zope.org conventions.
Changed:
D Products.Five/tag/
A Products.Five/tags/
-=-
Copied: Products.Five/tags (from rev 65452, Products.Five/tag)
___
Zope-Checkins maillist -
Log message for revision 65458:
Backport r22056 from Five's former trunk at codespeak.net:
Unit tests that did i18n via Localizer would fail because the request
attribute that keeps Localizers list of preferred languages did not exist.
Changed:
U
Log message for revision 65459:
Prepare for release
Changed:
U Products.Five/branches/Five-1.2/CHANGES.txt
U Products.Five/branches/Five-1.2/version.txt
-=-
Modified: Products.Five/branches/Five-1.2/CHANGES.txt
===
---
Log message for revision 65460:
prepare for release
Changed:
U Products.Five/branches/Five-1.3/CHANGES.txt
U Products.Five/branches/Five-1.3/version.txt
-=-
Modified: Products.Five/branches/Five-1.3/CHANGES.txt
===
---
Log message for revision 65461:
Minor license header cleanup
Changed:
UU Products.Five/trunk/formlib/formbase.py
UU Products.Five/trunk/formlib/tests/content.py
UU Products.Five/trunk/formlib/tests/test_formlib.py
UU Products.Five/trunk/formlib/tests/view.py
-=-
Modified:
Log message for revision 65463:
Shorter branch naming.
Changed:
A Products.Five/branches/0.1/
A Products.Five/branches/0.2/
A Products.Five/branches/1.0/
A Products.Five/branches/1.1/
A Products.Five/branches/1.2/
A Products.Five/branches/1.3/
D
Log message for revision 65467:
Small change item reordering
Changed:
U Products.Five/trunk/CHANGES.txt
-=-
Modified: Products.Five/trunk/CHANGES.txt
===
--- Products.Five/trunk/CHANGES.txt 2006-02-25 20:10:55 UTC (rev
Log message for revision 65473:
Stitch in Five via svn:externals
Changed:
_U Zope/branches/2.9/lib/python/Products/
-=-
Property changes on: Zope/branches/2.9/lib/python/Products
___
Name: svn:externals
-
+ Five
Log message for revision 65474:
Prepare to stitch in Five via svn:externals.
Changed:
D Zope/trunk/lib/python/Products/Five/
-=-
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
Log message for revision 41768:
Branch for deprecating Zope 2 interfaces.
Changed:
A Zope/branches/philikon-deprecate-interfaces/
-=-
Copied: Zope/branches/philikon-deprecate-interfaces (from rev 41767, Zope/trunk)
___
Zope-Checkins maillist
Chris Withers wrote:
yuppie wrote:
Philipp von Weitershausen wrote:
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
+10
Me too ;-)
Great. There don't seem
Andrew Milton wrote:
+---[ Philipp von Weitershausen ]--
| Andrew Milton wrote:
| +---[ Stephan Richter ]--
| | Hello everyone,
| |
| | With the development of Zope 3, the Zope developers committed to a new
| | development process
Hi there,
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
There are a few places in Zope 2 where they are still used for checks
(mostly webdav, OFS, ZCTextIndex). For the
Andrew Milton wrote:
+---[ Philipp von Weitershausen ]--
|
| Handing over ownership to the ZF and therefore having signed a
| Contributor Agreement are the terms of the svn.zope.org repository, just
| like that code is to be made ZPL.
The license part is irrelevant
yuppie wrote:
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
+10
But we can't deprecate z2 interfaces as long as Zope 2 itself uses them
for other tasks than
Andrew Milton wrote:
+---[ Philipp von Weitershausen ]--
| Andrew Milton wrote:
| +---[ Stephan Richter ]--
| | Hello everyone,
| |
| | With the development of Zope 3, the Zope developers committed to a new
| | development process
Andrew Milton wrote:
+---[ Philipp von Weitershausen ]--
|
| Handing over ownership to the ZF and therefore having signed a
| Contributor Agreement are the terms of the svn.zope.org repository, just
| like that code is to be made ZPL.
The license part is irrelevant
Andrew Milton wrote:
+---[ Philipp von Weitershausen ]--
|
| | * putting a project/package under the wings of the ZF ensures long-term
| | IP protection
|
| How? I think my death + 70 years is further away than the death of ZF, or
in
| fact the death of Zope
Andrew Milton wrote:
+---[ Stephan Richter ]--
| Hello everyone,
|
| With the development of Zope 3, the Zope developers committed to a new
| development process and higher software quality guidelines. With the
adoption
| of Zope 3 technologies in the wider Zope
Chris Withers wrote:
Philipp von Weitershausen wrote:
Chris Withers wrote:
[aside... hmmm, crossposting, maybe time to merge zope-dev and
zope3-dev? most stuff seems to be relevent to both nowadays]
+10
You know, I once had a proposal. Uh, never mind :)
Well, what needs to happen
Chris Withers wrote:
[aside... hmmm, crossposting, maybe time to merge zope-dev and
zope3-dev? most stuff seems to be relevent to both nowadays]
+10
You know, I once had a proposal. Uh, never mind :)
In Zope 3, we went with a more explicit installation mechanism,
in which people had to
Hi all,
the cross-repository merging between Zope 2 and Five has become a pain,
especially as Five is now a big element in Zope 2 development. Since
Five is ZPL and part of the Zope repository tree already, we would like
to take another, final step now and move its complete source code
control to
Jim Fulton wrote:
Some recent discussions on the distutils-sig mailing list have
helped me to understand some issues related to the ways we
extend the Zope application server. Traditionally, in Zope 2,
you extended Zope by dropping product packages into a special
Products package. This was
601 - 700 of 870 matches
Mail list logo
