Hi!
Working on the five:registerClass directive for Five 1.2 and Zope 2.9 I
had a closer look at the product initialization code.
I propose the following modifications for the dicts in
Products.meta_types (set by registerClass):
1.) 'action' key:
-
I'd like to give empty
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Weird. I can't reproduce this. Is anyone else seeing this?
For the benefit of those playing along at home:
Jim and I discovered this evening that we were running on
mostly-identical platforms (Ubuntu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Working on the five:registerClass directive for Five 1.2 and Zope 2.9 I
had a closer look at the product initialization code.
I propose the following modifications for the dicts in
Products.meta_types (set by registerClass):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Sigh.
I rebuilt Python 2.3.5:
[EMAIL PROTECTED]:~/p/z2/2$ /usr/local/python/2.3.5b/bin/python
Python 2.3.5 (#1, Oct 27 2005, 10:22:20)
[GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)] on linux2
Type help,
Tres Seaver wrote:
...
Just to note that the tests aren't running cleanly on Stefan Holek's
box, either (but they fail differently):
http://mail.zope.org/pipermail/zope-tests/2005-October/003421.html
http://mail.zope.org/pipermail/zope-tests/2005-October/003422.html
These are not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tres Seaver wrote:
...
Just to note that the tests aren't running cleanly on Stefan Holek's
box, either (but they fail differently):
http://mail.zope.org/pipermail/zope-tests/2005-October/003421.html
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
FWIW:
Alot. :)
$ pwd
/home/tseaver/projects/Zope-CVS/Zope-2_8-branch
$ find . -name *.py | grep -v build-base | xargs grep -l whrandom
./lib/python/AccessControl/DTML.py
./lib/python/Products/PythonScripts/help/PythonScript.py
The bad news is that I don't think I'll ever put in enough time to
fully understand what went wrong here.
The good news is that the newly-released Zope 2.8.4 Windows installer, at
http://www.zope.org/Products/Zope/2.8.4
includes pywin32 build 205. If that doesn't fix PySECURITY_ATTRIBUTES
Hi Tres!
Tres Seaver wrote:
yuppie wrote:
1.) 'action' key:
-
I'd like to give empty 'action' values a special meaning: The meta_type
is not visible in the add drop down in the ZMI.
The five:registerClass directive allows to set empty 'action' values.
This would resolve
FWIW, I know a couple of people are depending on this, so here's an
update.
I am working on merging multidatabase support, but I'm having some
merge/update troubles (if you're interested in the symptoms, see
http://www.plope.com/Members/chrism/heres_to_cvs). I suspect I'll
work it out,
[Tim, trying to comfort a suffering Chris]
...
End of story. Unless you feel you need to make another branch. In
that case, still do the two steps above first. Then create a new
branch from Zope trunk, svn switch your merged sandbox to that new
branch, then svn checkin.
That last part
Jim redid the way Zope trunk stitches in Zope3 since you last looked
at this, and that can create some mechanical problems (of the kinds
you're seeing, in fact). The svn docs probably won't help.
Suggestion (which is repetition of what I suggested before this
happened, but we'll gracefully let
[Chris McDonough]
FWIW, I know a couple of people are depending on this, so here's an
update.
I am working on merging multidatabase support, but I'm having some
merge/update troubles (if you're interested in the symptoms, see
http://www.plope.com/Members/chrism/heres_to_cvs). I suspect I'll
13 matches
Mail list logo
