Paul Winkler wrote:
Update: I *can* fetch the externals from a different box
(my windows laptop, on which i can't successfully build zope
because cygwin's python is known-broken and I don't have a C
compiler other than cygwin's.)
That's no excuse ;)
You can build Zope on Windows easily with
Florent Guillaume wrote:
I've done a big checkin to switch practically everything to the new-
style (actually they're 5 years old) security declarations.
I'd appreciate if another set of eyes could double-check everything;
while I've taken a number of steps to ensure I didn't make mistakes
Florent Guillaume wrote:
Ok I just fixed SecurityInfo, could you update AccessControl/ and
recheck please?
Florent
Hi Florent.
All our unit tests pass again. I'm really looking forward for having a
new Zope .0 release which might be compatible with an existing Plone
release ;)
Great
Hi.
Martijn Faassen wrote:
Andreas Jung wrote:
--On 12. September 2006 13:06:05 +0200 Martijn Faassen
[EMAIL PROTECTED] wrote:
Another point with this whole half-yr release cycle: we're going to
confuse
more and more professional users about which Zope version to use for
what.
I've
Hi,
Martijn Faassen wrote:
Hey,
I only caught this message earlier today, but this is really cool! It's
really nice to see some zope 2 recipes and I hope they indeed will end
up on svn.zope.org soon!
I have sent my contributer agreement per snail-mail last week to Zope
Corp. so it might
Martijn Faassen wrote:
Hey,
Just some feedback in case you haven't gotten this already: I have
problem running bin/buildout as it seems to fail getting workingenv.py
from the cheeseshop:
zc.buildout.easy_install: Getting new distribution for workingenv.py=0.3
Page at
Martin Aspeli wrote:
I just emailed Hanno a few questions, but I thought I'd post them here
as well for further discussion:
- Is it so that I should check out ploneout, run boostrap.py, then
../bin/buildout.sh for each project? Or can I somehow use the same
checkout of ploneout for
Martijn Faassen wrote:
Sidnei da Silva wrote:
On 1/18/07, Martijn Faassen [EMAIL PROTECTED] wrote:
snip
Considering installation of Products we're in new territory anyway -
they're not eggs, after all. I see in the result of ploneout that they
get symlinked into the Products directory - will
Martin Aspeli wrote:
This thread is getting rather long... :)
But except for the interaction of workingenv and buildout, which I'm not
smart enough to say anything useful about, we are almost finished ;)
- There is a 2.5 branch of ploneout
(http://svn.plone.org/svn/ploneout/branches/2.5)
Hi,
I had a few minutes to spare and took a quick look at the implementation.
Philipp von Weitershausen wrote:
As for the implementation, I gave it my best shot in the
philikon-aq-and-__parent__ branch. My experience with C is limited,
especially when it comes to debugging. Help is therefore
whit wrote:
Jim Fulton wrote:
whit wrote:
...
Specific use cases would help to guide this.
the main usecase for me is the following... hanno writes a recipe for
plone, and I want to use that recipe as part of setting up a
openplans development environment (for example inside my workingenv
Hi all,
while pushing local site support in CMF/Plone I came across some weird
test failures. After a while of debbuging I could track this down to the
http method in ZopeTestCase's doctest support.
The method in its Zope2 incarnation is not aware of local sites, while
the one in
Hi again,
I just noticed that the publish method from the Functional base class
from ZopeTestCase has the same problem. You can find the adjusted test
attached.
Hanno
Hanno Schlichting wrote:
Hi all,
while pushing local site support in CMF/Plone I came across some weird
test failures
developers, so should be reasonable stable.
Hanno
Hanno Schlichting wrote:
Log message for revision 75066:
Support for using zopectl on Windows has been added. All commands are
supported and there are two Windows specific ones: install and remove, which
install or remove the Windows
Hi.
Chris Withers wrote:
Hanno Schlichting wrote:
I have just recently been given zope.org SVN write access and made my
first bigger change - making zopectl work on Windows. Please review and
test my changes. The change I made is based on code that I had in the
plone.recipe.zope2instance
Hi,
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.
The branch can be found here:
svn+ssh://svn.zope.org/repos/main/Zope/branches/philikon-aq-and-__parent__
The current
Hi.
Martin Aspeli wrote:
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.
The current state is that there's only one test failure left in Five
Philipp von Weitershausen wrote:
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
Jens Vagelpohl wrote:
On 13 Aug 2007, at 11:11, Hanno Schlichting wrote:
One could also move the CMF bugtracker to LP at the same time. Then only
the APE and the PAS trackers would remain. The PAS tracker is already
empty and the APE tracker is also pretty much obsolete and contains only
Andreas Jung wrote:
--On 12. August 2007 19:53:57 +0200 Andreas Jung [EMAIL PROTECTED] wrote:
to make it short: I propose to move the Zope 2 bugtracker to
Launchpad. Since the Zope 3 bugtracker works already with success on
LP we
should follow with the Zope 2 bugtracker. Objections?
+1,
Laurence Rowe wrote:
Quite a lot of zope3 code (zc.datetimewidget for instance) expects to be
able to access request.locale. ZPublisher does not provide this and to
get around the limitation you must manually set request.locale in your
view using Products.CMFDefault.formlib.form.getLocale.
Dieter Maurer wrote:
Hanno Schlichting wrote at 2007-9-8 00:47 +0200:
...
My suggestion on this would be to make request.locale available in Zope
2.11. It would not be available through any of the other means like
request['locale'] or request.form['locale'] but just as a simple
property
Dieter Maurer wrote:
Hanno Schlichting wrote at 2007-9-9 11:58 +0200:
...
Obviously this needs a bit of rather hairy code
Indeed, as you must not define 'locale' as a request attribute
(it may hide 'locale' set otherwise) but otherwise let it behave as if
it were an attribute.
We already
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
We already do something similar for the request.debug variable, but this
uses a stack frame hack which limits the debug attribute to be shown to
code in the zope.* packages.
For the locale this is an undesired limitation as other
Hi.
Zope 2 currently emits deprecation warnings about old-style event
methods in OFS, for example manage_afterAdd and manage_beforeDelete.
The deprecation warning states that these methods won't be called
anymore in Zope 2.11.
I would like to turn this deprecation warning into a discouraged
Lennart Regebro wrote:
On 10/9/07, Wichert Akkerman [EMAIL PROTECTED] wrote:
Plone 3.0 needs Zope 2.10.3, anything earlier does not work.
Oh, I thought the idea was to always support two Zope versions? I'm
happy to hear that this isn't the case.
For 3.0 we needed the improved local
Hi.
Christian Theune wrote:
Cool,
Am Dienstag, den 16.10.2007, 17:16 -0400 schrieb Hanno Schlichting:
Log message for revision 80896:
Added LAZY_FILE_LOADING constant to PageTemplateFile. When set to True
Page Template files aren't lo
aded and parsed on Zope startup anymore
Martijn Faassen wrote:
Hanno Schlichting wrote:
Log message for revision 81348:
Optimized un/registerUtility via storing an optimized data structure
for
efficient retrieval of already registered utilities. This avoids
looping over
all utilities when registering a new one.
You
Martijn Faassen wrote:
Hanno Schlichting wrote:
Martijn Faassen wrote:
Hanno Schlichting wrote:
Log message for revision 81348:
Optimized un/registerUtility via storing an optimized data structure
for
efficient retrieval of already registered utilities. This avoids
looping over
all
Nathan Yergler wrote:
On 11/27/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
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)
Mikhail Kashkin wrote:
Looks like open source developers, especial Zope 3, have enough money to
buy Time machine. Check Zope 3 profile on Ohloh.net
http://www.ohloh.net/projects/4495?p=Zope+3
Codebase 138,855,676 LOC
Effort (est.) 49267 Person Years
$2,709,689,938
This is
Sidnei da Silva wrote:
On Dec 9, 2007 5:30 AM, Andreas Jung [EMAIL PROTECTED] wrote:
Objections? Thoughts?
That branch didn't look like it was far off being finished. Is there a
TODO of what is pending to finish it?
The good news is that all Zope tests are passing and all the heavy
lifting
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
http://svn.zope.org/Zope/branches/philikon-aq/
branch. Unfortunately both can't work (lack of personal time) on the
branch and finish it in
Hanno Schlichting wrote:
Andreas Jung wrote:
The only thing I'm going to do if no one objects is to deprecate calling
the ViewPageTemplateFile in Five without passing in the view. This
should at least allow us to merge the aq-branch without any problems for
Zope 2.13 if noone can think
Philipp von Weitershausen wrote:
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
Andreas Jung wrote:
--On 28. Dezember 2007 17:56:20 +0100 Hanno Schlichting
[EMAIL PROTECTED] wrote:
Now all of those above packages aren't in the beta1 tarball. I'd
consider this a bug, right?
I removed the externals so they are not in the b1 tarball. Possibly
a bug from the deprecation
Andreas Jung wrote:
--On 29. Dezember 2007 08:17:43 +0100 Hanno Schlichting
[EMAIL PROTECTED] wrote:
Adding those deprecated but still functional packages to the KGS would
be one way, but seems to be a bit of work.
I just wonder what deprecation in the future means. There were some
Tres Seaver wrote:
Nikhil N wrote:
Hmm, very strange. I just did:
I used:
$ workingenv aq
$ source aq/bin/activate
$ easy_install Acquisition
$ python
For both Python 2.4 and 2.5 and can reproduce the problem.
from ExtensionClass import Base
from Acquisition import Implicit
class
Hi.
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 duplicated - without the
existence of acquisition wrappers, security
Morning!
Andreas Jung wrote:
last night, roughly 20 tickets of the Zope 2 tracker were marked as
Invalid by a person (never heard its name) which is no part of the Zope
2 developers group on LP. Independent of each ticket I am a bit
surprised that obviously any authenticated LP user is able
Martijn Faassen wrote:
Alexander Limi wrote:
On Mon, 14 Apr 2008 10:11:11 -0700, Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those
failing Plone tests, merge the branch and be on our way.
This gets back to Hanno's suggestion
Hi again.
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
called 'instance') and added a simple test for the second one.
Now after
Hi.
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
Scope:
For those unfamiliar with the branch, it makes Acquisition aware of
__parent__ pointers. This makes it unnecessary to use Acquisition
mixin's for Zope 3 code to use them in Zope 2 code. The
Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Philipp von Weitershausen wrote:
In my opinion, the fact that it accidentally worked as an instance
variable isn't a very strong argument for continuing to support it. To
me, this is a prime example of misusing a Five
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty of time to test.
This sounds good. Here's
Hi.
Chris McDonough wrote:
True, although the Zope2 instance-creation scripts will probably become
setuptools console scripts, which means that things will likely need to
get shuffled around a bit from how things are now regardless and old
hands will be baffled anyway.
repoze.zope2 needs
Hi.
Hanno Schlichting wrote:
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
[...]
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.
Just as a note
Tres Seaver wrote:
I'd like to rip out the old Interface module from the 2.11 branch and
the trunk, along with all the useless decoys which import it. THere is
no *good* BBB reason to keep them around: anybody still depending on
them in A.G. 2008 needs to switch over, anyway.
Objections?
Hanno Schlichting wrote:
Hanno Schlichting wrote:
I'd like to propose to merge the philikon-aq branch into Zope trunk
aka Zope 2.12.
[...]
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
Hi.
I'd like to propose to deprecate the
Products.PageTemplates.GlobalTranslationService module and all custom
translation handling from Products.Five.
Rationale:
In order to bring zope.i18n translation handling to the masses, some
backwards compatibility code for
Christian Theune wrote:
On Sun, Apr 27, 2008 at 11:57:07AM -0400, Paul Winkler wrote:
Any idea what's wrong with Zope2.buildout?
Looks like Acquisition is not built properly:
http://zopebuildbot.whq.gocept.com/builders/Zope2.buildout/builds/75/steps/test/logs/stdio
No idea, the egg it has is
Hanno Schlichting wrote:
Christian Theune wrote:
On Sun, Apr 27, 2008 at 11:57:07AM -0400, Paul Winkler wrote:
Any idea what's wrong with Zope2.buildout?
Looks like Acquisition is not built properly:
http://zopebuildbot.whq.gocept.com/builders/Zope2.buildout/builds/75/steps/test/logs/stdio
Christophe Combelles wrote:
I think merging is not really done, and there are several changes to do
for i18n:
- split the zope gettext domain into all the separate namespaces.
Maybe only zope.app.* packages can be kept under the zope.app domain.
Just as a side note, I added a feature to
Chris McDonough wrote:
Jens Vagelpohl wrote:
On Apr 30, 2008, at 12:41 , Christian Theune wrote:
On Wed, Apr 30, 2008 at 12:16:53PM +0200, Wichert Akkerman wrote:
I'm trying to figure out what the current state of the art for
monitoring Zope2 processes is. Ideally I'ld want the equivalent of
Hi.
Roger Ineichen wrote:
I added a new package for extract i18n locales
and I have some questions.
Is it posible to split the zope.app.locales
package into a package which offers the
interfaces and classes e.g. PotMaker,
the generic extract.py file and another one
which provides the
Hi.
Roger Ineichen wrote:
Anyway, Since zcml is a default part of zope locale extraction
it make no sense to me to not using a working setup for
locale extraction. Grok? Does Grok not use zcml extraction?
If not, we could probably change the z3c.recipe and disable
the default zcml extractor.
Hi.
ranjith kannikara wrote:
I came across an error in module Acquisition, while trying to port
zope2 to python2.5. There was a discussion over the same topic in
JAN-2008. In acquisition the wrapper compare is returning false
irrespective of the parameters.
And the problem I stuck with was
Hi.
Hanno Schlichting wrote:
ranjith kannikara wrote:
I came across an error in module Acquisition, while trying to port
zope2 to python2.5. There was a discussion over the same topic in
JAN-2008. In acquisition the wrapper compare is returning false
irrespective of the parameters
Andreas Jung wrote:
lots of old-style Zope products are now available as eggs. However a lot
of people still don't work with buildout and need the old-style tar-balls.
Does anyone know of a setuptools extension for generating and upload the
tar-balls directly from a Products. package?
Hi.
Benji York wrote:
If you use zc.buildout, then you can try the branch by checking it out,
adding a develop entry into your buildout config referencing it, and
updating any version spec for zope.testing to 3.6dev. I'd really like
third-party confirmation of the total test time reductions
Tim Hicks wrote:
Am I right in thinking that there is a duplication of information in
having an eggified product's version number stored in setup.py and
version.txt?
Having your setup.py read its version from version.txt is easy, if you
don't want to update two places.
I think the more
Chris Withers wrote:
Martin Aspeli wrote:
Certainly, running Python 2.4 and Zope 2.10 compiled with mingw32 on
Windows as per http://plone.org/documentation/tutorial/buildout has
not given us any problems after a few months of using it.
I would expect the above to work as *everything* is
Hi.
It's awesome to see some progress on this. You are aware of the Gettext
manual at
http://www.gnu.org/software/gettext/manual/gettext.html#Plural-forms right?
Stephan Richter wrote:
On Wednesday 16 July 2008, Lennart Regebro wrote:
While talking about this, what would a ZPT
Sorry.
There's some garbage in my last message. Disregard the following bits.
Hanno Schlichting wrote:
br i18n:attributes=
You selected
span tal:content=num i18n:name=num5/span
out of
span tal:content=total i18n:name=total10/span
files.
/p
Can someone think about an example involving
Lennart Regebro wrote:
On Wed, Jul 16, 2008 at 22:36, Hanno Schlichting [EMAIL PROTECTED] wrote:
p i18n:translate=
You have to pay
span tal:content=view/formatted_amount i18n:name=amount
i18n:count=view/amount6 dollars/span.
/p
In this case the underlying value is a simple integer
Chris Withers wrote:
Martijn Faassen wrote:
Okay, so we can safely add Chris (and also Philipp) to the list of
people maintaining our windows binary eggs. Awesome! Chris, do you
think you can take it from here in getting an environment set up?
Would be rgeat to have a bullet point list for
Chris Withers wrote:
Sidnei da Silva wrote:
On Fri, Jul 18, 2008 at 1:23 PM, Chris Withers
[EMAIL PROTECTED] wrote:
Would be rgeat to have a bullet point list for how to get a suitable
environment set up given that I don't have mingw32 and have never
used it
before in my life :-S
Like
Martijn Faassen wrote:
On Mon, Jul 21, 2008 at 8:40 AM, ranjith kannikara
[EMAIL PROTECTED] wrote:
[snip]
I hope the code for this assert (used in line assert self.aq_base ==
self ) is defined for zope and can be fixed with not so much effort.
Can any one suggest where why these different
Hi.
Would someone (Jim, Philikon, Fred) be willing to do a new
zope.interface release or give me access rights on PyPi to do it myself?
Thanks,
Hanno
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No
Fred Drake wrote:
On Sat, Jul 26, 2008 at 7:36 AM, Hanno Schlichting [EMAIL PROTECTED] wrote:
Would someone (Jim, Philikon, Fred) be willing to do a new zope.interface
release or give me access rights on PyPi to do it myself?
I've added Stephan Richter and Andreas Jung to the project on PyPI
Martijn Faassen wrote:
I just looked at the PyPI page of 'transaction':
http://pypi.python.org/pypi/transaction
And I see some weirdnesses:
* it's called 'transaction 1.0a1'
* the 'changes' claim however:
1.0 (unreleased)
What's up? Clearly something went wrong during the
Martijn Faassen wrote:
There appears to be a release of zc.recipe.testrunner 1.1.0 which
requires zope.testing 3.6.0, but zope.testing 3.6.0 was not released as
far as I can see. This means zc.recipe.testrunner 1.1.0 cannot be installed.
http://pypi.python.org/pypi/zope.testing/3.6.0
This
Andreas Jung wrote:
--On 4. September 2008 13:38:27 +0200 Martijn Faassen
[EMAIL PROTECTED] wrote:
There appears to be a release of zc.recipe.testrunner 1.1.0 which
requires zope.testing 3.6.0, but zope.testing 3.6.0 was not released as
far as I can see. This means zc.recipe.testrunner
Wichert Akkerman wrote:
I was wondering why a non-zope project was pulling in zope.publisher and
ended up finding this chain:
chameleon.core - zope.i18n - zope.component[zcml] - zope.security -
zope.location - zope.traversing - zope.publisher
can we move the zcml components of
Andreas Jung wrote:
Depends on which Python versions we want/must support for the future.
One option would to jump on Python 2.6 for the next releases (skipping
Python 2.5 and dropping Python 2.4 support).
Just as a voice from the Plone crowd. With our current planned roadmap
we won't move to
Andreas Jung wrote:
RestrictedPython: I talked with Alan Runyan about this topic at the
Plone conferenceif we are serious then RP has to be reviewed. But
who can review it and how long would it take. There are possibly only a
limited number of people with the experience and skills for
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 the major
changes are:
Martijn Faassen wrote:
On Wed, Oct 15, 2008 at 2:30 PM, Andreas Jung [EMAIL PROTECTED] wrote:
You mean the review of RestrictedPython?
Yes.
If RestrictedPython is to be reviewed for changes, it *might* be
easier to do this for 2.4 - 2.5 instead of the big leap of two python
versions.
Hi.
I'd like to get feedback on an idea I had recently.
Problem
Zope2 currently includes large parts of Zope 3. Not all of the zope.*
and zope.app.* packages are maintained or are in use.
Still Zope 2 includes large amounts of them and thus implicitly
advertises them to be used. In addition
Hi,
I just released a new zope.interface 3.5.0 to be found at
http://pypi.python.org/pypi/zope.interface
I uploaded a zipped source distribution and (as we have C extensions)
Windows installers for Python 2.4, 2.5 and 2.6.
Please contact me, if you find problems with it.
Hanno
Hanno Schlichting wrote:
I just released a new zope.interface 3.5.0 to be found at
http://pypi.python.org/pypi/zope.interface
I uploaded a zipped source distribution and (as we have C extensions)
Windows installers for Python 2.4, 2.5 and 2.6.
Spotting my own mistake, I uploaded binary eggs
Chris Withers wrote:
Sidnei da Silva wrote:
I would like to propose backporting some of the fixes needed for
Python 2.5 and 2.6 all the way down to Zope 2.10.
I would *not* backport changes to RestrictedPython because
those are actually features (support for newer versions of Python) as
Tres Seaver wrote:
Hanno Schlichting wrote:
Here's a list of things I'd like to see in a 2.12 release:
- Official Python 2.5 and 2.6 support (almost done, requires a community
decision on when we call RestricedPython supported and reviewed)
+1 for 2.5; I'm pretty sure 2.6
Tres Seaver wrote:
Hanno Schlichting wrote:
I'm fine with having Plone 4 able to run on a 2.6-compatible Zope2. If
we add Python 2.6 to the supported list for a no-later-than Q3 2009 Zope
release, that should be sufficient, no?
Sure!
From a Zope perspective 2.11 should have had Python 2.5
Jens Vagelpohl wrote:
On Nov 4, 2008, at 09:10 , Andreas Jung wrote:
In the meantime, we can acknowledge that 2.8 and 2.9 are
retired (no
future work except maybe important security fixes),
+1
and announce that
2.10 will be retired after the 2.12 release:
We have to care about
Andreas Jung wrote:
On 04.11.2008 18:19 Uhr, 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
Jim Fulton wrote:
http://download.zope.org/distribution was set up as a place to publish
distributions while we were learning about setuptools, eggs, and
pypi. I think now, we're all using PyPI (or local repositories). I'd
like to deprecate this site, making it read-only for now, but
Hi.
I had some time to work on the Zope2 egg and the correct / minimal
dependency set. The current work is at:
svn://svn.zope.org/repos/main/Zope2.buildout/trunk
This gives you a Zope2 egg in a buildout environment with the latest
releases of all dependencies included. The Zope2 egg itself
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 code there should
Hi.
I just looked over this and fixed one test failure in Five. In general
all tests pass now, when run from the eggified Zope in:
svn://svn.zope.org/repos/main/Zope2.buildout/trunk
I guess that the zope.testbrowser problems are a mix of test
interdependencies and maybe a differing mechanize
Tres Seaver wrote:
Hanno Schlichting wrote:
In general all tests pass now, when run from the eggified Zope in:
svn://svn.zope.org/repos/main/Zope2.buildout/trunk
I just vendor imported mechanize 0.1.9 into the Zope SVN, and have
changed the svn:external in my Z2 trunk checkout to point
Tres Seaver wrote:
Matthew Wilkes wrote:
Log message for revision 93717:
assert isn't a function, using parens will cause the two arguments to be
treated as a 2-tuple, hence always true.
Changed:
U zope.tal/trunk/src/zope/tal/dummyengine.py
-=-
Modified:
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Mon Jan 5 12:00:00 2009 UTC to Tue Jan 6 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.
Yeah, thank you Tres and Stefan!
Hanno
___
Zope-Dev maillist -
Christian Theune wrote:
I noticed 'zope.globalrequest' on the PyPI RSS feed today and wonder
about it. IMHO this implements an anti-pattern in an official way
without a warning that this needs to be handled with care.
The discussion for this happened on the plone-dev mailing list. The
Chris Withers wrote:
Andreas Jung wrote:
Namespaces are like dust and smoke. We already have enough (pointless)
namespaces. So let's stick with zope.* and z3c.* for Zope related packages.
Why note merge those two into one then?
Merging namespaces just causes work without any benefit. A
Jens Vagelpohl wrote:
On Jan 16, 2009, at 18:25 , Hanno Schlichting wrote:
The concept of
giving SVN repositories any kind of quality level aspect failed in the
same way. Dependencies are specified in the setup.py and egg metadata.
Quality is judged by who has written some code, number
Tres Seaver wrote:
Hanno Schlichting wrote:
Log message for revision 94810:
Hhm, pdb?!?
Changed:
U Products.GenericSetup/trunk/Products/GenericSetup/tests/common.py
-=-
Modified: Products.GenericSetup/trunk/Products/GenericSetup/tests/common.py
Tres Seaver wrote:
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Mon Jan 19 12:00:00 2009 UTC to Tue Jan 20 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope[2.buildout]-trunk
Andreas Jung wrote:
I am currently trying to fix the generation of the creation and
configuration of the startup scripts. I am getting this when running
zopectl:
The debugger output isn't much helpful:
Wichert Akkerman wrote:
Previously Tres Seaver wrote:
Andreas Jung wrote:
- removing ZClasses completely
This is done now.
There is a whole lot of legacy code surrounding Zope startup and the
persistent control panel that is only there to support ZClasses.
Removing them would allow for a
1 - 100 of 620 matches
Mail list logo
