Malthe Borch wrote:
Log message for revision 94141:
Preparing release.
Changed:
U cmf.pt/trunk/CHANGES.txt
U cmf.pt/trunk/setup.py
-=-
Modified: cmf.pt/trunk/CHANGES.txt
===
--- cmf.pt/trunk/CHANGES.txt
Hanno Schlichting wrote:
Benji York wrote:
On Fri, Nov 14, 2008 at 7:23 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
Log message for revision 92953:
Copied over the UtilityTerm and UtilityVocabulary implementation from
zope.app.component to avoid a dependency.
Instead of duplicating the
Jens Vagelpohl wrote:
On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote:
If I'm not mistaken there was something about every release being
supported two years after its initial release in those discussions.
But time went on, we haven't sticked to a time-based release schedule
and those
Rudá Porto Filgueiras wrote:
I found a typo bug in zc.relationship 1.0.2 (pypi and svn tag 1.02).
It's fixed in trunk but not backported and plone.app.relations-1.0b2
unittest found this bug.
Thanks for the bug report and the patch. Could you please report it at
Andreas Jung wrote:
On 19.10.2008 14:14 Uhr, Andreas Jung wrote:
On 19.10.2008 14:04 Uhr, Roger Ineichen wrote:
Hi Andreas
Betreff: [Zope-dev] zope.app.container won't compile
A buildout fails reproducable both on Mac and Linux...how is
the guilty?
Same on windows with Python 2.4.
I
kevin gill wrote:
I need a little help. I checked two packages into svn.zope.org, but I have
set up the hierarchy incorrectly.
The packages are z3c.rotterdam and z3c.boston. The egg is in the base
folder, rather than in 'trunk'.
I would appreciate it if someone with administration access
Andreas Jung wrote:
A trunk checkout compiles cleanly on Python 2.4: Sidnei checked in a
fix for this problem on Thursday.
I assume this made it into zope.app.container 3.6.1 released on October
15th:
http://pypi.python.org/pypi/zope.app.container
So why won't this version build with
El 17 Oct 2008, a las 10:37 , Christian Theune escribió:
There is a process that actually needs the request and this process
is
what I call traversal: breaking down a URL and finding a publishable
object. zope.traversing has (almost) nothing to do with it, the real
kind of traversal happens
El 17 Oct 2008, a las 15:02 , Jim Fulton escribió:
First of all, its name is quite misleading. It should really be
called
'zope.resolvepath' because it resolves TALES-like object paths. In
fact,
it's pretty much only used by the PageTemplate machinery to hook it
up
to the TALES
Hanno Schlichting wrote:
Stephan Richter wrote:
On Wednesday 15 October 2008, Sidnei da Silva wrote:
I don't want to rain on your parade, but I already did a first pass at
reviewing the changes in Python 2.5 and Python 2.6. There are no
significant changes that I could spot so far. Apparently
Christian Theune wrote:
we stumbled over an annoyance that took a while to debug:
Writing an ITraversable, we used zope.traversing.api.traverse() in a
test to verify our code. We registered the ITraversable as an
(non-multi) adapter and ended up with a working test.
In the actual system,
Thomas Lotze wrote:
Jim Fulton [EMAIL PROTECTED] wrote:
I would change it to just use getattr rather than hasattr.
try:
getattr(ob, name)
except AttributeError:
return False
...
This doesn't handle the case that the attribute exists as a property
but raises an AttributeError
El 15 Oct 2008, a las 19:24 , Shane Hathaway escribió:
Philipp von Weitershausen wrote:
First of all, its name is quite misleading. It should really be
called
'zope.resolvepath' because it resolves TALES-like object paths. In
fact,
it's pretty much only used by the PageTemplate machinery
Encolpe Degoute wrote:
Dieter Maurer a écrit :
Garito wrote at 2008-10-8 14:22 +0200:
I'm agree with you, Tino. Plone has a lot of ugly features (as KSS, for
instance)
Why is KSS ugly?
Reading the documentation, I found it quite attractive
That is what KSS opponents atr thinking:
[EMAIL PROTECTED] wrote:
We're contemplating the move of our Zope 2.x application to 64-bit Windows.
We rely on a few add-on packages, notably PyWin, which has 64-bit support for
Py 2.6 only.
I'd be grateful for a rough idea on when there could be a Zope 2.x release
working with Python 2.6
Marius Gedminas wrote:
On Wed, Oct 08, 2008 at 12:35:39AM -0300, Sidnei da Silva wrote:
Trying to run some tests with Python 2.6 I stumbled on a problem that
I need help with: an interface that has an attribute named 'with'.
The interface in question is defined in zope.app.component.back35:
El 8 Oct 2008, a las 14:23 , Sidnei da Silva escribió:
On Wed, Oct 8, 2008 at 8:53 AM, Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
Sidnei da Silva wrote:
I'm trying to fix some import errors, which seem to be related to
PEP-328.
I'm fixing those errors this way, though I don't
Sidnei da Silva wrote:
I'm trying to fix some import errors, which seem to be related to PEP-328.
I'm fixing those errors this way, though I don't know if that's the
recommended way of fixing it. Thoughts?
try:
from DT_Util import parse_params, name_param
except ImportError:
#
Marius Gedminas wrote:
On Wed, Sep 17, 2008 at 12:52:49PM -0400, Tres Seaver wrote:
Proposal
Instead, what I *am* proposing is adding metadata which allows consumers
of such packages to verify that the package is downloaded / installed
correctly. In particular, I want for the
El 9 Sep 2008, a las 20:37 , Dieter Maurer escribió:
Chris Withers wrote at 2008-9-8 18:34 +0100:
...
There's the backward-compatibility issue, which is a showstopper.
There's plenty of code that does this:
adapter = package.interfaces.IFoo(object, None)
Changing the signature as you
Benji York wrote:
On Wed, Sep 3, 2008 at 11:41 AM, Stephan Richter
[EMAIL PROTECTED] wrote:
For several packages we took the following approach. Most packages that have
browser packages are in zope.app; for example, zope.app.folder (we did not
convert this package yet). We then took the API
El 30 Aug 2008, a las 07:50 , Dieter Maurer escribió:
Chris Withers wrote at 2008-8-29 10:25 +0100:
Dieter Maurer wrote:
Then, we could get rid of the {get|query}[Multi]Adapter altogether
and consistently use I() with appropriate optional
parameters --
what a simplification and
El 1 Sep 2008, a las 17:23 , Chris Withers escribió:
Philipp von Weitershausen wrote:
I've personally thought for some time that it would be quite nice
if all you had to do was call an interface to look up a utility
(which is sort of a multi-adapter of order 0) or to do some kind
El 1 Sep 2008, a las 19:26 , Dieter Maurer escribió:
Chris Withers wrote at 2008-9-1 16:23 +0100:
...
auth = IAuthentication() # utility
auth = IAuthentication(default=None)
langs = IUserPreferredLanguages(request) # adapter
langs =
Chris Withers wrote:
I'm just starting to play with zope.testbrowser's testing.Browser but I
notice that is uses the following packages:
transaction
zope.app.testing
zope.app.folder
zope.app.component
...but zope.testbrowser doesn't declare any dependency on these.
It does, using the
Chris Withers wrote:
Why does the egg in the subject line exist
Because somebody made it and uploaded it to download.zope.org. It
probably happened during the initial eggification period when we didn't
have a solid release process [1].
and why does buildout pick it over a stable release?
Chris Withers wrote:
Okay,
So I bumped into the ZODB3 3.9.0-dev-r77011 problem while trying to get
going with zopeproject.
zopeproject created a buildout.cfg in my test project, so I thought I'd
lock ZODB to 3.8.0 to prevent problems:
[buildout]
develop = .
parts = app test
El 19 Aug 2008, a las 12:05 , Chris Withers escribió:
Philipp von Weitershausen wrote:
and why does buildout pick it over a stable release?
Because buildout, like easy_install, will pick the newest available
version for a distribution. Fortunately, buildout has a prefer-
stable option so
Shane Hathaway wrote:
Chris Withers wrote:
From a user's perspective, this makes no sense:
from zope.interface import implements,Interface
from zope.component import queryAdapter
class ISomething(Interface): pass
...
class MyClass: implements(ISomething)
...
m = MyClass()
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Fri Aug 15 11:00:00 2008 UTC to Sat Aug 16 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Unknown
---
Subject: UNKNOWN :
Log message for revision 89760:
Merge Maurits's r89745 as well: Proper English spelling of cannot.
Changed:
U Zope/trunk/lib/python/Products/PythonScripts/PythonScript.py
-=-
Modified: Zope/trunk/lib/python/Products/PythonScripts/PythonScript.py
Thomas Lotze wrote:
zope.app.form items edit widgets don't provide the no value value if
the corresponding field is required. While this prevents invalid input, it
means that e.g. a drop-down box may then have one of the valid values
pre-selected. If user forgets to change that value, he could
Garito wrote:
Could someone point me where the page template code decide if an
expression is a path expression or a string or python one, please?
I'm studying the zope page template classes and I would like to
understand where this decision is taken
Garito wrote:
Use:
/path/to/the/object/with/${some/magic/variables}/to/solve/some/paths/in/a/simplest/way
Path expressions already support this.
tal:define=pathel some/magic/variables;
objpath/to/the/object/with/?pathel/to/solve/some/...
So basically in TALES path
Garito wrote:
Considere this case:
I have the sking value in the variable at args/Yanged/Skin
How can I do the equivalent to
args/Yanged/raiz/Skins/${args/Yanged/Skin}/arbolYanged.css/absolute_url
?
In the python way it will be:
path(path('string:' +
Garito wrote:
Finally it's possible to do what I need without the need to declare any
variable?
Not that I know of.
If not my change will be 4-6 lines of code and it's ok for me to make
this change
I only need to understand were the code decides if the expression is
standard, string
When relying on a third-party package with ZCML configuration, it is
sometimes desirable to disable certain directives, for instance when the
third-party package defines an event subscriber that you'd like to
disable. This is now possible with z3c.unconfigure.
While zope.configuration (the
Wichert Akkerman wrote:
I've re-tagged and reuploaded new versions zope.app.container 3.5.6 and
zope.app.authentication 3.4.3. This should be ok.
Re-uploading is very problematic: if anyone has the previous version in
their buildout download cache they will never get the new version. I
prefer
Marius Gedminas wrote:
On Tue, Aug 05, 2008 at 10:36:30PM +0100, Martin Aspeli wrote:
Subscribers and subscription adapters are particularly bad in this way,
since they are unnamed and thus can't be overridden, only amended to.
We've talked about an off switch for ZCML before. Given that we
El 6 Aug 2008, a las 16:47 , Stephan Richter escribió:
On Wednesday 06 August 2008, Philipp von Weitershausen wrote:
I'm working on a package for this functionality in z3c.unconfigure
right
now. Name inspired by Martin's suggestion above; my original
prototype
used had a different name
El 6 Aug 2008, a las 17:17 , Roger Ineichen escribió:
I'm +1 on zc.configuration.
z3c.unconfigure, however, will contain zope.component
specific code to unconfigure subscribers (which currently
have no useful discriminator). So it's a hack to make it work
with existing Zope code out there. If
Chris Withers wrote:
Nikolay Kim wrote:
you can create utility in python file and then use component=
for example utility.py:
class Utility(object):
pass
myUtility = Utility()
configure.zcml:
utility name=myUtility component=.utility.myUtility /
I'm aware of this but it kind of
Chris Withers wrote:
Nikolay Kim wrote:
I'm aware of this but it kind of defeats the idea of seperating code
and configuration...
So, other ideas?
create new zcml directive.
That seems pretty heavyweight :-/
It's not. It's in fact relatively easy to write a custom utility
directive
Tres Seaver wrote:
Log message for revision 89399:
Pin / fix up dependencies based on comparison with monolith.
Thanks for picking this up!
I do, however, strongly object to pinning versions of dependencies in
setup.py like this. What's the point of eggifying Zope 2 in the first
place
El 2 Aug 2008, a las 17:45 , Chris Withers escribió:
Benji York wrote:
In case anybody's wondering how this complies with our no removal
of any
release whatsoever policy [1], be assured that a 3.4dev-r73090
thing isn't
a release by our standards. This version number not only contains
the
Christophe Combelles wrote:
could someone remove this package from the PyPI :
http://pypi.python.org/pypi/zope.size/3.4dev-r73090
This is an empty development version, considered more recent by PyPI
than the latest released version 3.4.0. (which is r78211)
Done.
In case anybody's wondering
Christophe Combelles wrote:
Stephan Richter a écrit :
On Friday 01 August 2008, Christophe Combelles wrote:
Did you miss the CHANGES.txt in zope.release ? We have two histories
now.
Nope, but that file tracks the package -- source code -- changes of
zope.release.
I wanted a separate file
Shane Hathaway wrote:
Marius Gedminas wrote:
I think I'll run the test suite again on a 64-bit Linux machine, for
extra fun. And maybe do that for Python 2.4 as well.
zope.proxy and related modules failed badly under 64 bit Python 2.5
until I fixed the C code on the trunk 2 weeks ago,
Wichert Akkerman wrote:
Stephan Richter wrote:
On Wednesday 23 July 2008, Wichert Akkerman wrote:
If there are no objections I intend to merge the branch to trunk in a
few days
I am uncomfortable with the way you approached this. I think there are at
least two other possibilities
I would like to remind everyone that when you do refactorings and move
code around, to please use 'svn mv' or 'svn cp'. For instance, when you
split a large file into two smaller ones, use 'svn cp' to create the
second file and then remove stuff from it that doesn't go there. That
way, version
Chris Withers wrote:
Hi All,
Just me, or is it excessive that we have:
http://mail.zope.org/pipermail/zope3-checkins/
This one is obsolete now.
http://mail.zope.org/pipermail/zope-checkins/
This one is for Zope 2 only.
http://mail.zope.org/pipermail/checkins/
This one covers the
Tres Seaver wrote:
Mark Hammond wrote:
Well, Zope moved onwards from PAS to PAU
I doubt that seriously: I would venture that there are two orders of
magnitude more users of PAS than PAU in production deployments. PAU was
an attempt to port the PAS to a component-centric implementation, but
Stephan Richter wrote:
Hi everyone,
I just tried to create a catalog for an annotation and noticed that it does
not get filled. Digging around in the zope.annotation package, I noticed that
the zope.annotation package does not send out any object events. This
sucks. ;-)
Thus I propose:
-
Stephan Richter wrote:
On Tuesday 15 July 2008, Fred Drake wrote:
On Tue, Jul 15, 2008 at 12:30 PM, Stephan Richter
[EMAIL PROTECTED] wrote:
Thus I propose:
- Add ObjectCreatedEvent event notification to zope.annotation factory
call.
By this, I presume you mean the stuff in
Jeff McNeil wrote:
That's not all that obvious to someone new to the Zope system. Most
of the documentation I've found is geared towards the 2.x branch. As
Zope 3 and Zope 2 are different animals, I wouldn't think that the
deployment steps and recommendations would be all that similar.
With
Paul Winkler wrote:
On Sun, Jul 13, 2008 at 01:20:53PM -0400, Philipp von Weitershausen wrote:
Jeff McNeil wrote:
I'd love to be able to just drop an egg on the file system and tell
Zope Here, go load that one now via configuration alone.
You could also write your own ZCML directive
Hermann Himmelbauer wrote:
And there's once again this mingw32 problem.
4) Next, I tried zopeproject:
$ easy_install zopeproject
$ zopeproject HelloWorld
First, zopeproject does not install the packages into the Python
site-packages,
That's *intended*. That's, in fact, much better than
Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU with
Plone's PAS and further enable (non-AT) content objects as source for users and
groups. All functionality is developed in pure zope3, the plone
Wichert Akkerman wrote:
Previously Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU with
Plone's PAS and further enable (non-AT) content objects as source for users
KLEIN Stéphane wrote:
I wonder why class constructor is never in apidoc ?
Because nobody has bothered to implement this feature. Patches are
welcome :)
Are there something in OOP concept I haven't understand ?
I don't know what you mean with this.
El 21 Jun 2008, a las 20:15 , Chris Withers escribió:
Philipp von Weitershausen wrote:
This isn't a matter of a binary zope.proxy egg. If you look at the
'zope2' part of your buildout.cfg, you'll see it's actually trying
to compile Zope 2 itself (which happens to contain the zope.proxy
Martin Aspeli wrote:
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer,
currently getting this:
creating zope.proxy
copying zope/proxy\proxy.h - zope.proxy
error: Python was built with Visual Studio 2003;
extensions must be built with a compiler
Martijn Faassen wrote:
One question is what to do for persistent registrations in local sites.
I don't imagine they're used a lot, but it'd mean a content upgrade to
re-register them, right?
The only piece of software that, to my knowledge, can actually *make*
local view registrations is
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer,
currently getting this:
creating zope.proxy
copying zope/proxy\proxy.h - zope.proxy
error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate
David Glick wrote:
On Jun 18, 2008, at 1:44 PM, Malthe Borch wrote:
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
Jim Fulton wrote:
On Jun 18, 2008, at 4:31 PM, Malthe Borch wrote:
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).
Right. This is a historical
Malthe Borch wrote:
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*.
Jeff Kowalczyk wrote:
I was going to ask this question anyway, but perhaps it's more timely with
the scheduled server move:
Has anyone made a git clone of svn://svn.zope.org/repos/main suitable for
public mirroring on github, etc.?
Not that I know of, but there's a read-only SVN mirror:
Marco Bizzarri wrote:
Hi all.
Apologies in advance if my question has a somewhat obvious answer.
I'm working on a Zope application, developed as a python product.
I've ZTC in place for this application. While I run all the ZTC, I can
see python process size growing. Can I use this as an
These failures are due to recent changes to zope.tal (3.5.0) in which
the TAL interpreter no longer emits a trailing newline character (and
thus finally complies with its own spec).
I've fixed this on the zope.pagetemplate trunk now.
[EMAIL PROTECTED] wrote:
The Buildbot has detected a new
zope.app.twisted was missing a test dependency (zope.testbrowser) for a
level 2 test. Fixed now.
[EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of zope.app.twisted on Zope.
Full details are available at:
http://zopebuildbot.whq.gocept.com/zope.app.twisted/builds/97
Here, the same thing as with zope.pagetemplate happened. zope.tal no
longer emits a trailing newline character. Fixed on the trunk.
[EMAIL PROTECTED] wrote:
The Buildbot has detected a new failure of zope.app.zptpage on Zope.
Full details are available at:
Shane Hathaway wrote:
Hi all,
I'm trying to get a handle on Zope 3. I plan to take a bunch of Zope 3
modules and combine them in a new way. The goal is to create for myself
a comfortable working environment that lets me run simple code in a
small mod_wsgi environment with easy reloading
Malthe Borch wrote:
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
On 2 Jun 2008, at 20:44 , Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2008-5-28 21:52 +0200:
Dieter Maurer wrote:
2008-05-24T09:31:32 ERROR Zope.SiteErrorLog http://myurl/error_log/manage_main
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module
Dieter Maurer wrote:
Giampiero Benvenuti wrote at 2008-5-24 11:47 +0200:
...
after the upgrade from zope2.9.7 to 2.10.6 i get this error in the
event log:
2008-05-24T09:31:32 ERROR Zope.SiteErrorLog http://myurl/error_log/manage_main
Traceback (innermost last):
Module ZPublisher.Publish,
Andreas Jung wrote:
Is there a complete documentation of the dtml-tree tag anywhere?
The dtml reference of the Zope book has the following for some options:
This attribute is for advanced usage only
Where can I find out about this 'advanced usage'?
Using DTML and related DTML tags is like
Believe something very very rotten in Five's registerPackage was fixed
by Rocky in r72986 [1]. As far as I can tell this was never merged to
the 1.4 branch, but I could we wrong.
[1] http://svn.zope.org/?rev=72986view=rev
Sasha Vincic wrote:
Forgot to say that this is Zope 2.9.8, Five 1.4
Tarek Ziadé wrote:
If nothing exists, I would like to suggest adding a setuptools
console entry point in zope.testing setup.py file, to get a python
script in the $PYTHON/bin folder, exactly like what
zc.recipe.testrunner does.
+1
It could be called zope.testrunner maybe ? (nose= nostests,
Roger Ineichen wrote:
Is there a reason why zope.publisher.interfaces.NotFound
is not locatable?
class NotFound(LookupError, TraversalException):
implements(INotFound)
def __init__(self, ob, name, request=None):
self.ob = ob
self.name = name
Why should a NotFound
Sebastian Wehrmann wrote:
the zope.i18nmessageid package has a broken link on
http://download.zope.org/zope3.4/zope.i18nmessageid/ . The
'zope.i18nmessageid-3.4.3-py2.4-linux-i686.egg' does not exist any more
on pypi.
Right. It was deliberately removed because binary eggs should never ever
Maurits van Rees wrote:
Without having tried pure Zope 3, only Grok --- I have been working on
grokproject during the Grokkerdam sprint --- the following in
buildout.cfg should work just as well:
find-links = http://download.zope.org/distribution/
extends =
Lennart Regebro wrote:
On Thu, Apr 24, 2008 at 10:07 PM, Jim Fulton [EMAIL PROTECTED] wrote:
- If a file is documentation and a test, make sure it is good
documentation. In that case, documentation comes first. Don't add so many
tests that it ruins the documentation.
- Test edge cases in
On 21 Apr 2008, at 11:53 , Martin Aspeli wrote:
- Projects gives an explanation of how the different Zope
projects fit
together (Zope 2, Zope 3, Grok, CMF, ZODB). Each is then given a
subfolder
that contains a standard structure: A front page that explains the
project
in more detail, Get
On 19 Apr 2008, at 22:39 , Chris McDonough wrote:
Philipp von Weitershausen wrote:
Chris McDonough wrote:
I wonder if Philipp would be amenable to writing a proposal on
this, and get Chris McDonough's input.
IMO, a Zope2 egg release should depend on the following packages:
- 'ZODB3
Chris McDonough wrote:
I wonder if Philipp would be amenable to writing a proposal on this,
and get Chris McDonough's input.
IMO, a Zope2 egg release should depend on the following packages:
- 'ZODB3' (already packaged)
- 'transaction' (depended on by newer ZODBs)
- 'ZConfig' (also depended
Martijn Faassen wrote:
Tres Seaver wrote:
[snip]
The second problem that might arise, is that the implicit assumption
that every object inside Zope 2 inherits from Acquisition base
classes no longer holds. Code that relies on the various aq_*
attributes to be there need to be adjusted to use
Log message for revision 85467:
Remember that Hanno's fix should probably be made in zope.app.pagetemplate.
Changed:
U
Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py
-=-
Modified:
Log message for revision 85468:
Improve doctest paragraph about calling templates that are instance variables.
Changed:
U
Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy.py
U
Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy.zcml
Tres Seaver wrote:
The second problem that might arise, is that the implicit assumption
that every object inside Zope 2 inherits from Acquisition base classes
no longer holds. Code that relies on the various aq_* attributes to be
there need to be adjusted to use the Acquisition methods
Hanno Schlichting wrote:
Timeline:
I would like to do the merge as soon as possible, so people can easily
test it against all their applications and report back problems.
Merging it into Zope trunk will get it into the Zope 2.12 release which
is at this point not scheduled yet, but is
Thanks for looking into this, Hanno! Here's my feedback:
Hanno Schlichting wrote:
Hanno Schlichting wrote:
I kept my promise and added the simple tests for the first two issues
I found while doing testing against Plone.
I have meanwhile fixed the first trivial issue (conflicting argument
Wichert Akkerman wrote:
Previously Philipp von Weitershausen wrote:
ViewPageTemplateFile etc. are only meant to be used as class attributes,
never as instance attributes. This statement is also true for the
current, acquisition-based one from Five.
Is that documented anywhere? I can't seem
Malthe Borch wrote:
On Z2, certain imports need to come from Products.Five, to play nicely
with ZPublisher and friends.
Not really. You can inherit from zope.publisher.browser.BrowserView and
Five's browser:page / directive will magically slap
Acquisition.Explicit into a newly-created
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Martijn Faassen wrote:
Technically, I think that this is going to be hard. You'd need to patch
in the magic acquisition base class. Acquisition is the main reason that
some of the code needed to be
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
I'm not sure this is all that useful. For Plone 4, we're just going to
have a number of plone.*, plone.app.* and Products.* (and a few others,
like kss.*) eggs that we can put in a KGS or version pin in a single
Plone egg.
For Plone 4
Philipp von Weitershausen wrote:
Andreas Jung wrote:
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I
would like to start a discussion about the pros and cons, risks and
advantages of any eggification effort
Andreas Jung wrote:
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I would
like to start a discussion about the pros and cons, risks and advantages
of any eggification effort.
Chris favors a 'big' Zope egg
On 5 Feb 2008, at 19:23 , Chris Withers wrote:
Stephan Richter wrote:
On Tuesday 15 January 2008, Chris Withers wrote:
For what I'm after, I need to have a more dynamic buildup of
registrations based on which objects have been traversed through.
Right. I think the component architecture is not
James Robertson wrote:
How do I upgrade Five (http://codespeak.net/z3/five/) from v1.3.8 to
v1.4.4 in Zope v2.9.7?
The Plone product I wish to install (Reflecto v1.2 -
http://plone.org/products/reflecto) apparentl. requires v1.4.1+.
Frustratingly, the installation page
1 - 100 of 870 matches
Mail list logo
