Thomas Lotze wrote:
I just realized that Zope 2.11.0-a1 contains zope.app.fssync but not
zope.fssync. This doesn't make much sense to me given that the former
depends on the latter. Is there a good reason for it, should both be
included, or none of the two?
Probably an oversight.
According to CHANGES.txt, you're fixing a bug. Where's the test that
exercises that the bug fix code? (Yes, I'm going to get anal about this.)
To anybody, the fix will look a bit dubious. At least I personally am
wondering how simply changing the datatype in the ZConfig schema will
work... A
Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
+100
--
http://worldcookery.com -- Professional Zope documentation and training
___
Zope-Dev maillist - Zope-Dev@zope.org
Stephan Richter wrote:
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the traffic is pretty high there.
If you do not follow it at all,
Stephan Richter wrote:
On Saturday 06 October 2007 13:14, Andreas Jung wrote:
You are using 7 times the term Zope2 and 9 times Zope 3
and also Plone 3.0 in this small text. Can you try to describe
this without 2 or 3 in Zope *? I guess not, right?
s/Zope 2/Zope application server
s/Zope 3/Zope
Martijn Faassen wrote:
Zope 3 is a bunch of technologies for building (web) applications in the
form of an integrate set of Python libraries.
Let's call those the Zope Libraries. Because by now we have far more
than just the ones that came from exploding Zope 3 (e.g. all the ones
from the
Dieter Maurer wrote:
David Pratt wrote at 2007-10-8 00:21 -0300:
Zope 2 is one application among many dependent upon zope 3.
Zope 3 is different software than zope 2.
I do not argue with you that Zope3 is different software than Zope 2.
What I argue about is Zope 2 is an application.
I have
Uli Fouquet wrote:
during grok development we recently experienced some trouble with the
zope.app.error package. We distribute the list on
`http://download.zope.org/distribution` as sources list for grokproject,
so that projects created with that tool, by default lookup this list for
available
Hanno Schlichting wrote:
Log message for revision 80945:
Moved two implements declarations from Five into the proper classes.
I object to this change. HTTPRequest does not really fulfil the
IBrowserRequest interface, and ObjectManager isn't a real IContainer
either. I understand that
Baiju M wrote:
Hi Limi,
Alexander Limi wrote:
Sorry if this has been asked hundreds of times before — I couldn't
find any info on this apart from the Summer of Code project related
to Zope 3.
Now only the packages under `zope` `zope.app` packages works
using Python 2.5 . I don't know
Alexander Limi wrote:
Will Zope 2 ever run on Python 2.5, or is that postponed indefinitely?
It will run on Python 2.5 when somebody makes it run.
We see an increasing amount of users trying to use Zope 2 with their
systems that have Python 2.5 as default.
Then I suggest you do something
Stephan Richter wrote:
On Friday 09 November 2007, Roger Ineichen wrote:
Hi Tres
Whoever released those two eggs (the '.dev-r#' ones) need
to release real updated packages, and then grok 0.11.1
should be released using them.
DEATH TO FAUX PACKAGES!
As far as I understand, this does not
Stephan Richter wrote:
On Friday 09 November 2007, Philipp von Weitershausen wrote:
It can't because you guys broke a dozen packages when you split up some
of the zope.app.* packages. I'm going to fix this now.
Can we stop pointing fingers, please?
Sorry for not sugar coating the facts. I
Stephan Richter wrote:
On Friday 09 November 2007, Philipp von Weitershausen wrote:
Modified: zope.app.securitypolicy/trunk/setup.py
===
--- zope.app.securitypolicy/trunk/setup.py 2007-11-09 13:08:59 UTC
(rev 81634
Lennart Regebro wrote:
On Nov 9, 2007 4:06 PM, Roger Ineichen [EMAIL PROTECTED] wrote:
Create our own locked down index?
I think so because,
Surely there must be a way to say I want to use THAT KGS over there.
Except for this module, that should hav this version. And of course,
all these
Roger Ineichen wrote:
Before KGS there was no concept for keep the eggs in sync. Each project
has to do it by itself. KGS at least is something that helps to manage
the zope eggs. Everything outside this has to be done by the release
manager of the project.
And before the KGS, the cheesshop
On 9 Nov 2007, at 16:51 , Lennart Regebro wrote:
On Nov 9, 2007 4:06 PM, Stephan Richter
[EMAIL PROTECTED] wrote:
On Friday 09 November 2007, Philipp von Weitershausen wrote:
-Version 3.4.0 (2007/9/25)
--
+- Reverted the premature split away of core components
On 9 Nov 2007, at 17:11 , Lennart Regebro wrote:
On Nov 9, 2007 5:02 PM, Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
Yeah, but other packages in the current KGS have already been
converted to use zope.securitypolicy, so reverting the split-up would
cause more trouble than I thought
http://wiki.zope.org/zope3/PackagesShouldLoadConfigurationTheyDependUpon
Comments appreciated. Otherwise, silence is treated as assent.
I'm planning on starting with this tomorrow as part of the Boring Sprint
we're having in Tübingen right now.
___
On 9 Nov 2007, at 20:15 , Roger Ineichen wrote:
Betreff: [Zope-dev] RFC: Packages should load configuration
they depend upon
http://wiki.zope.org/zope3/PackagesShouldLoadConfigurationThey
DependUpon
Comments appreciated. Otherwise, silence is treated as assent.
I'm planning on starting with
Tres Seaver wrote:
A KGS needs to have the following properties:
- The generation zero of any KGS is an empty set of revisions.
- By default, any revision N of a KGS starts out as a draft version
which is an empty layer over version N-1. Changes to the draft
then shadow any versions
On 10 Nov 2007, at 14:06 , Tres Seaver wrote:
If we have software which can generate the pacakge index at a URL
for a
KGS, then it could certainly generate a 'version.cfg' as well, to
support buildout.
We already do. Stephan's zope.release does that already. The file is
actually available
Chris McDonough wrote:
- Institute a policy that all distributions that are released to the
cheeseshop should be installable via easy_install. IMO, if they
are not installable this way, they should not be released to the
cheeseshop, given the larger Python community's
Chris McDonough wrote:
Attempting to easy_install all 'zope'-related releases using the script
at
http://svn.repoze.org/playground/trunk/chris/zopesvnchecker/releasechecker.py ,
the results were:
8 failures, 183 successes.
See http://www.plope.com/static/misc/rcresults-2007-11.17.txt for
Stephan Richter wrote:
I just updated the Zope 3.4 KGS with some new features.
1. You only need to upload the controlled-packages.cfg file now; all other
files are generated.
2. The controlled-packages.cfg file now supports a name and version option.
Thus, all generated files are versioned
Chris Withers wrote:
Tres Seaver wrote:
Both are. RestrictedPython is still used in Zope2.
Ah, so RestrictedPython is actually what's used for Script (Python)'s in
current Zope 2 releases?
Yes, it's a low-level compiler for Python code that replaces certain
operations such as getattr
On 19 Nov 2007, at 20:26 , Chris Withers wrote:
So, I'm guessing RestrictedPython is the one to aim for?
No idea what you need...
http://mail.python.org/pipermail/python-list/2007-November/466438.html
It seems like zope.security does exactly what you need (e.g. user code
shouldn't have to
On 20 Nov 2007, at 00:15 , Chris Withers wrote:
Philipp von Weitershausen wrote:
On 19 Nov 2007, at 20:26 , Chris Withers wrote:
So, I'm guessing RestrictedPython is the one to aim for?
No idea what you need...
http://mail.python.org/pipermail/python-list/2007-November/466438.html
It seems
Maurits van Rees wrote:
I have been busy with zope.formlib. See this weblog entry for some
background:
http://maurits.vanrees.org/weblog/archive/2007/11/search-forms-with-zope-formlib-and-batching
This is Plone 3 with Zope 2.10.4 btw.
I discovered there is a difference between getting a
Wichert Akkerman wrote:
Previously Ross Patterson wrote:
Chris Withers [EMAIL PROTECTED] writes:
Hi All,
Does the component architecture support un-registering adapters and
the like?
From zope.component.interfaces:
class IComponentRegistry(interface.Interface):
Register components
On 25 Nov 2007, at 13:37 , Chris Withers wrote:
Philipp von Weitershausen wrote:
class IComponentRegistry(interface.Interface):
I think you should use zope.component.getGlobalSiteManager() for
this.
So getGlobalSiteManager returns a component registry?
Yes. It returns the one and only
Chris Withers wrote:
Is deferredimport handy for dealing with circular import problems,
Sure.
or was it targetted at solving another problem?
From zope.deferredimport/trunk/src/zope/deferredimport/README.txt or
its PyPI page (http://pypi.python.org/pypi/zope.deferredimport/3.4.0):
Christophe Combelles wrote:
Hello,
An full-egg zope 3.4 buildout installed with zopeproject tells me the zope
version is 3.3.1 (in /++etc++process/):
- I have a fully eggified zope 3.4 installed with zopeproject.
- I also have a zope 3.3.1 installed on the system python.
When I start the 3.4
Chris Withers wrote:
Philipp von Weitershausen wrote:
On 25 Nov 2007, at 13:37 , Chris Withers wrote:
Philipp von Weitershausen wrote:
class IComponentRegistry(interface.Interface):
I think you should use zope.component.getGlobalSiteManager() for this.
So getGlobalSiteManager returns
Nathan Yergler wrote:
I've run into a problem this morning with i18n in Zope3, and I'm not
exactly sure what the appropriate approach is. We have a set of South
African translations, paticularly Zulu (zu) and Sotho (st) that are
getting picked up correctly. Upon some inspection it appears that
On 26 Nov 2007, at 19:22 , Chris Withers wrote:
(and I'm guessing there is an ISite somewhere, as I could find no
definition of setSiteManager, but how does
IComponentArchitecture's getSiteManager relate to that of ISite?)
zope.component.getSiteManager() will return whichever component
Sebastian Wehrmann wrote:
while using the AbsoluteURL Adapter in a view,
By the way, you're using Five's AbsoluteURL adapter. (It's different
from the one in Zope 3). Also, the patch below seems to be for Five.
Would be good to mention that :).
it only returns the path
of the object, not
On 28 Nov 2007, at 11:45 , Sebastian Wehrmann wrote:
Can you round up a test that demonstrates how the current
implementation fails to cover your case and how your suggestion
change fixes that?
While trying to write a test it turned out, that it's not a problem
in Five but in the
On 28 Nov 2007, at 12:54 , Daniel Havlik wrote:
Am 28.11.2007 um 12:01 schrieb Philipp von Weitershausen:
The problem we tried to solve was: We have a structure of Plone
content objects. We wanted to access a particular one in a view
which can be called anywhere. Therefore we registered
Martijn Pieters wrote:
On Nov 28, 2007 12:29 AM, Nathan Yergler [EMAIL PROTECTED] wrote:
If you follow the wink,
http://www.unicode.org/cldr/repository_access.html has the details to
the files. Currently the latest is at
http://unicode.org/Public/cldr/1.5.0/core.zip.
Zope at this point still
Roger Ineichen wrote:
Hi Malthe
Betreff: [Checkins] SVN: z3c.jbot/ Initial import.
Log message for revision 81997:
Initial import.
[...]
+ from Products.Five.browser.pagetemplatefile import
+ ZopeTwoPageTemplateFile
I really like what you are doing, cool ideas!
But I also have a
Tres Seaver wrote:
Martijn Faassen wrote:
Hey,
On Nov 28, 2007 12:16 AM, Martijn Jacobs [EMAIL PROTECTED] wrote:
We could also consider putting them in some kind
of collective-like SVN repository so that people can
make changes when they need to.
I think this is a great idea as it works
sorry, meant to CC [EMAIL PROTECTED], not zope-dev@zope.org
Philipp von Weitershausen wrote:
Tres Seaver wrote:
Martijn Faassen wrote:
Hey,
On Nov 28, 2007 12:16 AM, Martijn Jacobs
[EMAIL PROTECTED] wrote:
We could also consider putting them in some kind
of collective-like SVN repository
Chris Withers wrote:
Hi All,
I'm looking to get RestrictedPython working in Python 2.5.
Has any work been done on this so far?
My first question is about the right way to get a checkout that I can
develop in now. In years gone by, I would have created a branch of the
whole of zope 3, checked
On 5 Dec 2007, at 15:46 , Chris Withers wrote:
There's python setup.py develop, which will also install the
checked out thing as a development egg,
What does that mean? Which python files would I edit to make changes
in this case?
The ones you checked out. This isn't rocket science, you
Chris Withers wrote:
Philipp von Weitershausen wrote:
$ svn co $z/RestrictedPython/trunk RestrictedPython (or a branch)
$ cd RestrictedPython
$ /your/development/python bootstrap.py
$ bin/buildout
$ bin/test
($z refers to svn+ssh://svn.zope.org/repos/main on my system)
Where does this put
Christophe Combelles wrote:
Hi,
When creating a buildout with zopeproject, the site.zcml puts the package
registration before the apidoc registration:
include package=${package} /
!-- Remove this reference to disable the APIDoc tool.
You should do this for production --
include
Hi there,
zope.sendmail is missing changelog entries for the last two releases. As
far as I can tell from the checkins list (which isn't always accurate),
these people have last worked on zope.sendmail:
* Marius Gedminas
* Benji York
* Albertas Agejevas
It would be cool if they and
Andreas Jung wrote:
--On 18. Dezember 2007 21:53:55 +0100 Hanno Schlichting
[EMAIL PROTECTED] wrote:
Andreas Jung wrote:
the Zope 2.11 beta phase has been delayed for while. The reason for
holding but the release was Philipps and Hannos work on the
On 24 Dec 2007, at 16:32 , Andreas Jung wrote:
WARN: KGS incomplete - zope.app.content_types not found
WARN: KGS incomplete - zope.app.event not found
WARN: KGS incomplete - zope.app.filerepresentation not found
WARN: KGS incomplete - zope.app.location not found
WARN: KGS incomplete -
On 25 Dec 2007, at 10:58 , Andreas Jung wrote:
/opt/python-2.4.4/bin/python /Users/ajung_data/sandboxes/Zope/
ajung-2-11-prep-branch/test.py -v
Running tests at level 1
Running unit tests:
Running:
..
rror in test testSetupConfiguredLoggers
Chris Withers wrote:
Hi All,
I saw the zope.proxies module and wondered if it might be able to help
me with two problems I need to solve:
- can these proxies be used to keep track of a traversal path in much
the same way (although no seperate containment and context chains
needed) as the
P.S.: This is explained in detail in my book, chapter on containers.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
Andreas Jung wrote:
Log message for revision 83064:
added various zope.app packages for backward compatibility
Wrong branch :/. It's fine for those to be missing from the *trunk*,
since they were scheduled for removal for Zope 2.12 anyway. They just
need to be there on the 2.11 branch.
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
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
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
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
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
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
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
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
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
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
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 =
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,
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
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
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
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:
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:
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*.
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
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
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
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
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
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
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
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,
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
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
301 - 400 of 436 matches
Mail list logo
